Skip to content
Last updated

Test Cards

Overview

You can use the following test card numbers to simulate different payment scenarios when testing your integration with the Ryft SDK.

These card numbers are designed to trigger specific responses from the payment gateway, allowing you to verify that your application handles various outcomes correctly.

3D-Secure Test Cards

The following test card numbers can be used to simulate different 3D-Secure authentication scenarios, such as:

  • Frictionless: authentication approved without challenge;
  • Frictionless with 3DS Method: authentication approved after 3DS method;
  • Challenge: immediate challenge;
  • 3DS method, then challenge: authentication after 3DS method, then challenge.
SchemeCard Number3DS flow
Visa4012000000060085Frictionless
Visa40663300000000043DS method frictionless
Visa49387300000000013DS method challenge
Visa49181900000000023DS challenge
Mastercard5555555555554444Frictionless
Mastercard54545454545454543DS method frictionless
Mastercard52000000000010213DS method challenge
Mastercard52957959768593953DS challenge
Amex343434343434343Frictionless
Amex3714496353984313DS method frictionless
Amex3742454554001263DS method challenge
Amex3741010000006083DS challenge

Declined Payments

The following cards can be used to test transactions that fail after reaching the card issuer.

Please note that these card numbers need to be used in conjunction with the associated CVV codes to simulate the specific decline reasons.

SchemeCard NumberCVVDescription
Visa4000000000001000100Declined due to insufficient funds
Mastercard5425233430109903100Declined due to insufficient funds
Visa4000000000001000001Declined due to incorrect CVV
Mastercard5425233430109903001Declined due to incorrect CVV
Visa4000000000001000222Declined due to issuer reason "Do not honour"
Mastercard5425233430109903222Declined due to issuer reason "Do not honour"
Amex3782822463100051000Declined due to insufficient funds