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
    • 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
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Schedule a recurring charge
      • Manage your Scheduled Charges
    • 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
    • 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
    • Transactions
      • Transactions
      • Cancel payments
  • Wire Transfers
    • Banks and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
    • Error Codes for Transfers
  • Cash Payments
    • How do Cash Payments Work?
    • Accept a Cash Payment
    • Authorized locations
    • Error Codes for declined cash transaction
  • Alternative payment methods (APM)
    • How do APM payments work?
    • Accept Bre-B payments
  • Money Disbursement
    • Payment Distribution
    • Recharge your balance for dispersions
    • Wire Transfer
      • How Does a Payment Distribution by Wire Transfer Work?
      • Payment Distribution to Bank Accounts
      • Disburse with Bre-B
      • Error codes for transfer dispersions
    • Cash
      • How does payment distribution in cash work?
      • Distribute Payments in Cash
      • Manage your Payment Distribution Transactions
  • 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 Distribution Webhooks
      • Webhook for payment disbursement through wire transfer
      • Webhook for Payment Distribution in Cash
    • 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

Frequently Asked Questions

Check our quick answers to frequently asked questions

How can I get a test account?#

You can apply for a free test account from our website. Once your application has been accepted, Kushki will grant you access to the console, an online panel where you can manage your Kushki integration for a specific country.

I have built an integration for several countries, can I use the same test account?#

If you are developing an integration for several countries, we recommend you to create an account for each one of them. In this way, you can run tests with the local configuration and currency.

Does Kushki allow processing of international cards?#

Kushki allows you to process international cards in certain cases. Contact your sales representative or visit our Support Center for more information on how to do this.

Can I use my test account after obtaining my productive account credentials?#

Yes, you can do it. Your test account will not be disabled once you receive your productive account credentials.

What should I do once my integration is completed?#

A technical certification is required. Get in touch with us to schedule a certification session where we will perform some tests to verify that your integration runs as expected.

What is tokenization?#

Tokenization is a process by which Kushki transforms sensitive customer data into an alphanumeric code called token. When you use a token, it's not necessary to manage such data directly, and you can make any transaction safely.

Does the token expire?#

Yes, it expires. A token has a life span of 30 minutes and can only be used once.

Does Kushki have a pre-designed form for customers to enter payment information?#

Yes, it's called Cajita (Little Box). If you import Cajita on your front end, you will have a pre-designed form. The form will change according to the payment method.

Can I design my own front end form?#

Yes, you can do it. You are free to design your own form with the colors and logos of your choice. After obtaining data from your client, you just need to request a token by using one of Kushki's front end libraries. Check our web guides for more details.

What do I need to have in mind when designing my own form for credit card payments?#

Below you will find a list of the validations you need:
The cardholder's name is required.
The credit card number field only allows numbers.
The credit card field allows a maximum of 16 digits (it may be less).
The credit card number is required.
The CVV field only allows numbers.
The CVV field allows no more than 4 numbers (they may be 3).
A CVV is required.
The CVV will be masked so it cannot be read; each character is replaced with symbols such as asterisks (*) or points (-).
The expiry date must be a valid date (current or future month and year).
An expiry date is required.
The Pay button is disabled after the first click.

If I use Cajita, do I have to contact you to obtain a token?#

It is not necessary. Cajita already has built-in tokenization logic. After clicking the Pay button, the Cajita will give you a token.

Can Kushki send a payment confirmation to my integration service?#

Yes, it can. We offer you notifications via Webhooks. Check our guidelines on this topic.

How can I configure my Webhook URL in Kushki?#

Please, get in touch with us contact with us; our team will need your service's URL as well as the public ID of your business.

What do I need to receive a notification through my Webhook?#

Your Webhook should have the capacity to receive POST requests. It is also important to have a SSL certificate. If you receive notifications correctly, please send us back a 200 status code.

What if my Webhook temporarily fails?#

If we receive an error response when we try to notify your service, we will try again every 5 minutes, during the next 5 hours of the initial report.
Modificado en 2026-10-14 19:53:31
Anterior
Quick Start
Siguiente
Moving to Production
Built with