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
    • 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 one-time payments with authorization and capture work?
      • Receive payments with authorization and capture
    • Webpay Plus Payments
      • Accept Payments through Webpay Plus
      • Reserve funds with Webpay Plus
    • 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 Webpay Scheduled Payments
      • Recurring Payments through Webpay OneClick
      • Reserve funds in subscriptions with Webpay OneClick
    • One Click Payments with Webpay OneClick
      • Webpay OneClick Payments
      • Reserve funds in one click payments with Webpay OneClick
    • OneClick Payments
      • Accepting One-Click Payments
      • How does authorization and capture work in OneClick payments?
      • Receive OneClick payments with authorization and capture
  • Card-present payments
    • Accept card present payments
    • Test data
    • Webhooks for card present
    • 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
    • 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
  • Money Disbursement
    • Wire Transfer
      • How does the dispersion by means of bank transfer work?
      • Payment Distribution to Bank Accounts
      • Error codes for transfer dispersions
  • 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
      • Webhook for Payments Made with Webpay Plus
    • Recurring Payments Webhooks
      • Webhook for Recurring Payments Made with Card
      • Webhook for recurring payments with Webpay OneClick
    • 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 by card.

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response:(000) Approved Transaction

Declined transaction in token request#

Card number: 000000000000000000.
CVV: any.
Expiration date: Any date in the future.
Response:K025 Invalid card

Transaction rejected at payment request#

Card number: 4349003000047015.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Invalid card#

Card number: 4349008516656431.
CVV: any.
Expiration date: Any date in the future.
Response:(019) Unsupported card

Insufficient funds#

Card number: 4349001210846432.
CVV: any.
Expiration date n: Any date in the future.
Response: (021)Insufficient funds

Invalid CVV#

Card number: 4349003243371321.
CVV: any.
Expiration date: Any date in the future.
Response: (022) Unable to verify CVV

Blocked card#

Card number: 4349001386781322.
CVV: cualquiera.
Expiration date: Any date in the future.
Response: (023) Card blocked by bank

Payments with Webpay Plus#

Use the following data to test payment reception with Webpay Plus. To check the status of the transaction, you can use the method card-async status.
In the event of selecting a debit card, you will only have to send the card number that corresponds to the scenario you want to test.

Approved transaction#

Card number: 4051885600446623.
CVV: 123.
Expiration date: Any date in the future.
RUT: 11.111.111-1.
Password: 123.
Respuesta: (000) Approved Transaction

Declined transaction#

Card number: 5186059559590568.
CVV: 123.
Expiration date: Any date in the future.
Response:Error in the transaction

One-Click Charges#

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

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response: (000) Approved Transaction

Declined transaction in token request#

Card number: 4574441215190335.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Transaction rejected at payment request#

Card number: 4349003000047015.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Invalid card#

Card number: 4349008516656431.
CVV: any.
Expiration date: Any date in the future.
__Response: __(019) Usupported card

Insufficient funds#

Card number: 4349001210846432.
CVV: any.
Expiration date: Any date in the future.
Response: (021)Insufficient funds

Invalid CVV#

Card number: 4349003243371321.
CVV: any.
Expiration date: Any date in the future.
Response: (022) Unable to verify CVV

Blocked card#

Card number: 4349001386781322.
CVV: any.
Expiration date: Any date in the future.
Response: (023) Card blocked by bank

On-demand payments with Webpay Oneclick#

Use the following data to test payment reception with Webpay Oneclick. To check the status of the transaction, you can use the method card-async status.
In the event of selecting a debit card, you will only have to send the card number that corresponds to the scenario you want to test.

Subscription created#

Card number: 4023655102252133.
CVV: any.
Expiration date: Any date in the future.
Response: Approved transaction

Declined transaction#

Card number: 4568652646042584.
CVV: any.
Expiration date: Any date in the future.
Response: 500 Rejected transaction

Reserve funds in a card#

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response: (000) Approved Transaction

Declined transaction in token request#

Card number: 4574441215190335.
CVV: any.
Expiration date: Any date in the future.
Respuesta:(017)Invalid card

Transaction rejected at payment request#

Card number: 4349003000047015.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Decline in capture of reserved funds#

Card number: 4547004841271012.
CVV: any.
Expiration date: Any date in the future.
Response: (579) Declined transaction

Reserve on-demand funds#

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response: (000) Approved Transaction

Declined transaction in token request#

Card number: 4574441215190335.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Transaction rejected at payment request#

Card number: 4349003000047015.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Decline in capture of reserved funds#

Card number: 4547004841271012.
CVV: any.
Expiration date: Any date in the future.
Response: (579) Declined transaction

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 150.

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response: (000) Approved Transaction

Declined transaction in token request#

Card number: 4574441215190335.
CVV: 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: Transaction initialized
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 credentials to simulate transactions from the Bank Transfer System. You can check the status of the transaction using the get status transfer method.

Approved transaction#

RUT: 123456789.
Password: kushki123.
Response: Successful Transaction

Failed transaction#

RUT: 000000000.
Password: kushki123

Card enrollment#

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

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response: (201) Subscription created

Transaction declined at token request#

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

Recurring charges with Webpay Oneclick#

Use the following data to test recurring payment reception with Webpay Oneclick. To check the status of the transaction, you can use the method card-async status.
In the event of selecting a debit card, you will only have to send the card number that corresponds to the scenario you want to test.

Subscription created#

Card number: 4051885600446623.
CVV: 123.
Expiration date: Any date in the future.
Card type: Credit.
RUT: 11.111.111-1.
Password: 123.
Card number: 4051884239937763.
CVV: 123.
Expiration date: Any date in the future.
Card type: Debit.
RUT: 11.111.111-1.
Password: 123.
Response: Approved transaction

Declined transaction#

Card number: 5186059559590568.
CVV: 123.
Expiration date: Any date in the future.
Card type: Credit.
RUT: 11.111.111-1.
Password: 123.
Card number: 5186008541233829.
CVV: 123.
Expiration date: Any date in the future.
Card type: Credit.
RUT: 11.111.111-1.
Password: 123.
Respuesta: 500 Rejected

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.

Approved transaction#

Card number: 5451951574925480.
CVV: any.
Expiration date: Any date in the future.
Response: (000) Approved Transaction

Declined transaction in token request#

Card number: 4574441215190335.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Transaction rejected at payment request#

Card number: 4000001278960006.
CVV: any.
Expiration date: Any date in the future.
Response:(017)Invalid card

Money distribution to bank accounts#

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.
Kushki allows you to simulate money distribution transactions. Use the following data when requesting the payout token. You can validate the status through the endpoint of status query.

Successful transaction#

ID number: 123456789.
Response: Transaction status: Approval

Declined transaction#

ID number: 999999990.
Response: transaction does not exist
Modificado en 2026-10-14 19:49:07
Anterior
Policy for Important API Changes
Siguiente
Error Codes
Built with