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
    • Introduction to 3DS
    • Functionalities by business model
    • How do third party commissions work?
    • Integration guide Third Party Commissions
    • One-step Payments
      • How do Card Payments Work?
      • Accept a Card Payment
      • Accept One-Time Payments with OTP
      • OTP Authentication Error Codes
      • Error codes for single card payments
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Create a recurring charge
      • Manage your Scheduled Charges
    • Refunds
      • Returns, cancellations, and refunds
    • 3DS Authentication
      • 3DS API integration
      • 3DS integration with kushki.js library
      • 3DS API integration plus kushki.js library
      • 3DS Error Codes
  • Recurring Card Payments (Online)
    • Functionalities by business model
    • Error codes in recurring charges
    • Authenticate your subscriptions with 3DS
    • External subscriptions to Kushki
    • OneClick Payments
      • Accepting One-Click Payments
  • 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
  • Cash Payments
    • How do Cash Payments Work?
    • Accept a Cash Payment
    • Authorized locations
    • Error Codes for declined cash transaction
  • Plugins
    • Shopify
      • Shopify
      • Plugin Operation
    • VTEX
      • VTEX Integration Guide
  • Payment Links
    • Smartlinks
  • 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
    • 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 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 by card.

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) Invalid card

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) Invalid card

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

Transaction approved#

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

Cash payments#

Kushki allows you to simulate cash payments, either approved or declined transactions. Use the following data when requesting the token of cash in. You can validate the status through the status query endpoint.

Successful transaction#

ID number: any.
Response: Successful Transaction

Initialized transaction#

ID number: 9999999999.
Response: Initialized transaction
Testing the initialized transaction scenario will not return any Webhook events.

Declined transaction#

ID number: 1000000000.
Response: Expired 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 when requesting the token of transfer in to simulate different responses. You can validate the transaction response by calling the endpoint of status query.

Successful transaction#

ID number: any.
Response: Successful Transaction

Rejected transaction#

ID number: 999999990.
Response: 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) Subscription created.

Transaction declined at token request#

Card number: 4574441215190335.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.
Response: (017) Declined transaction

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) Invalid card

Transaction rejected at payment request#

Card number: 4000001278960006.
CVV: any.
Zipcode: any.
Expiration date: Any date in the future.
Response: (017) Invalid card
Modificado en 2026-10-14 19:46:10
Anterior
Policy for Important API Changes
Siguiente
Error Codes
Built with