loading...
loading...

Important Update: Streamlining Our Rail Network Effective September 2, 2026

sunsetting redundant rails

At Yativo, we’re constantly evaluating our infrastructure to make sure it reflects the realities of the regulatory and banking landscape we operate in, and to keep our platform fast, reliable, and easy to build on.

As part of that ongoing work, we are sunsetting a number of virtual account currencies and payment rails, effective September 2, 2026. This decision was driven by two factors: recent regulatory and banking partner changes that make certain rails no longer viable, and an internal push to streamline operations around the corridors where we can offer the strongest, most reliable service.

Below is a full breakdown of what’s changing. If any of these rails are part of your current integration, please review the details and reach out to your account manager as soon as possible to discuss migration options.


Section 1: Virtual Accounts

Currency / RailAlternativeStatus
EURDEEUR (faster payments endorsement)Existing accounts remain active — no new accounts issued
MXNTEFMXN, MXNBASE (virtual card endorsement)Full sunset
USDSPIDUSDCOBO (COBOPOBO Endorsement)Full sunset
COPPayment linksFull sunset
CRCNAFull sunset
ARSPayment linksFull sunset
BRLUSDBRL (Brazil endorsement)Full sunset
PENPayment LinksFull sunset

What this means:

  • EURDE clients with existing virtual accounts can continue using them as normal. We are no longer provisioning new EURDE accounts.
  • MXNTEF, USDSPID, COP, CRC, ARS, BRLUSD, and PEN virtual accounts will be fully decommissioned. Clients using these currencies should begin transitioning to alternative account options ahead of the sunset date.

Section 2: Payin and Payout Rails

Payouts

The following payout methods will be sunset:

Gateway IDMethod
1334INTERBANKING (ARG)
1343Local Bank Transfer (ACH)
1346CCE
1350TEF (Low Value)
1351Local Bank Transfer (SCP)
1352Yape
1353ACH
1354TransfiYa
1355BreB (COL)
1356SINPE (CRI)
1357ACH
1358ACH
1359ACH Pronto
1360SIPAP (PRY)
1361ACH

Payins

The following payin methods will be sunset:

Gateway IDMethod
12cc0ae8-e2b1-426d-aa30-d8a1076f489eEtpay
21e0962c-d7e5-4a03-9a7f-eaf749a7f676PSE (B2B)
32c7fb48-df78-45d3-b045-509c835f0126SoyFri QR (GTM)
4fc5b452-167f-4b8b-b24b-68e7bc3f6e54QR
565b6526-36b8-4650-8ba8-95e94e13aa06QR
82628f36-e00b-4abb-9a9e-8126c6756822PIX (B2B2C)
89f13ba5-9cbf-4662-847e-6433a9749863DEBIN
cc7410bd-2fca-4ebc-a7b6-0bde9711d5faCODI
ccfe1c62-9975-47ab-8d89-d58d16596921Wallet Fri (GTM)
d1a3f6cb-6804-4ae3-99cc-5e0c76862e25Akisi Online Referenced Payments (GTM)
f3a53ed4-f62e-4f76-9a59-e96f42ae9c2bQR (B2B2C)

Why We’re Making This Change

Two things are driving this update:

  1. Regulatory and partner changes. Some of the rails above are being sunset because recent shifts on the regulatory or banking-partner side have made them impossible to continue supporting.
  2. Operational streamlining. Others are being consolidated so we can focus our infrastructure investment on the corridors and rails where we can guarantee the highest reliability and performance for our clients.

What You Need to Do

  • Review the tables above against your current integration to identify any affected rails or virtual accounts.
  • Reach out to your account manager before September 2, 2026, to discuss alternative rails or corridors that can cover your use case.
  • Update any hardcoded gateway IDs in your integration referencing the payin/payout methods listed above.

We know changes like this can affect live operations, and we don’t take that lightly. Our team is ready to work directly with every affected client to make this transition as smooth as possible.

If you have questions, please contact your Yativo account manager or reach out to our support team directly.