Jan 07, 2016 - 03:18 PM
We support a number of merchant gateway (find a list here: https://www.nsoftware.com/ibiz/epayment/).
The recommend gateway:
All other are available, however we do not recommend using a gateway that is not widely used by our customers.
Here are the reasons why:
1) Each gateway has hundreds of pages of error integration rules and unique API code. If we do not widely use a gateway and we don’t recommend it, that means if you start using it, we have no idea how well it will perform at scale. It doesn’t mean you can’t use it or we don’t support it, it just means that you may have problems with it.
For example some gateways will not pass correct error messages back to the customer when there is a problem, or the way they pass it back to Shopping Cart Elite it will not parse correctly. Some gateways will not handle a payment transaction with decimals points (and if we miss it during beta testing your customer will fail when you are live). Some gateways will not pass the transaction # back to us making the order remain pending in our system even though it is paid (assuming we miss it in beta testing you will have problems).
Even though we support all the gateways, we do not guarantee the performance of those that are not widely used by our customers.
2) Some gateways have conflicting AVS (address verification rules) with Shopping Cart Elite that decline transaction without our knowledge, some of them will not accept AMEX and you won't know about it until someone complains. When we explain to you the best practices on using a payment gateway, we can only rely on those we widely use and interact with on a daily basis. So if a gateway starts producing errors that contain only error codes, we will not know how to solve them or where to start.
3) If a gateway changes an API or stops working, and you are the only one using that gateway, the case will be considered a priority 2 because it is only affecting only your store and you can always sign up with another gateway we recommend. We will resolve your case but we can't guarantee any SLA (service level agreement) on a gateway that we don't recommend. If you choose to use a gateway that we do not recommend, you will have to make sure you don't have problems and if you do have a problem, you will need to report it and allow us time to resolve it.
If you insist on using a gateway on the list that is not certified, please understand the liability you will have of using it.
4) Alot of our clients use BluePay and we recommend BluePay because BluePay is trusted by over 76,000 businesses and processes $21 billion in transactions annually. This puts it well into the big leagues of processing companies, with a full range of products and services available for small to enterprise-level businesses.
BluePay offers a variety of specialized merchant accounts designed to fit your particular business situation. Industry-specific programs include restaurants, retail stores, churches, non-profit organizations, and many others. Enterprise and B2B/B2G merchants may take advantage of BluePay’s Level 2, Level 3, and large ticket processing capability. All the descriptions of end-to-end encryption and tokenization basically just mean that BluePay has good data security features. As a feature of the BluePay gateway, merchants can customize their own fraud protection parameters and filters.