Documentation
Accept payments through one API
Tunnel sits in front of providers like Paystack and Flutterwave. You send one unified collection request; Tunnel routes using your rules, performs the charge on the selected PSP with your credentials, and returns a normalized response (plus optional raw provider payload).
What you integrate against
POST /v1/collections using the unified request/response contract (major-unit amounts, status + nextAction). Responses still sit in the Tunnel envelope (success, data, meta); the selected provider’s raw body is in data.raw.Base URL
https://xv9ni4gwk9.execute-api.us-east-1.amazonaws.com/dev/v1Every response looks like this
Success and error responses share one envelope so your client code stays simple.
{
"success": true,
"data": { },
"meta": {
"requestId": "req_abc123",
"timestamp": "2026-07-31T12:00:00.000Z"
}
}{
"success": false,
"error": {
"code": "INVALID_REQUEST",
"message": "Human-readable description"
},
"meta": {
"requestId": "req_abc123",
"timestamp": "2026-07-31T12:00:00.000Z"
}
}Integration path
- 1. Create a workspaceSign up and open the dashboard.
- 2. Connect a providerAdd Paystack or Flutterwave test keys while the dashboard is in Test Mode.
- 3. Create an API keyDashboard → API Keys → create
sk_test_…(thensk_live_…when you go live). - 4. Charge and verify
POST /v1/collectionswith your payment details; Tunnel routes and charges the PSP. Redirect whennextActionasks for it, then verify or wait for a webhook.
Guides in this docs set
Get an API key and send it
One request, any provider
Ask the provider for the final status
Complete a payment inside your own page
A one-time account for the customer to pay into
A code the customer dials
Approve from a wallet
Debit a Nigerian bank account
Send the customer to OPay to approve
A QR code any Nigerian bank app can scan
Hear when a payment settles or fails
Status codes and what to do about them