Show / Hide Table of Contents

Test Cards

These cards are for the development and test environments. They are not real cards and they do nothing in production.

Loop

The simulator processor ("Loop") decides the result from the card number. Visa style cards start with 4000, Mastercard style cards with 5100.

Result Visa Mastercard
Approved 4000000000000002 5100000000000008
Declined 4000000000000010 5100000000000016
Error 4000000000000028 5100000000000024
Approve only on the last merchant account (used to test the fallback between merchant accounts) 4000000000000036 5100000000000032
Error: the processor throws an exception 4000000000000044 5100000000000040
Approve after a 5 second delay 4000000000000051 5100000000000057
Approve after a 35 second delay 4000000000000069 5100000000000065
Approve after a 65 second delay (longer than most timeouts) 4000000000000077 5100000000000073
Ask the user: the simulator page shows Approve, Decline and Error buttons (async and hosted payments only) 4000000000000085 5100000000000081
Declined with a host code: the cents of the amount become the standard host code, for example 1.51 gives 51 4000000000000093 5100000000000099
Result from the cents (see below). The simulator sends the IPN notification at once and returns the cardholder to your returnUrl 4000000000000101 5100000000000107
Result from the cents. The simulator sends the IPN notification only: the cardholder is not returned (the page shows "IPN Only test case") 4000000000000119 5100000000000115
Result from the cents. The cardholder is returned first and the IPN notification follows later: after half a second for an approval, after 5 seconds for a decline or an error 4000000000000127 5100000000000123

For the three IPN cards the cents of the amount choose the result: 00 the simulator page with the three buttons, 01 approve, 02 decline, 03 error (any other cents also show the page). They are meant for async payments, where the simulator page and the IPN notification are in play. The IPN goes to the same host that received the simulator request.

Any other card is approved or declined from the cents of the amount:

Cents Result
00 Approve
01 Decline
02 Error
other Approve

An amount of 0 is a card check and is approved: see Sync Payment.

Wallets

A wallet payment (Wallets) on an account of the Dummy processor that takes wallets is answered at once. The card in the token is treated like a typed card, so the Loop cards above decide the result for a token made with them; the test cards of Google's own TEST environment are not in the list, so the cents of the amount decide:

Cents Result
01 Decline
02 Error
other Approve

The three IPN cards need the cardholder's browser and are not for wallet payments.

3D Secure

These are the Ravelin 3DS sandbox cards, used when 3D Secure is enabled on the account. Most fail the Luhn check, so they only work against the sandbox.

Card Number ARes transStatus After challenge Notes
4200000000000002 Y Frictionless success
4200000000000003 A Attempted
4200000000000004 C Y Challenge then success
4200000000000005 N Failed
4200000000000006 U Unavailable
4200000000000007 R Rejected
4200000000000008 C A
4200000000000009 C N
4200000000000010 C U
4200000000000011 C R
4200000000000012 Directory server error
4200000000000013 3DS server error
4200000000000014 C Y No 3DS Method
4200000000000015 C Y Challenge mandated
4200000000000016 C Y Out of band
4200000000000017 C N Out of band

Data only authentication:

Card Number Scheme
4508750015741019 Visa
5123456789012346 Mastercard
5149612222222229 Mastercard Identity Check

The challenge passcode is 1234.

Note

Which protocol version a card negotiates is decided by its ACS and directory server, not by us. See 3DS Api for the versions PayLolly supports.

In this article
Back to top Generated by DocFX