End to End Testing
We deliver a comprehensive sandbox staging environment for our merchants to use while building up their integration. You can use our given set of test cards to ensure the capability of your integration in dealing with different payment processing use cases.
Introduction
For the sake of our merchants convenience and to ensure the integrity of every merchant's integration with OPay, we provide a comprehensive sandbox staging environment. You may use OPay staging environment while building up your integration or if you may wish to explore OPay's newly added features. You will have the capability to simulate purchases using your own OPay integration in staging mode. This allows you to ensure the integrity of your integration logic before you switch into production mode without having to make real purchases. We provide a set of cards where you can test different payment use cases. Note that you can only use these cards for testing within your OPay account and not for real purchases. Similarly, genuine card numbers will not be recognized within your staging environment. To simulate payments, use any of the following test card details provided in the table below.
Card Schemes
| Card type | Number | CVV | Expiry Date | Description |
|---|---|---|---|---|
| Visa | 4508 7500 1574 1019 | 100 | 05/25 | This card will always return successful payment |
| Visa | 4012 0000 3333 0026 | 100 | 05/25 | This card will always return successful payment |
| Visa | 4012 0000 3333 1123 | 100 | 05/25 | This card will always return pending payment |
| Mastercard | 5123 4500 0000 0008 | 100 | 05/25 | This card will always return successful payment |
| Mastercard | 2223 0000 0000 0007 | 100 | 05/21 | This card will always return failure due to invalid expiry date |
| Mastercard | 5111 1111 1111 1118 | 100 | 05/25 | This card will always return failure due to insufficient fund |
| Mastercard | 2223 0000 0000 0023 | 100 | 05/25 | This card will be accepted for any amount between 0 and 100 transactions, otherwise, it will be rejected. |
| Meeza | 5078 0300 1111 0007 | 123 | 01/39 | This card will always return successful payment |
| Meeza | 5078 0300 2222 0001 | 123 | 01/39 | This card will always return failure due to invalid expiry date |
| Meeza | 5078 0300 3333 0005 | 123 | 01/39 | This card will always return failure due to insufficient fund |
Bank Installment
| CARD TYPE | NUMBER | CVV | EXPIRY DATE | DESCRIPTION |
|---|---|---|---|---|
| MasterCard | 5393 9900 0000 0006 | 100 | 05/25 | This card will always return successful payment |
| MasterCard | 5441 1100 0000 0003 | 100 | 05/25 | This card will always return failure payment due to invalid expiry date |
Mobile Wallet
| WALLET ACCOUNT | DESCRIPTION |
|---|---|
| 01066668888 | This wallet account will always return successful payment, the callback will be sent automatically after 1 minute |
| 01077779999 | This wallet account will always return failure payment, the callback will be sent automatically after 1 minute |
ValU Installment
| ValU ACCOUNT | OTP | DESCRIPTION |
|---|---|---|
| 01066668888 | 123456 | This ValU account and OTP will always return successful payment |
| 01066668888 | 111111 | This ValU account and OTP will always return failure payment |
| 01066668888 | 222222 | This ValU account and OTP will always return invalid OTP or pending status |
Reference Code
Reference Code Payin Verification
Shahry Installment
| Shahry ID | Order Token | DESCRIPTION |
|---|---|---|
| 01066668888 | 123456 | This Shahry ID and Order Token will always return successful payment |
| 01022224444 | 111111 | This Shahry ID will always return ‘Shahry ID does not exist’ |
| 01066668888 | 222222 | This Order Token will always return ‘Invalid Order Token’ |
| 01066668888 | 000000 | This Order Token will always return failure payment |
