Overview
RohoPay supports Visa and Mastercard payments. All card transactions go through 3D Secure (3DS) authentication — the bank’s hosted verification page — for maximum approval rates and chargeback protection.How Card Payments Work
Endpoint
Unlike mobile money endpoints, the card checkout endpoint authenticates via
api_key in the request body rather than the Authorization header. This allows client-side checkout flows.Request Body
Your RohoPay API key (test or live). Provided in the body to support browser-side checkout forms.
Amount in smallest currency unit (e.g.,
10000 for UGX 10,000).Currency code. Accepted:
UGX, KES, TZS, RWF.Cardholder’s full name.
Cardholder’s email address.
Payment description for the merchant dashboard.
URL the user is redirected to after 3DS completes (success or failure).
16-digit card number without spaces or dashes.
Card expiry in
MM/YY format (e.g., 10/26).3-digit CVV / security code on the back of the card.
Example Request
Successful Response
payment_url immediately. Do not store or display this URL — it is a one-time-use 3DS session link.
Supported Card Brands
| Brand | Prefix | Notes |
|---|---|---|
| Visa | 4 | Visa Verified (3DS) |
| Mastercard | 51–55 / 2221–2720 | Mastercard SecureCode (3DS) |
Next Steps
3D Secure Flow
Understand the full redirect flow and how to handle the return URL.
Test Cards
Use test card numbers to simulate approvals and declines.