8 Things to Look For in a Payment Gateway Integration
Robust API. Payments functionality is integrated into platforms that are used in differing ways by many different organizations. The API should provide all the needs of the integrating organization, be easy to use and supply example code for commonly used languages.
- Integration support. In some cases providing a robust API isn't enough. The ability to get in touch with professionals on the gateway's integration technical support team is a must. To be able to talk to someone on the integration team can be extremely helpful in some cases.
- Omnichannel functionality. In todays market space there are applications that must support phones, tablets, desktop, point of sale and specialty hardware devices. Integration methods must meet the needs of all. Multiple payment modals also fall under this umbrella. United States ACH and credit cards, Canadian EFT and credit cards as an example.
- Options for managing recurring payments. A good payment integration API will have functionality that supports recurring payments. However, in some use cases the SaaS integrating organization will prefer that it is their application that schedules, manages and maintains the subscription based payments.
- Handling sensitive data. Is the gateway provider a PCI level one certified payment provider? Your gateway partner should be tokenizing sensitive data, leaving you with nothing to store other than a reference token that's not usable should a breach occur. In some integration use cases the API integration method can bypass the integrating organization's servers all together and transmit directly to the gateway.
- Reporting. What types of reporting are available? A good gateway integration will provide multiple ways to obtain reporting, e.g., online portal with dashboard views and search functionality. Reporting flows from the API connection might be batch or live communication via webhooks.
- Speed. Nobody wants a slow experience for posting a transaction and receiving confirmation. Look for sub-one second response times.
- Infrastructure. Are there co-locations? Is there power back-up capabilities? You should strive to make sure that your organization will be integrating to a gateway platform that has 99.9% uptime at a minimum
Payment Gateway Integrations FAQ's
- How long should a Payment Gateway Integration take? This depends on a number of factors. How much reporting functionality will you provide your user base? The more reconciliation insight you want to offer, the more dev time it will take. It also depends on the differing payment modalities. Are you credit card only? Will you offer an card updater option? ACH Payment Processing? All will affect dev time. A few days to a few weeks are likely
- Should I expect free tech support? Just as it should not cost you anything (but dev time) to integrate, you should also expect timely, free dev support
- Should I expect rev share from the gateway provider? In a word-yes. What that is varies from provider to provider but a definite yes.