Getting Started
Welcome to the Payment Gateway API. This guide will help you get up and running with our payment processing platform in just a few steps.
Sign Up on the Dashboard
Start by creating an account on our merchant dashboard. You'll need to provide your business information, contact details, and banking information for settlement.
Go to DashboardGenerate Your API Keys
Once your account is set up, navigate to Settings → API Keys in the dashboard. Click "Generate New Key" to create your first API key. You'll be able to choose between:
- •Sandbox Keys: For testing your integration
- •Live Keys: For processing real payments
⚠️ Keep your API keys secure! Never share them publicly or commit them to version control.
Manage Multiple API Keys
You can generate multiple API keys for different purposes:
Different Applications
Generate separate keys for your web application, mobile app, and backend services for better organization and security.
Multiple Businesses
If you manage multiple businesses under the same account, generate dedicated API keys for each business. This keeps transactions organized and allows you to track revenue per business independently.
Separate Environments
Always use different keys for sandbox and production to prevent accidental charges during testing.
Start Integrating
Include your API key in the X-API-Key header for every API request. All requests must be made over HTTPS.
Here's a quick example:
🔐 Authentication Guide
For complete details on authentication, security best practices, and how to manage your API keys, visit our Authentication guide:
View Authentication Guide →Available API Endpoints
Need Help?
Our support team is available 24/7 to help you with integration questions and technical issues.
Contact SupportPayment Matrix Reference Specs
Execute live tests against specific routing definitions. Use the toggle buttons inside the terminal frames to inspect alternate structural responses.
/v1/payments/card/initiate1. Initiate Card Payment (with 3DS)
Verify authorization layers. Production payloads must follow precise protocol arrays to pass modern network orchestration gateways securely.
Required Headers
{
"amount": 2500,
"currency": "GHS",
"email": "customer@example.com",
"card": {
"number": "4000123456789010",
"expiry_month": "12",
"expiry_year": "2028",
"cvv": "123"
},
"redirect_url": "https://yourdomain.com/checkout/verify"
}{
"status": "success",
"transaction_reference": "TXN-CARD-90811A",
"amount": 2500,
"currency": "GHS",
"message": "Payment authorized successfully."
}/v1/checkout/sessions2. Create Hosted Checkout Session
Verify authorization layers. Production payloads must follow precise protocol arrays to pass modern network orchestration gateways securely.
Required Headers
{
"amount": 150,
"currency": "USD",
"merchant_reference": "INV-2026-004",
"customer": {
"email": "m.amoo@exxari.com"
},
"redirect_url": "https://yourdomain.com/success"
}{
"status": "success",
"session_id": "cs_live_9921c8b3f11a",
"checkout_url": "https://checkout.gateway.com/pay/cs_live_9921c8b3f11a"
}/v1/transactions/verify/TXN-ORD-771923. Verify Transaction Status
Verify authorization layers. Production payloads must follow precise protocol arrays to pass modern network orchestration gateways securely.
Required Headers
{
"status": "success",
"transaction_reference": "TXN-ORD-77192",
"amount": 500,
"currency": "GHS",
"channel": "mobile_money"
}/v1/payments/momo/charge4. Mobile Money Charge API
Verify authorization layers. Production payloads must follow precise protocol arrays to pass modern network orchestration gateways securely.
Required Headers
{
"amount": 80,
"currency": "GHS",
"phone_number": "0244123456",
"provider": "MTN"
}{
"status": "success",
"transaction_reference": "TXN-MOMO-10293",
"message": "Transaction completed instantly."
}/v1/refunds/initiate5. Execute Reverse / Refund Request
Verify authorization layers. Production payloads must follow precise protocol arrays to pass modern network orchestration gateways securely.
Required Headers
{
"transaction_reference": "TXN-CARD-90811A",
"amount": 2500,
"reason": "Customer order cancellation."
}{
"status": "success",
"refund_reference": "REF-88192-A",
"amount_refunded": 2500
}https://merchant-api.yourdomain.com/webhooks/payments6. Webhook Notification Event Structure
Verify authorization layers. Production payloads must follow precise protocol arrays to pass modern network orchestration gateways securely.
Required Headers
{
"event": "transaction.completed",
"created_at": "2026-05-30T08:39:00Z",
"data": {
"status": "success",
"amount": 2500,
"currency": "GHS"
}
}