Test cards

To check the validity of the technical integration and different user scenarios for card payments, you can execute test payments in the test projects using test cards.

With test cards, the processing scenario is selected based on the card number. Other parameters, such as payment amount, cardholder name, or verification code, can take arbitrary values, but they must be specified in the correct format. For example, the card expiry date cannot predate the payment date. The followings test cards are currently supported in the payment platform.

Table 1. Test cards for processing scenarios without performing 3‑D Secure authentication
Card	Payment system	Status	Notes
`4000000000000077`	Visa	`success`
`4111111111111111`	Visa	`decline`
`4000000000000135`	Visa	`decline`	Payment was declined due to insufficient funds on the card, error code `10105`
`4000000000000119`	Visa	`success`	Payment to register a COF purchase
`4000000000000119`	Visa	`decline`	Debit operation performed as part of the registered COF purchase was declined
`4539121411168251`	Visa	`decline`	Payment was declined due to a delay in request processing by the issuer

Table 2. Test cards that support 3‑D Secure 1
Card	Payment system	Status
`4314220000000056`	Visa	`success`
`4006260000000014`	Visa	`success`
`4314220000000072`	Visa	`decline`
`4314220000000098`	Visa	`decline`
`5413330000000019`	Mastercard	`success`
`5413330000000035`	Mastercard	`decline`
`5413330000000092`	Mastercard	`decline`

Table 3. Test cards that support 3‑D Secure 2
Card	Payment system	Status	Notes
`4314220000000056`	Visa	`success`	Challenge flow when the ACS page is displayed for entering the code
`4012000000020089`	Visa	`decline`	Challenge flow when the ACS page is displayed for entering the code
`4477000000000006`	Visa	`success`	Frictionless flow
`4012000000020063`	Visa	`success`	Frictionless flow when 3‑D Secure 2 fails and the 3‑D Secure 1 authentication is performed instead
`4344693136092508`	Visa	`success`	Challenge flow when 3‑D Secure 2 is not supported by the issuer and 3‑D Secure 1 authentication is performed instead
`4165519761269614`	Visa	`decline`	Challenge flow when 3‑D Secure 2 is not supported by the issuer and 3‑D Secure 1 authentication is performed instead
`4331289925608649`	Visa	`decline`	Frictionless flow when 3‑D Secure 2 fails and the 3‑D Secure 1 authentication is performed instead
`4383604346807330`	Visa	`decline`	Challenge flow when 3‑D Secure 2 fails and the 3‑D Secure 1 authentication is performed instead
`5413330000000019`	Mastercard	`success`	Challenge flow when the ACS page is displayed for entering the code
`5544330000000045`	Mastercard	`decline`	Challenge flow when the ACS page is displayed for entering the code
`5252000000000004`	Mastercard	`success`	Frictionless flow
`5544330000000029`	Mastercard	`success`	Frictionless flow when 3‑D Secure 2 fails and the 3‑D Secure 1 authentication is performed instead
`5426257498841734`	Mastercard	`success`	Challenge flow when 3‑D Secure 2 fails and the 3‑D Secure 1 authentication is performed instead
`5722753235016359`	Maestro	`decline`	Challenge flow when 3‑D Secure 2 fails and the 3‑D Secure 1 authentication is performed instead

In additional to testing card payments, in the payment platform are supported capabilities to testing alternative methods. For more information, see Testing. Additional questions about testing payments can be addressed to ECommPay technical support.