Test Data

October 09, 2026

Access a unified list of test card numbers so you can test your integration.

This page includes different test data for each payment method, so that you can use these to simulate different scenarios and ensure that your integration is performed as expected.

One-time card payments

Use the following data to test the reception of [one-time payments(https://docs.kushki.com/mx/card-payments/one-step-payments/accept-a-payment) by card.

Approved transaction

Card number: 5451951574925480.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (000) Approved Transaction

Declined transaction in token request

Card number: 4574441215190335.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (017) Declined transaction

Transaction rejected at payment request

Card number: 4349003000047015.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (017) Invalid card

Invalid card

Card number: 4349008516656431.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response:(019) Unsupported card

Insufficient funds

Card number: 4349001210846432.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (021)Insufficient funds

Invalid CVV

Card number: 4349003243371321.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (022) Unable to verify CVV

Blocked card

Card number: 4349001386781322.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (023) Card blocked by bank

On-demand payments

Send the following data to test the creation of a subscription and the subsequent execution of the on-demand charge.

Transaction approved

Card number: 5451951574925480.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (000) Approved Transaction

Declined transaction in token request

Card number: 4574441215190335.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (017) Declined transaction

Transaction rejected at payment request

Card number: 4349003000047015.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response:(017)Invalid card

Invalid card

Card number: 4349008516656431.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response:(019) Unsupported card

Insufficient funds

Card number: 4349001210846432.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (021)Insufficient funds

Invalid CVV

Card number: 4349003243371321.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (022) Unable to verify CVV

Blocked card

Card number: 4349001386781322.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (023) Card blocked by bank

OTP Payments

Test the payment reception with OTP validation by sending the following data:

Transaction approved

Card number: 5451951574925480.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (000) Approved Transaction

Declined transaction in token request

Card number: 4574441215190335.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (017) Declined transaction

Card subscription

Use the following data to test the subscription of a card.

Transaction approved

Card number: 5451951574925480.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (201) Created subscription.

Transaction declined at token request

Card number: 4574441215190335.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (017) Declined transaction

Wire transfers

Use the following identification numbers in the documentNumber field when requesting the transfer in token to simulate different responses. You can check the transaction result by calling the status query endpoint.

Approved transaction

Identification number: 123456789 (or any number other than 999999990).

Response: status: approvedTransaction, responseCode: OK

Declined transaction

Identification number: 999999990.

Response: status: declinedTransaction, responseCode: FAILED

Right after init, the first status query returns initializedTransaction. Wait a few seconds and query again to see the final status. The decline is only visible in the status query.

Payment Distribution

Use the following identification numbers when requesting the transfer out token to simulate different responses. You will be able to validate the transaction response by calling the status query endpoint.

Approved transaction

Account number: 646180110400000007.
Identification number: 123456789.
Identification type: CURP or RFC.
Account type: CB.

Cancelled transaction

Account number: 646180206800000003.
Identification number: CADM9108029F4.
Identification type: CURP or RFC.
Account type: CB.

Returned transaction

Account number: 646180206800000003.
Identification number: CADM9108029G5.
Identification type: CURP o RFC.
Account type: CB.

Plugins

To test the card payment reception using the available plugin for Shopify, you can use the following credentials:

Transaction approved

Card number: 5451951574925480.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (000) Approved Transaction

Declined transaction in token request

Card number: 4574441215190335.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (017) Declined transaction

Transaction rejected at payment request

Card number: 4000001278960006.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.

Response: (006) Rejected transaction