1. Cash Payments
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. Cash Payments

Accept a Cash Payment

Allow your users without a bank account to purchase your products or services
Web
iOS
Android
This payment option is ideal for those customers who want to purchase the products or services available on your website, but do not have a card or a bank account. To do so, you need to capture your customer's basic details, to generate a reference or voucher, with which your user will be able to make the payment at an authorized location of the collection entity of their choice.
The payment flow that you will integrate is as shown below:
Flujo pago con efectivoEN
To keep in mind
Due to our risk policies, the available payment methods and the integration type may vary once you complete the affiliation. We will tell you how to proceed if this process applies to your merchant.

1. Set up your Front-end#

The front-end is responsible for collecting the user’s main details, generating a token for such information through Kushki’s servers, and sending that information to the back end to start the payment process.
For this, you have two options: Kajita and Kushki.js.

Kajita#

Kushki has payment forms ready to collect card information securely. You can use any of our versions:
Cajita: our first version of the payment form. Not customizable.
Kajita: is the second version, which allows you to add customizations from your Administration Console and even have several versions of Kajita, one for each payment method, for example.

Create and customize your Kajitas#

With Kushki you can create your Kajitas from the Administration Console. Click here to learn how to do this.

Set up Kajita#

Include the kushki-checkout.js script in your payment page by adding it to the <head> of your HTML file. Always load kushki-checkout directly from cdn.kushkipagos.com. Do not include the script in a bundle or package or host a copy of it.

Add Kajita to your Website#

Kajita needs a space within your page. Enter the following code in your website's <body>, where you want the payment form to be displayed.
Remember to configure the action of the action form according to the corresponding endpoint in your back end, to obtain the token.
Then, add the following script tag. Make sure that the form has been uploaded.
This will create a predesigned form on your website to accept payments.
You can use Cajita to offer not only cash payments, but also payments with card or through wire transfers.

Kushki.js#

Use Kushki.js if you need more control over the "look & feel" or appearance of your payment form.

Set up Kushki.js#

Option 1 - CDN#
Use the following script tag at the end of the <body> of your payment page.
Option 2 - NPM#
Install the package from npm.
Then import it into your code using the following code.
Set up Kushki object#
Add the following code to your application

Collect User Information and Send it to your Back End#

First, embed the form in your payment page adding the required fields. You can design it as you prefer.
For example:
And, for the moment the user submits the form, add the token request and take it to your back end.
Check the full reference on our Kushki.js reference

2. Set up your Back-end#

The back-end is responsible for receiving the token obtained from your front end and starting the payment process with Kushki.
When the user submits the form, your front end sends a token to an endpoint that you specified previously. Using this token, you must make a call to our charges endpoint to start the charge.
JavaScript
Python
PHP
Check our API Reference for more information.
According to the consumption response of the method to initiate the transaction, redirect the user to the URL of the PDF of the voucher so that your customer can download and print it and thus make the payment at the authorized location point of the collection entity of their choice.

3. Test your Integration#

There are test identification numbers that you can use to simulate status to ensure that your integration is ready. Use them in the token request (front end):
Approved Transaction: Any identification number
Initialized transaction: 9999999999
Declined Transaction: 1000000000

4. Prepare your Certification#

Read the following guidelines for technical certification approval (required to obtain productive account credentials):
The calculation of taxes and the total amount must be the correct amount.
Messages displayed on the screen are in line with Kushki’s responses.
All Kushki responses must be saved and recorded (required in case you need support).
Kushki's logo must be visible for the customer. You can find our logo in several formats here.
Make sure to send all the data required as specified in the [API Reference
If you are using Kushki.js, make sure that:
The payer name must be required.
The payment button must be disabled after the first click.
Kushki's logo must be visible for the customer. You can find our logo in several formats here.
If you design your own voucher, also consider the following:
The pin must be visible.
The agreement number must be visible. (Only if the Init response contains it).
The voucher expiry date must be visible.
Cash points where the PIN can be used to make the payment must be visible.
The total amount is visible.
The barcode is displayed (in case it is included in the response of the charge endpoint ).

Accept Webhooks
Manage correctly post-payment events.
Check the Status of your Transactions
In addition to the receipt and the payment pin, you will also receive a TicketNumber which is the identifier of your transaction in Kushki and also corresponds to the parameter that you can use to check the status of the transactions through our API.
Modificado en 2026-10-14 19:48:02
Anterior
How do Cash Payments Work?
Siguiente
Authorized locations
Built with