Skip to main content

Overview

Bank transfers are a popular payment method across Latin America, with each country having its own interbank transfer system. Yuno provides a unified API to accept bank transfers across multiple countries while handling the country-specific requirements behind the scenes. Bank transfer methods supported:
  • PSE (Colombia) — Online bank transfer via redirect
  • SPEI (Mexico) — CLABE-based interbank transfer
  • Transferencia 3.0 (Argentina) — QR-based bank transfer
  • Khipu (Chile) — Bank transfer aggregator via redirect

PSE (Colombia)

Overview

PSE (Pagos Seguros en Linea) is Colombia’s online bank transfer system, operated by ACH Colombia. The customer selects their bank, is redirected to their online banking portal, and authorizes the transfer.

Requirements

Creating a PSE Payment

PSE Redirect Flow

  1. Create the payment — the response includes a redirect_url
  2. Redirect the customer to the redirect_url
  3. Customer selects their bank and logs into online banking
  4. Customer authorizes the transfer
  5. Customer is redirected back to your callback_url
  6. Verify final status via webhook (do not rely on callback URL parameters alone)
PSE transfers can take up to 15 minutes to be confirmed. Always use webhooks for definitive payment status. The callback URL redirect may arrive before the payment is fully confirmed.

SPEI (Mexico)

Overview

SPEI (Sistema de Pagos Electronicos Interbancarios) is Mexico’s real-time interbank transfer system operated by Banco de Mexico. Customers transfer funds using a CLABE (Clave Bancaria Estandarizada) number.

Requirements

Creating a SPEI Payment

SPEI Response

The response includes CLABE details for the customer to initiate the transfer:
Display the CLABE, beneficiary, amount, and reference to the customer so they can initiate the transfer from their banking app.

Transferencia 3.0 (Argentina)

Overview

Transferencia 3.0 is Argentina’s interoperable QR payment system, regulated by BCRA (Banco Central de la Republica Argentina). Customers scan a QR code with their banking or wallet app to transfer funds.

Requirements

Response

The response includes a QR code for the customer to scan:

Khipu (Chile)

Overview

Khipu is a Chilean bank transfer aggregator that enables online payments through the customer’s bank. It supports all major Chilean banks and provides a redirect-based flow.

Requirements

Khipu Redirect Flow

Khipu follows the same redirect pattern as PSE:
  1. Create the payment
  2. Redirect the customer to the redirect_url
  3. Customer selects their bank and authorizes the transfer
  4. Customer is redirected back to your callback_url
  5. Verify final status via webhook

Status Polling and Webhooks

For all bank transfer methods, use webhooks as the primary mechanism for receiving payment status updates: If needed, you can also poll payment status:
Prefer webhooks over polling. Polling should only be used as a fallback. If polling, use a reasonable interval (every 30-60 seconds) and implement exponential backoff.

Settlement Timelines

Common Issues

Response Handling

Redirect-Based Methods (PSE, iDEAL, SEPA)

Bank transfer methods typically return a redirect URL:
Redirect the customer to redirect_url to authorize the transfer at their bank. After authorization, the customer is redirected back to your return_url.

Webhook Events

Never rely on the redirect callback alone for payment confirmation. The customer may close their browser before being redirected back. Always use webhooks for definitive status updates.