1. Wire Transfer
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
    • How do third party commissions work?
    • Integration guide Third Party Commissions
    • 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 single 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
    • 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 Payments
      • Accepting One-Click Payments
      • How do OneClick payments with authorization and capture work?
      • Receive one-click payments with authorization and capture
  • Card-present payments
    • Card present payments
    • Accept card present payments
    • Test data
    • Webhooks for card present
    • Cloud Terminal API
      • Cloud terminal API overview
      • Take payments
      • Cancel a payment request
      • Check the status of a payment request
      • How to print a customized ticket?
    • App-to-app
      • App-to-app overview
      • Take payments
    • Terminal SDK
      • Terminal SDK Introduction
      • Take payments
    • 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
    • How do Payments by Wire Transfers Work?
    • Banks and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
  • Money Disbursement
    • Wire Transfer
      • How Does a Payment Distribution by Wire Transfer Work?
      • Payment Distribution to Bank Accounts
      • Error codes for transfer dispersions
  • Payment Links
    • Smartlinks
  • Plugins
    • Shopify
      • Shopify
      • Plugin Operation
    • VTEX
      • VTEX Integration Guide
  • 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
    • Webhooks
    • 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
    • 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 Transfer

Payment Distribution to Bank Accounts

Distribute payments to your customers or vendor's bank accounts.
Payment distribution by wire transfer consists of sending money to your customers' accounts. In other words, if you have their bank details, you can use your Kushki distribution account and send the money to their accounts by wire transfer, using whatever logic you prefer.
This is ideal for:
Payments for suppliers or sellers
Marketplaces
Delivery applications
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.

Operation details#

The dispersion process in Mexico is done in the following way: Merchant > Kushki > Processor > User.
ParameterDetail
Minimum amount1 MXN
Maximum amountNo limit
Transaction approval timeImmediate (same bank and other banks)
Processing days7 days a week
Processing hours24/7
Types of recipient accounts available for sending wire transfers- CLABE account
- Debit card
- Cell phone number**.
(accountType and accountNumber parameters must be sent in the token request.)
** To send payments by cell phone number, the recipient of the transfer must have previously associated their deposit account to their cell phone number in their bank , either physically (bank branch) or electronically (bank's mobile application).
Importante
Banco S3 México, S.A. is not available for disbursement via bank transfers.

Process Flow#

The flow that you will integrate is shown below:
Transfer Out Mexico Flow
Here you will learn how to integrate money distributions by wire transfer.

1. Obtain the list of partner banks#

The first step is to check the list of banks available to make the wire transfer. To do so, you must use this endpoint, which will show you the banking institutions available to make the transaction.
JavaScript
Python
PHP
In response to this call, you will receive the name and code of the available banks. The latter must be sent in the transfer out token request.

2. Tokenize the information#

After obtaining the bank code of the account where the transfer will be received, you have to request a token by using our transfer out token request endpoint.
JavaScript
Python
PHP
In case you do not know the recipient's document number, send ND in the documentNumber field.

3. Initialize the transaction#

In this step, you should have obtained a token and can start the distribution process with Kushki. You will need to make a call to our initialization endpoint to initiate payment.
JavaScript
Python
PHP
See our API Reference for more information.
In the response, a ticket number and a status are issued for the transaction.
Important
Once a distribution by wire transfer has been initialized, it will not be possible to cancel it.

4. Track the transaction status (optional)#

Now that the transfer is close to being processed, you can check the transaction status via webhooks or manually, by using our API

Webhook#

The transaction status is automatically notified at the time when the money has been deposited in the bank account.
The webhook response will contain the variables processorStatus and processorStatusDescription within the metadata object with the final status of the distribution:
  "metadata": {
       "processorStatus": "LIQUIDADO",
       "contractID": "AB123",
       "processorStatusDescription": null
   },
See here the complete structure of the webhook of distribution by wire transfer.
To configure a webhook in your test merchant site, you need to notify our agents by indicating the URL and the payment method via email to soporte@kushkipagos.com.

API#

You can use our Get Status endpoint in our API to manually track the status of a specific transaction.

5. 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.
There are test ID numbers that you can use in the UAT environment to ensure that your integration is ready.
Approved transaction
Account number: 646180110400000007
Identification number: 123456789
Identification type: CURP or RFC
Account type: CB
Cancelled transaction
Account number: 646180206800000003
Identification number: CADM9108029F4
Identification type: CURP or RFC
Account type: CB
Returned transaction
Account number: 646180206800000003
Identification number: CADM9108029G5
Identification type: CURP o RFC
Account type: CB
Importante
There are two methods to top up funds in your distribution account. The first one is through the Console and you can do it by following these instructions.
The second method is through support. To top up funds for the testing phase, email us to integraciones@kushkipagos.com. And for the production phase, you must make a transfer of funds to the following business account:
Bank: Nvio
Account Type: Clabe
Business account: 710969000045648227
Business name: Kushki S D RL DE CV
Tax ID: KUS1812121C1
Once the transfer has been made, it is necessary to send the receipt to the support area at finopsmex@kushkipagos.com.
The time for the funds to be available in the account will be 3 hours from the time the mail was received.

6. Prepare your certification#

Read the following guidelines for technical certification approval (required to obtain productive account credentials):
Tax calculations must be correct.
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).
If there's no requirement for sending a reference voucher to the customer's mail, you don't need to specify an email address in the token request.
If webhook notifications are received correctly, respond to the request with a status 200.
The payment button must be disabled after the first click.
Kushki's logo must be visible to the customer. You can find our logo in various formats here.
Make sure that in the body of the request all the fields required in the API Reference are included.

Accept webhooks
Manage correctly post-payment events.
Modificado en 2026-10-21 22:32:52
Anterior
How Does a Payment Distribution by Wire Transfer Work?
Siguiente
Error codes for transfer dispersions
Built with