In this section:
Test Payment Cards
To test your failure pages use a Test Payment Card. The test will always return an OK response and an Authorisation Code. All other card numbers will be declined. Always use the CVV of 123 (1234 for Amex cards).
Payment Method |
Card Number |
Card Type |
---|---|---|
Visa |
4929000000006 |
Visa |
Visa |
4929000005559 |
Visa |
Visa |
4929000000014 |
Visa |
Visa |
4929000000022 |
Visa |
Visa Corporate |
4484000000002 |
Visa |
Visa Debit |
4462000000000003 |
VisaDebit |
Visa Electron |
4917300000000008 |
VisaElectron |
MasterCard |
5186150660000009 |
MasterCard |
MasterCard |
5186150660000025 |
MasterCard |
MasterCard |
5186150660000108 |
MasterCard |
MasterCard |
5186150660000207 |
MasterCard |
Debit MasterCard |
5185690060000001 |
DebitMasterCard |
Maestro (UK Issued) |
6759000000005 |
Maestro |
Maestro (German Issued) |
6705000000008 |
Maestro |
Maestro (Irish Issued) |
5185570760000008 |
Maestro |
Maestro (Spanish Issued) |
6766000000000 |
Maestro |
American Express |
374200000000004 |
AmericanExpress |
Diners Club / Discover |
36000000000008 |
Discover |
JCB |
3569990000000009 |
JCB |
Magic CardHolder Values
The following table lists our magic CardHolder values. When you test your Opayo Form hosted page, these simulate 3D-Authenticated transaction responses.
Magic Value |
3DSecureStatus |
Description |
---|---|---|
SUCCESSFUL |
OK |
Returned for a frictionless flow where authentication is successful. |
NOTAUTH |
NOTAUTHED |
Returned for a frictionless flow where authentication is unsuccessful. |
CHALLENGE |
Status=3DAUTH 3DSecureStatus=OK |
Returned for a challenge flow. The cardholder will be re-directed to the ACS to enter two-factor authentication. A CReq, VPSTxId, ACSURL and StatusDetail will also be returned. Once you re-direct to the ACSURL, entering the correct password displayed on the site will simulate a successful authentication, entering any other password will simulate an unsuccessful authentication. |
PROOFATTEMPT |
ATTEMPTONLY |
The cardholder attempted to authenticate themselves, and the process did not complete. A CAVV is returned and this is treated as being successfully authenticated. |
TECHDIFFICULTIES |
INCOMPLETE |
3D-Secure authentication was unable to complete. No authentication occurred. |
ERROR |
ERROR |
Simulates an error condition where 3D-Authentication cannot be performed due to data errors or service unavailability in one of the parties involved in the check. |
3D Secure Scenarios
You can enter the following characters into the password field to simulate different scenarios:
3DSv2
Value |
Description |
challenge |
Successful authentication. (All other phrases will fail authentication) |
Test Address values
Test your Rule Base and fraud-specific code by omitting the following codes:
- Billing Address 1: 88
- Billing Post Code: 412
The transaction will authorise and you will receive NOTMATCHED messages in the AVS/CV2 checks.
Support
Email the Opayo Support team for help with your debugging issues.