1. Quick Start
Kushki Docs
English
  • Español
  • English
  • Home
  • Quick Start
    • Frequently Asked Questions
    • Moving to Production
    • Policy for Important API Changes
    • Test Data
    • Error Codes
    • Latest Features
  • Payment Glossary
    • Payments Glossary
  • One-time card payments (Online)
    • Supported card brands
    • Functionalities by business model
    • How do third party commissions work?
    • Integration guide Third Party Commissions
    • Network Tokens
    • One-step Payments
      • How do Card Payments Work?
      • Accept a Card Payment
      • Direct charge (without token)
      • Accept One-Time Payments with OTP
      • OTP Authentication Error Codes
      • Error codes for single card payments
    • Two-steps Payments
      • How do single payments with authorization and capture work?
      • Receive payments with authorization and capture
    • Refunds
      • Returns, cancellations, and refunds
    • 3DS Authentication
      • Introduction to 3DS
      • 3DS API integration
      • 3DS integration with kushki.js library
      • 3DS API integration plus kushki.js library
      • 3DS Error Codes
    • Apple Pay Payments
      • Apple Pay Configuration
      • Apple Pay Sandbox testing
  • Recurring Card Payments (Online)
    • Functionalities by business model
    • External subscriptions to Kushki
    • Authenticate your subscriptions with 3DS
    • Accept one-click payments with 3DS
    • Error codes in recurring charges
    • Apple Pay for Subscriptions
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Create a recurring charge
      • Manage your Scheduled Charges
    • OneClick Payments
      • Accepting One-Click Payments
      • How do OneClick payments with authorization and capture work?
      • Receive one-click payments with authorization and capture
  • Card-present payments
    • Card present payments
    • Accept card present payments
    • Test data
    • Webhooks for card present
    • Cloud Terminal API
      • Cloud terminal API overview
      • Take payments
      • Cancel a payment request
      • Check the status of a payment request
      • How to print a customized ticket?
    • App-to-app
      • App-to-app overview
      • Take payments
    • Terminal SDK
      • Terminal SDK Introduction
      • Take payments
    • Raw card-present API
      • Raw card-present API overview
      • Cryptographic key exchange
      • Sample script to encrypt information
      • Take Payments
      • Frequently Asked Questions
      • Error codes for card-present transactions
    • Transactions
      • Transactions
      • Cancel payments
    • Kushki One
      • First Steps
      • Autenticación y Cifrado de Requests
      • Accept payments with Kushki One
      • Amount Format
      • Async services and webhooks
      • Printing on SmartPOS terminal
      • Unified Error Catalog — Kushki ONE Connect
    • Kushki One Payment App
      • Overview
      • Process a payment
      • Split payment on the terminal
      • Refunds and PreAuth & Capture
      • Review Your Transactions
      • Terminal Setup
  • Wire Transfers
    • How do Payments by Wire Transfers Work?
    • Banks and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
  • Money Disbursement
    • Wire Transfer
      • How Does a Payment Distribution by Wire Transfer Work?
      • Payment Distribution to Bank Accounts
      • Error codes for transfer dispersions
  • Payment Links
    • Smartlinks
  • Plugins
    • Shopify
      • Shopify
      • Plugin Operation
    • VTEX
      • VTEX Integration Guide
  • Payment forms and buttons
    • Kajita
      • How Does it Work?
      • Payment Kajitas
    • Payment Button
      • Overview
      • Generate a payment button
  • Branch Offices Management
    • How to Onboard Submerchants via API
  • Notifications
    • Webhooks
    • Good Practices
    • Check your Webhooks
    • One-time Payments Webhooks
      • Webhook for One-Time Payments made with a card
      • Webhook for One-Time Payments by Wire Transfer
      • Webhook for One-Time Payments in Cash
    • Recurring Payments Webhooks
      • Webhook for Recurring Payments Made with Card
    • Payment Distribution Webhooks
      • Webhook for payment disbursement through wire transfer
    • Payment button Webhooks
      • Webhooks with Payment Button
    • Smartlinks Webhooks
      • Webhooks with Smartlinks
    • Refunds Webhooks
      • Webhook for Voids and Refunds
      • Chargeback Webhooks
HomeMexico 🇲🇽
Ecuador 🇪🇨Chile 🇨🇱Colombia 🇨🇴Peru 🇵🇪
HomeMexico 🇲🇽
Ecuador 🇪🇨Chile 🇨🇱Colombia 🇨🇴Peru 🇵🇪
Status
Soporte / Support
English
  • Español
  • English
  1. Quick Start

Test Data

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(/mx/card-payments/one-step-payments/accept-a-payment) by card.
Important
For payments with American Express cards, the firstName parameter accepts a maximum of 18 characters.

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:
Important
The test amount to enter during the OTP validation for it to be successful is 555.

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
For more specific scenarios, send the data used in one-time card payments.

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#

The final result of this test data depends on your merchant's configuration: it requires the test environment (sandbox) to be active for your merchant and the assigned processor to support simulating certain statuses. If you don't get the expected result, contact your Kushki account manager or support.
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#

The final result of this test data depends on your merchant's configuration: it requires the test environment (sandbox) to be active for your merchant and the assigned processor to support simulating certain statuses. If you don't get the expected result, contact your Kushki account manager or support.
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:
The scenarios described will be required to approve the technical certification. To test more specific scenarios, you can send the data specified in the one-time card payments.

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
Modificado en 2026-10-14 19:41:51
Anterior
Policy for Important API Changes
Siguiente
Error Codes
Built with