Skip to main content

Payment integration

OPay Payment Gateway

Mobile money payments via OPay Online Gateway, using mutual RSA-encrypted and RSA-signed request/response payloads. Common in Uganda and Nigeria.

Read the payment gateway setup guide

Supported markets

  • Uganda
  • Nigeria

Setup guidance

  1. Obtain your clientAuthKey from the OPay merchant dashboard.
  2. Generate an RSA key pair (1024-bit). Register the public key with OPay via the merchant dashboard, and register the callback/webhook URL below at the same time.
  3. OPay will give you their own RSA public key in return - paste it below alongside your own private key. Both keys are required: requests are RSA-encrypted with OPay's public key and signed with your private key; OPay's webhooks are the reverse.
  4. Use sandbox base URL for testing before production.

Configuration requirements

Enter these values in the matching gateway settings. Obtain credentials from the provider and keep them private.

Client Auth Key Required
Your RSA Private Key Required
Your own RSA private key (PEM format) - used to sign requests and decrypt OPay's responses/webhooks. Never share this with anyone, including OPay.
OPay's RSA Public Key Required
OPay's RSA public key (PEM format), given to you during merchant onboarding - used to encrypt requests and verify OPay's responses/webhooks.
API Base URL Required
Environment Required
Currency Required
Callback URL Optional