Global Payments test cards

Use these details to try payments in a Global Payments sandbox (test) account. They work only in the sandbox: never use them in live, and never put real card or bank details into a sandbox.

To try 3D Secure, it has to be switched on both in the Global Payments connection settings and on your Global Payments account (see Connecting Global Payments).

How to choose a test result

The card number sets the result. Any cardholder name, security code and future expiry date will do (Test Cards).
The 3D Secure cards give their results only when Enable 3D secure is switched on in the Global Payments connection settings here and Global Payments has switched 3D Secure on for your account (Connecting Global Payments). We use 3D Secure only when a customer pays online with a new card, so enter the card number in the checkout: phone (MOTO) payments and saved cards skip it.
We go ahead with a payment only when 3D Secure authentication succeeds or is attempted (Test Cards: 3D Secure 2). We decline the other results (authentication failed, rejected by the issuer, couldn’t be performed) with “3D Secure authentication failed”, without asking Global Payments to authorise the payment.
For SEPA, pay in euros (EUR), with Enable SEPA switched on in the Global Payments connection settings here and SEPA switched on for your Global Payments account (Connecting Global Payments). Global Payments’ page doesn’t list SEPA test bank accounts, so use the ones in SEPA Direct Debit below. The checkout asks for the account holder name: our tests use an ordinary first and last name.

Cards

Use any cardholder name, any security code and any future expiry date.

Successful payments

Card	Number	Notes
Visa	`4263 9700 0000 5262`
Visa	`4111 1111 1111 1111`	Used in our own tests
Mastercard	`5425 2300 0000 4415`
American Express	`3741 010000 00608`
Diners Club	`3625 6000 0007 25`
Discover	`6011 0000 0000 0087`
JCB	`3566 0000 0000 0000`

Declines and errors

The code in brackets is Global Payments’ result code. Global Payments lists a card for each of these results for Mastercard, American Express, Diners Club, Discover and JCB too, on its Test Cards page.

Number or trigger	Result
`4000 1200 0000 1154`	Declined by the bank (101)
`4000 1300 0000 1724`	Declined: referral B (102)
`4000 1600 0000 4147`	Declined: referral A, card reported lost or stolen (103)
`4009 8300 0000 1985`	Error: communication error (200)
`4242 4200 0000 0091`	Declined: strong customer authentication required (111)
`5114 6100 0000 4778`	Mastercard. Declined by the bank (101)

3D Secure

Global Payments’ test cards for 3D Secure 2 cover Visa and Mastercard.

Number	Result
`4222 0000 0628 5344`	Visa. Frictionless: authenticated
`4222 0000 0521 8627`	Visa. Frictionless: authentication attempted but not successful; Global Payments says the payment still goes ahead
`4222 0000 0214 4131`	Visa. Frictionless: authentication failed
`4222 0000 0727 5799`	Visa. Frictionless: rejected by the issuer
`4222 0000 0888 0910`	Visa. Frictionless: authentication couldn’t be performed
`4222 0000 0122 7408`	Visa. Challenge
`5354 5600 0000 0004`	Mastercard. Frictionless: authenticated
`5580 3648 7495 8322`	Mastercard. Frictionless: authentication attempted but not successful
`5540 0105 8539 7800`	Mastercard. Frictionless: authentication failed
`5588 3121 9436 2669`	Mastercard. Frictionless: rejected by the issuer
`5520 6802 1189 1022`	Mastercard. Frictionless: authentication couldn’t be performed
`5506 8744 9668 4651`	Mastercard. Challenge

SEPA Direct Debit

Global Payments’ Test Cards page doesn’t list SEPA test bank accounts. Our own tests use these with Global Payments’ sandbox.

IBAN	Result	Notes
`DE12 5001 0517 0648 4898 90`	The customer is sent to Global Payments to confirm the payment, which then stays pending until Global Payments confirms it	Used in our own tests
`BE71 0961 2345 6769`	The same: sent to Global Payments, then pending. Our tests also save this account and take a payment from it	Used in our own tests

Was this page helpful?