|
Merchant Account Questions
|
|
Q
|
Why are you offering these merchant accounts?
|
|
A
|
Basically, because they save money, offer excellent service, and just plain make sense, especially when coupled with OneStep ChargeSM.
|
|
|
Q
|
What do you mean by "surcharged to death?"
|
|
A
|
Take a look at your most recent merchant account statements (if your provider actually gives you a statement that can be deciphered). Do you see that most (if not all) of your transactions include heavy surcharges? Were you promised rate X, but see rate X + Y applied to virtually every transaction on your statement? You are being surcharged to death. Your transactions are not qualifying for the great rate you thought you were getting, for various reasons. Switch to one of our merchant accounts, install OneStep ChargeSM, and then look at your new statements. You'll be pleased.
|
|
Q
|
Will my existing merchant account work with OneStep ChargeSM?
|
|
A
|
Yes. That is, the processing networks through which a OneStep ChargeSM solution is certified cover over 90% of all U.S. banks, as well as European and Canadian banks. It is extremely rare that an account cannot be used (occasionally the merchant account representative must simply build a new file for a different network). In such cases, we can even custom-build a certified connection into the bank of choice, if desired.
|
|
|
Integration Questions
|
|
Q
|
Should I expect a complicated or time-consuming integration process for OneStep ChargeSM?
|
|
A
|
No. The OneStep ChargeSM API is utilized basically by creating a temp-table and calling a run program. Depending upon your front-end and futher requirements, you can expect to get OSC up and running in a very short time.
|
|
|
Q
|
Do I have to install other software on my UNIX/Linux/Windows server?
|
|
A
|
No, unless your chosen configuration needs an encrypted transport and your OS doesn't have it. A readily-available freeware utility can solve this, but even this small utility is not necessarily required.
|
|
|
Q
|
Does OneStep ChargeSM require particular Progress products such as the AppServer?
|
|
A
|
No. All you need is Version 9 or later (for TCP/IP socket functionality).
|
|
|
API Questions
|
|
|
Q
|
Why was my transaction "declined" by the processor?
|
|
A
|
There are a host of reasons why a particular transaction might be declined. Examine your trExec.authDetails field, though in many cases no additional information is provided by the processing network. The reasons can range from insufficient credit to a card reported stolen to an invalid expiration date entered.
|
