OPay Payment Gateway
Welcome to the OPay Checkout (payment gateway) developer documentation hub! Here you’ll find comprehensive guides and documentation to help your platform provide seamless online payment experiences for your customers.
Use our Checkout payment solution in your app or website to simplify payment for your customers. Your customers can choose to pay from their cards, use QR payments, or with their OPay Wallet (interestingly, we have access to over 8 million and counting of those).
Mobile Integration (Android only)
The OPay Mobile Checkout SDK enables acceptance of payments via the OPay wallet and QR Code payment system. If the OPay App is not installed on a customer's device, the transaction will be processed via web view (HTML 5) within the Checkout SDK. The SDK is meant for making payments seamlessly with OPay regardless of OPay App being installed on the device or not.
This SDK handles 2 flows:
App Invoke Flow: In cases where the OPay App is also installed on the user device, an intent is called and the OPay App will be launched to complete the transaction and give the result back to your app.
Redirection Flow: In case OPay App is not installed, the Mobile Checkout SDK will open a webview (HTML 5 Checkout Page) to process transactions and give results to your app via the callback function.
Collect online payments with OPay Web Checkout (Web Integration)
OPay Checkout for your website provides a secure, PCI-compliant way to accept Debit/Credit card, QR payment, and OPay wallet payments from your customers.
To get started, you need to perform the following tasks in the order at which they’ve been specified:
- Register your merchant account: If you already have an OPay merchant account for your business, kindly login to your merchant dashboard open.opayweb.com to retrieve your staging credentials & whitelist your IPs. Else, you can create an account here.
- Generate your staging account credentials: These credentials would be retrieved from the merchant dashboard and they include your MID (Merchant ID which remains the same for both staging and production environments), secret key, public/private keys as well as authentication tokens where applicable.WarningFor security purposes, your keys need to be kept on the server-side and shouldn’t be shared with anyone. Do not commit your secret keys to git, or use them in client-side codes.
- Whitelist your IP Address(es): To increase the security of API calls between systems, you need to specify up to five different IP addresses that you would be accessing these APIs from.WarningEach IP address must be Internet-facing. To represent a range of IP addresses, use the asterisk (*) character.