Testing Your Integration
Everything you need to know to test your Wajub integration before going live.
Testing your integration is a critical step before processing real payments. Wajub provides a complete sandbox environment, predefined test scenarios, and tools to validate your webhooks — without risking a single franc.
What you can test
- All payment methods: MTN MoMo, Orange Money, Wave, Airtel, bank cards, transfers.
- All transaction statuses:
pending,complete,failed,canceled,refunded. - Webhooks: signature, retries, normal events, and errors.
- Transfers and push payments: outgoing payouts to Mobile Money wallets.
- Error cases: insufficient funds, invalid number, provider timeout, bank rejection.
Use Konsole alongside
Konsole is your test cockpit: inspect each request in API Logs, resend a webhook delivery in Webhooks, and see which provider a test payment was routed to in Routing Log.
The sandbox environment
The sandbox is an isolated environment, functionally identical to production but with no
financial consequence. You access it with a pk_test.… key (and a sk_test.… secret key
for sensitive operations).
Never mix keys
A pk.… key triggers real debits. Keep your production keys
strictly out of test code.
Where to start?
- Sandbox mode — get your test keys and understand the differences with production.
- Test scenarios — simulate all possible cases (success, failure, timeout…).
- Test webhooks — validate your receiving endpoint and signature verification.
Test lifecycle
1. Get your test keys in Dashboard > Developers > API Keys
2. Initialize a payment with pk_test.…
3. Choose a scenario (test number or card)
4. Check the result in Konsole > API Logs and Konsole > Routing Log
5. Verify that your webhook was correctly received and processed server-side
6. Iterate: error cases, retries, timeouts…