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

How do Payments by Wire Transfers Work?

We explain how a payment by wire transfer works in Kushki
If your users do not have a credit card or wish to use the available balance in their bank accounts to make an online purchase, the account debit (wire transfer) is the ideal and fast payment option.

Payment process#

The payment process by wire transfer consists of allowing your customer to use the available balance in their bank account to pay for a purchase on your website or app. To do so, you must redirect your customer to the website of the bank entity of their choice at checkout to authorize the transaction amount to be debited from their account.

The Flow#

The payment process with transfers consists of allowing your customer to use the available balance in their bank account to pay for a purchase on your site or app. To do so, you must redirect your customer to the site of the bank they select at checkout, so they can authorize the debit of the transaction amount from their account.
In Ecuador you can offer transfers through two processors: traditional bank transfer and DeUna!, the digital wallet backed by Banco Pichincha. The integration flow is the same in both cases; the only thing that changes is the way your customer completes the payment.
Transfer in general flow
1. Selection of the payment method
Within your app or website, the user must select transfer as the payment method and fill in the payment form data.
2. Sending the request
Your merchant sends the transfer request to Kushki so it can initiate the transaction.
3. Sending the URL
Kushki confirms the creation of the transaction and returns the URL to which you must redirect the user.
4. Redirection for bank selection
Your merchant redirects the user to the indicated URL, so they can select their bank and make the transfer.
5. Bank portal login and authorization
When the user enters their bank's site, they authenticate, verify the transaction data (operation description, amount and account to be debited) and accept that the transaction amount be debited from their account balance.
6. Debit confirmation
When the user authorizes the transfer, the bank confirms the result of the operation to Kushki.
7. Kushki notification
Kushki notifies you of the final status of the transaction.

Variant: paying with DeUna!#

DeUna! is the digital wallet with the widest adoption in Ecuador. Your customer pays with the balance in their DeUna! account from the app, without registering a card or selecting a bank.
Processor activation
DeUna! is enabled as a processor for your merchant from the Kushki Console, and the Kushki team does it. There is no parameter in the request to select the processor: once enabled, the same Init Transaction endpoint starts returning the DeUna! fields.

The three payment experiences#

A single request returns all three experiences. You decide which one to display, based on the channel your customer is buying through.
ExperienceResponse fieldBest forCompatible apps
Dynamic QRqrDesktop checkout: the customer scans with their phoneDeUna!, Banco Pichincha, Diners
Deep linkredirectUrlMobile web or your own app: opens DeUna! in one tapDeUna!
Reference codereferenceCodeAlternative when the camera fails or the customer prefers to typeDeUna!, Banco Pichincha

DeUna! payment flow#

Steps 1, 2, 3, 6 and 7 are identical to the traditional transfer. Steps 4 and 5 change.
flow-transfer-in-deuna-ec-en
4. Displaying the payment experience
Instead of redirecting the user to a bank portal, your merchant displays the experience that matches its channel: render the qr in your checkout, present the redirectUrl as a payment button, or display the referenceCode so the customer can type it into the app.
With the QR and the reference code, the user never leaves your site.
5. Confirmation in the DeUna! app
The user opens DeUna!, verifies the transaction data (merchant, order number and amount) and confirms the payment with their biometrics or PIN. The amount is debited immediately from their account balance.

Render the QR code#

The qr field contains a PNG image encoded in Base64, with the data:image/png;base64, prefix already included. You must read the value and render it as an image in your checkout: Kushki does not host the QR image for you.
Do not add the prefix twice
Because qr already carries the data:image/png;base64, prefix, concatenating it again produces an invalid data URI and the image fails silently: you will see a blank space with no error in the console.

Expiration times#

The QR, the deep link and the reference code expire in 3 minutes, while the transaction token lasts 30 minutes. Generate the payment experience at the moment your customer is ready to pay, show a countdown on screen, and request a new token if it expires.

Receive wire transfers
Start your integration and accept wire transfers
Modificado en 2026-10-14 19:47:44
Anterior
Wire Transfers
Siguiente
Banks and transaction details for bank transfer payments
Built with