1. Test OAuth and RSA key
Retrieves an OAuth token, fetches the RSA public key, and validates that PHP can parse the key. This test does not initiate a payment.
2. Collection / Cash-In
Sends a collection request to the configured Airtel UAT endpoint.
/merchant/v1/payments/
RW / RWF
3. Disbursement / Cash-Out (v3)
Sends funds to the payee wallet using Airtel's documented v2 endpoint. Use only an Airtel-approved UAT test wallet.
/standard/v3/disbursements
4. Configuration diagnostics
These are non-secret settings loaded by Laravel.
- Environment
- UAT
- Base URL
- https://openapiuat.airtel.co.rw
- Country
- RW
- Currency
- RWF
- Collection endpoint
- /merchant/v1/payments/
- Transactions enabled
- Yes
- Message signing enabled
- Yes
- Configured RSA padding
- pkcs1
- HTTP timeout
- 30 seconds
Known connection results
- OAuth token endpoint: previously HTTP 200.
- RSA key endpoint: previously HTTP 200.
- Public key parsing: previously successful, 2048 bits.
- Collection: requires a successful provider API response.
5. How to diagnose a failed request
- HTTP 400 with ROUTER007: inspect API version and router access.
- Disbursement: use the v2 endpoint shown above and confirm PIN encryption and message-signing settings with Airtel.
- HTTP 200 with success false: inspect the provider's response code and result code.
- OAuth failure: inspect token endpoint status without exposing credentials.
- RSA validation failure: inspect the safe parsing error in Laravel logs.
- Unclear provider error: correlate the request ID with the server log.
Detailed server diagnostics are stored in storage/logs/laravel.log. Never show access tokens, client secrets, PINs, raw request signatures, or full encryption keys in this page.
CK SOFTWARE · Airtel Rwanda UAT diagnostic console. Keep this page behind authentication and do not expose it publicly.