As integrated payments become a “must-have” rather than a “nice-to-have”, more merchants are working to embed the credit card processing function into their existing applications. This allows for faster transaction processing, more visibility, better reporting, and even an improved customer experience. However – as with most IT modernization efforts – it doesn’t happen overnight.
As Curbstone’s Product Manager, Alan O’Guin, sees it, there are three maturity levels for integrated payments.
No integration at all. Payments are disconnected from your critical business systems, such as your ERP or order entry application. Sales reps, customer service teams, or phone agents have to open an entirely separate program to enter a customer’s credit card information. Reporting requires various data downloads and manual reconciliation.- Loose integration. Transactions are largely sent via API calls. These calls may return some information about the transaction that can then be stored in your existing systems. However, if reporting is available, it is not native to your IBM i. You won’t have a local transaction file that contains all your transactions; there may be some method for storing cards on file, but the corresponding tokens won’t be stored locally either. Meanwhile, there’s little to no built-in automation.
- Tight/seamless integration. You have direct integration with your order entry and financial systems. You also have IBM i software installed on your system; this contains your physical files, libraries, native reporting, test utilities, and working example programs. All payment transactions are recorded in a physical file on your IBM i; this is a key feature as it allows you to leverage your existing resources for development and research. Similarly, you have complete control over your payment operations and their sequence. Instead of having to work your business processes into the limitations of a non-integrated system, you dictate what happens and when. Similarly, you can automate key payment processing functions, like placing cards on file or running zero-dollar authorizations. Lastly, cards on file are stored in a digital wallet on your IBM i, where they’re easily available to your order entry application.
No integration at all. Payments are disconnected from your critical business systems, such as your ERP or order entry application. Sales reps, customer service teams, or phone agents have to open an entirely separate program to enter a customer’s credit card information. Reporting requires various data downloads and manual reconciliation.As O’Guin explains further:
“Seamless integration with your payment software should be the goal – and really, it should be viewed as a requirement. In other applications, you wouldn’t accept fractured systems, data silos, and disconnected processes. Payments should be held to the same standard as other essential business components – and anything else should be viewed as a liability.”
How to Achieve a Seamless Payment Integration with the Applications You Run on Your IBM i
At Curbstone, we make seamless integration simple. Our payment processing software offers integrated credit card processing functionality for all the ways you do business: online, over the phone, or in person. Test utilities and working examples make the process straightforward for your existing RPG resources; because our programs are written in the language you already know and understand, there’s no need for complicated trial and error.
If you’re ready to move from a loose integration – or no integration at all – to a seamless IBM i payment integration that delivers faster transactions, more visibility, and time-saving automation options, let us know and we’d be happy to help you explore your options.
