The Payments Integration Checklist I Blog

There are plenty of things to check when starting out, but when it comes to payments, we’ve got you covered. Before anyone starts processing payments for live transactions, tests should be done to make sure things run smoothly. The last thing we want is for consumers to have error messages when trying to pay!

When it comes to payments, every integration is unique, so there is no “one fit’s all” checklist to make sure everything is taken care of. Depending on the software or application, the functions will probably be different, with various bells and whistles for each one. However, there are a few standard things to look for before going live.

Let’s start with the most common ways that software companies and applications enable payments for their customers.

Common Integrations

Security For Repeat Visitors

For software that operates on a subscription or recurring basis, why not make it so that people will not have to re-enter payment details for repeat purchases? Just as we create “profiles” for our LinkedIn or Facebook accounts, we can also create payment “profiles” for repeat users.

A payment profile consists of the information you would need to make a purchase - like billing address and card numbers. This information can then be stored securely on the account and re-used.

Custom Web Applications

For the more technology-savvy software companies out there, the option exists to connect directly with a payment provider via APIs. Using these APIs, partners can pass data from their custom application straight to the secure server of the payment provider.

Custom Checkout: One of the more popular web applications for integrating payments is Custom Checkout. Custom Checkout form is PCI compliant and can accept credit cards, wallets, and Interac. Key features include:

Tokenization: Custom Checkout uses secure tokens that are passed to the payment API to take a payment.

No Redirects: The required input fields are embedded directly into the software ore webpage.

Full Control: Custom Checkout gives the software provider full control over the UI/UX experience.

Knowledge and understanding of coding languages is definitely required to create a custom integration into a payments API. However, the result is a consistent payment experience throughout the software or application. As long as the developer documentation is available and easy to get through, a single integration enables access to multiple payment types.

Testing Integrations

Chances are, regardless of integration, your customers are probably going to be accepting credit cards. You want to make sure those cards process correctly, the proper notifications are in place, and that fraud protection measures are in place.

How do you make sure your customers are set up for success?

Test Cards: Most payment processors will provide a list of test cards that can be run through before going live. These test cards are a great asset to make sure the process is running smoothly on a checkout page!

Payment Notifications: To be informed on payment statuses or other events, such as a refund request, software vendors need to ensure notifications are being sent.

Fraud Protection: Anti-fraud tools are essential for fighting fraud in online payments, but they aren’t always turned on right from the get-go. Make sure the proper tools, such as AVS and CVV, are required before going live.

Reporting & Reconciliation: Every business is going to want to see their reports, and understand how to reconcile their accounts. The main reports would be settlement details and reconciliation. Understanding how to settle an account is crucial for proper reconciliation. Software providers should ensure their customers understand the processes prior to going live.

If you are curious about what the process looks like with Bambora, set up a test account and find out! It’s totally free, and you will get a first-hand look at how payments are processed with us!