Test in Sandbox

On this page:

Overview

You can use one of our Sandbox accounts in our TEST environment to test our REST API even before you have created an account! To test your failure pages use a Test Card. The test will always return an OK response and an Authorisation Code. All other card numbers will be declined.

Important: Never use real card details to test your integration!

Sandbox Profiles

Choose from two sandbox test profiles:

Basic Profile

By default, all AVS and CV2 and 3D Secure checks are turned off. You can test most of our PI examples using this profile.

vendorName: sandbox
integrationKey: hJYxsw7HLbj40cB8udES8CDRFLhuJ8G54O6rDpUXvE6hYDrria
integrationPassword: o2iHSrFybYMZpmWOQMuhsXP52V4fBtpuSDshrKDSWsBY1OiN6hwd9Kb12z4j5Us5u

Extra Checks Profile

The extra checks profile account has strict AVS and CV2 checks and 3D Secure authentication enabled by default.

  • All transactions failing to pass AVS or CV2 checks are rejected.
  • Successful transaction registration will result in a request for 3D Secure authentication.
vendorName: sandboxEC
integrationKey: dq9w6WkkdD2y8k3t4olqu8H6a0vtt3IY7VEsGhAtacbCZ2b5Ud
integrationPassword: hno3JTEwDHy7hJckU4WuxfeTrjD0N92pIaituQBw5Mtj7RG3V8zOdHCSPKwJ02wAV

Passing AVS Checks

To pass the AVS checks you must provide the following details in the transaction thebillingAddress object:

"address1": "88"
"postalCode": "412"

Passing CV2 Checks

To pass the CV2 checks you must provide the following securityCode (the card CVV or CV2) when creating a card identifier:

"securityCode": "123"
Note: To override the default security settings, use the applyAvsCvcCheck and apply3DSecureproperties when posting to the transactions endpoint.

Postman Collection

If you would like to test the API quickly, we recommend using Postman. To get you started faster, we have created this collection that you can simply import into Postman.

Magic CardHolder Values

The following table lists our magic CardHolder values. When you test your Opayo Pi transaction request, these simulate 3D-Authenticated transaction responses.

 

 

Magic Value

3DSecureStatus

3D Secure Rule

Description

SUCCESSFUL

OK

Passes all rules

Returned for a frictionless flow where authentication is successful.

NOTAUTH

NOTAUTHED

Accept 3d auth failure

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.

NOTENROLLED

NOAUTH

Accept card not in scheme

Authentication could not be performed

PROOFATTEMPT

ATTEMPTONLY

Passes all rules

The cardholder attempted to authenticate themselves, and the process did not complete. A CAVV is returned and this is treated as being successfully authenticated.

REJECT

NOTAUTHED

Rejects before rulebase check

Authentication rejected by Issuer.

TECHDIFFICULTIES

INCOMPLETE

Accept issuer not in scheme

3D-Secure authentication was unable to complete. No authentication occurred.

ERROR

ERROR

Accept MPI failure

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. It can also result if you have not submitted the creq to the ACSURL within thirty seconds, or your customer has not entered 2FA on the ACS’s authentication page within ten minutes.

Test Address Values

Test your Rule Base and fraud-specific code by omitting the following codes:

  • billingAddress.address1 =  88
  • billingAddress.postalCode = 412

Test Payment Cards

You can use the following Test Cards with:

  • Any expiryDate up to today's date
  • The CVV of 123 (1234 for Amex cards).

Available test payment cards for 3D Secure testing

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

Test 3D Secure Passwords

 

Value

Description

challenge

Successful authentication. (All other phrases will fail authentication).

 

 

Simulate a 'Declined by the bank' response

To simulate a 'Declined by the bank' response, use a test card from the following table. Always use the CVV of 123.

Cards simulating a 'Declined by the bank' response

Payment Method

Card Number

Card Type

CVV Value

Visa

4929602110085639

Visa

123

MasterCard

5403814948608092

Mas

123

    Support

    Email the Opayo Support team for help with your debugging issues.