1. Wire Transfers
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. Wire Transfers

Receive Wire Transfers

Your customers will be able to use the balance in their bank account to make purchases on your website or application
Web
iOS
Android
Allow your customers to use the available balance in their bank account to purchase your products or services from your website via a wire transfer. To do so, you must obtain the basic data of your paying customers and redirect them to the Wire Transfer System (which can be configured from the administration console) to authorize the debit to their bank account.
The payment flow that you will integrate is as shown below:
Flujo Pago con transferencia (CL-EC-PE) EN
Important
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 data, generating a token for such information through Kushki's servers, and sending that information to the back end to start the payment process.
You have two options to integrate: Kajita and Kushki.js.

Kajita#

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

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.
For Kajita (v.2):
For Cajita (v.1):
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 script tag.
For Kajita (v.2) you can obtain such script from your Administration Console, as explained in Create and customize your Kajitas.
For v.1 (Cajita), add the following script, making sure the form has loaded:
This will create a predesigned form on your website to accept payments.
You can use Kajita to offer not only wire transfer payments, but also card or cash payments.

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 the Kushki object#
Add the following code to your application

Request the list of banks#

Before generating the token, you can load the full list of available banks, so that the paying customer can select the entity to make the transfer:
This is an optional step. In the event that you do not include it in your integration, the paying customer will select their bank when redirected to the wire transfer portal. If you want the customer to pay at a specific bank of your choice, this must be indicated in the body of the request method of the wire transfer token.

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:
Send notifications to your customers
If you want your customers to be notified of their transactions, make sure to capture your customer's email address in the payment form. In addition to this, remember to enable the notification option from your administration console.
Then, for the moment when the user submits the form, add a token request and send 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 charge endpoint to start the charge process.
API Reference for Chile
Request a Transfer In token
Init Transaction
Get Status
Always authenticate from your server
The transaction init requires the Private-Merchant-Id header. Never expose your Private Key in front-end code: this call must always be made from your back end.
JavaScript
Python
PHP
According to the consumption response of the method to initiate the transaction, redirect the user to the URL that Kushki returns from the Wire Transfer System so that they can authenticate in their bank entity and authorize the transaction amount to be debited from the balance of their bank account.

Display the result of the transaction#

Once the payment is completed, the customer will be returned with a GET call to the callbackUrl you specified when requesting the token.
Along with the return URL, we will send the transaction token in the path, with which you can check the status of the transaction using this endpoint. In addition, you will obtain the necessary information for your customer's payment voucher.
For example, for callbackUrl = 'http://www.example.com' the customer will return to:
GET https://www.example.com/?token=26735cbb653a421ba7138eb515e0ab1d
where token is equal to 26735cbb653a421ba7138eb515e0ab1d
According to the response that you receive from the transaction status, show the user a success or failure screen to inform the customer whether the payment was made correctly or if there was an error.

3. Test your Integration#

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.
To test your integration, we have a test environment where you can simulate transactions from the Bank Transfer System.
The first step is to select "Test Bank" from the list of banks. Use the following data to make a test transfer payment to ensure that your integration is ready.
Approved Transaction
RUT: 11111111-1
Password: 111111
Account: Select the first account
Activation with code: 11111111
Coordinates: 11 11 11
Code by SMS or mail: 111111
Verification: 11
Declined Transaction
RUT: 44444444-4
Password: 444444
Account: Select the first account
Coordinates: 44 44 44
Verification: 44
Below is an example of the bank transfer payment process. Remember that the actual payment process for your customers may vary depending on the bank selected.
Customize the transfer portal
Kushki gives you the possibility to customize the Wire Transfer System from your administration console. Click here for more information.

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 should be aligned with Kushki's responses.
All Kushki responses must be saved and recorded (required in case you need support).
In the event of successful receipt of the Webhook notification, respond to the request with a statusCode 200, and inform your customer.
The "Pay" button is disabled after the first click.
If the result of the transaction is Initialized, a new transaction must not be allowed until approved or rejected.
Kushki's logo must be visible for the customer. You can find our logo in several formats here.
Make sure to send all the variables required, specified in the API reference.

Accept Webhooks
Manage correctly post-payment events.
Check the status of your transactions
With the token you received from the front end, you will also be able to check the status of transactions through our API.
Modificado en 2026-10-14 19:51:50
Anterior
Banks and transaction details for bank transfer payments.
Siguiente
Check the Status of a Transaction
Built with