To test your integration without having to complete the WebPAY setup process or debit actual accounts, you can use our Sandbox. The Sandbox is an exact copy of the Production Environment, except that the merchant does not really exist and card accounts are not really debited. Find the details below:
Sandbox URLs
| URL | Description |
|---|---|
| https://sandbox.interswitchng.com/webpay/pay | Payment page |
| https://sandbox.interswitchng.com/webpay/api/v1/gettransaction.json | Transaction Confirmation Query (JSON) |
| https://sandbox.interswitchng.com/webpay/api/v1/gettransaction.xml | Transaction Confirmation Query (XML) |
Merchant details WebPAY
- WebPAY Demo Merchant
- This is the demo merchant’s name and is not required anywhere. FYI only
- 6205
- This is the Product ID (POST field product_id)
- 101
- This is the Payment Item ID (POST field pay_item_id)
Use the following as your MAC/Hash key
D3D1D05AFE42AD50818167EAC73C109168A0F108F32645C8B59E897FA930DA44F9230910DAC9E20641823799A107A02068F7BC0F4CC41D2952E249552255710F
Merchant details WebPAY DIRECT (With Payment Split Instruction)
- WebPAY DIRECT Demo Merchant
- This is the demo merchant’s name and is not required anywhere. FYI only
- 6204
- This is the Product ID (POST field product_id)
- 101
- This is the Payment Item ID (POST field pay_item_id)
Use the following as your MAC/Hash key
E187B1191265B18338B5DEBAF9F38FEC37B170FF582D4666DAB1F098304D5EE7F3BE15540461FE92F1D40332FDBBA34579034EE2AC78B1A1B8D9A321974025C4
Merchant details CollegePAY WEB
- CollegePAY Demo Merchant
- This is the demo merchant’s name and is not required anywhere. FYI only
- 6207
- This is the Product ID (POST field product_id)
- 103
- This is the Payment Item ID (POST field pay_item_id)
Use the following as your MAC/Hash key
CEF793CBBE838AA0CBB29B74D571113B4EA6586D3BA77E7CFA0B95E278364EFC4526ED7BD255A366CDDE11F1F607F0F844B09D93B16F7CFE87563B2272007AB3
Merchant details CollegePAY WEB (With Payment Split Instruction)
- CollegePAY Demo Merchant
- This is the demo merchant’s name and is not required anywhere. FYI only
- 6207
- This is the Product ID (POST field product_id)
- 101
- This is the Payment Item ID (POST field pay_item_id)
Use the following as your MAC/Hash key
CEF793CBBE838AA0CBB29B74D571113B4EA6586D3BA77E7CFA0B95E278364EFC4526ED7BD255A366CDDE11F1F607F0F844B09D93B16F7CFE87563B2272007AB3
Demo Card details
Please note, real Credit/Debit cards will not work on the Test Environment. To perform all your Test Transactions, kindly select one of the Test Cards cards below based on the scenario you’re testing for:-
This is the demo card with which you would always get a Approved Successful response
- 1.
- Success
- 6280511000000095
- Dec 2026
0000
123
- This is the demo card that would decline with ‘Z1′ and a response description of No Card Record. See the response codes page for more details
- 2.
- No Card Record
5061030000000000043
Oct 2018
1234
123
- This is the demo card that would decline with ‘Z1′ and a response description of Incorrect PIN. See the response codes page for more details
- 2.
- Incorrect PIN Card
5061030000000000035
Sept 2019
0000
123
- This is the demo card that would return with Insufficient Funds
- 3.
- Insufficient Funds
- 5061030000000000027
Sept 2019
1234 - 123
Heads up!
Since this is a demo merchant being used by everyone, you need to make sure your transaction reference (txn_ref) is unique by prepending something unique to the transaction reference.
For example Instead of XXXXXX, where X is a random integer from 1 – 9, you should use something like COMPNAMEXXXXX, DATETIMEXXXXX, TIMESTAMPXXXXX, etc.
COMPNAMEXXXXX – ABCLIMITED123495
DATETIMEXXXXX – 010120161130AM9999
TIMESTAMPXXXXX – 14685721698877998
Otherwise, you could use some GUID type system to generate a reference for your tests. We expect that when you move to production, your transaction references would most probably come from a database of some sort and would be unique.
6325