Simulate bank transfers
The simulator works only in the test environment. No real money is moved, and it cannot be used with live (production) account numbers.
Pretend to be a customer paying by bank transfer, so you can see exactly what your system receives when a real payment arrives. No real money moves.
Sandbox only. It doesn’t accept Live account numbers.
When to use it
Any flow where a customer pays you by bank transfer into an account number you generated:
Persistent Payment Account
A permanent account number a customer can pay into at any time.
Payment request
A one-time account number for a specific payment or invoice.
Checkout gateway transfer
A one-time account number for a payment on Paga Checkout.
It’s especially useful for checking that:
- Your callback URL receives payment notifications.
- Your system credits the right customer with the right amount.
- Underpayments, overpayments and duplicate payments are handled the way you expect.
Before you start
- A Sandbox account on beta-business.paga.com.
- Your Sandbox API keys. See Get your API keys.
- A test account number from the API, for example from
registerPersistentPaymentAccountorpaymentRequest. - A callback URL set for your Sandbox business, so you receive the payment notification.
Testing on your own machine? Use a tunnelling tool such as ngrok so Paga can reach your local callback URL.
Simulate a transfer
Generate a test account number
Call the API in Sandbox and save the accountNumber in the response.
Open the simulator
Fill in the transfer details
| Field | What to enter |
|---|---|
| Recipient Paga account number | The test account number from step 1 |
| Amount | What the customer is sending, in Naira, e.g. 5000 |
| Currency | NGN |
| Sender bank | Access Bank |
| Narration (optional) | A short description, e.g. Invoice 1023 |
Select Trigger Deposit
The simulator behaves as though a real transfer just arrived.
Check your integration
Within a few seconds, a payment notification reaches your callback URL, the transaction appears in your Sandbox dashboard, and your system updates the customer’s balance, order or invoice.
Scenarios worth testing
| Scenario | How to simulate it | What to check |
|---|---|---|
| Exact payment | Send the amount requested | The payment is marked complete |
| Underpayment | Send less than requested | Partial payment is handled correctly |
| Overpayment | Send more than requested | The extra is handled as you intend |
| Repeat payment | Pay the same persistent account twice | Both payments are credited |
| Duplicate notification | Replay the same callback | The customer isn’t credited twice. De-duplicate on the transaction reference |
| Invalid account | Use an account number that doesn’t exist | The simulator shows an error and nothing reaches your callback |
Troubleshooting
No callback received
Check the callback URL is set for your Sandbox business, is publicly reachable, and returns HTTP 200 quickly.
Account number is invalid
Make sure it was generated in Sandbox, with the same business and keys you’re testing with.
Wrong amount in your system
Read the amount field from the notification, not a value saved from the original request.
Going live
Switch to Live keys and base URL
See Authentication for the Live base URLs.
Update your callback URL
Set it for your Live business in the business portal.
Make a small real transfer
Confirm everything works end to end before opening it to customers.
Need help? We’re here 24/7
Talk to our support team any time, or ask questions in the developer community.
Updated 12 days ago

