Remittances & Cross-Border Payments: Modernize the Core to Capture the Flow

More than $64 billion a year in remittances enters Mexico. Almost all of that money passes, today, through some system. The question for your institution is simple: does it pass through yours, or through the one that had the core to capture it?

The figures are enormous and yet easy to overlook from the server room. In 2024, Mexico received a record $64.745 billion in remittances, according to the Bank of Mexico—the equivalent of close to 4% of GDP, per BBVA Research's analysis—keeping it the world's second-largest recipient, just behind India, according to the World Bank. The entire region received $161 billion, the Inter-American Development Bank reported. That flow is one of the most constant and massive movements of money crossing the border, and it's in full digitalization. Whoever has the architecture to capture it captures a huge share of recurring financial activity.

The digitalization already happened: the data point that changes everything

Here's the number that should move any bank in the region: in 2024, 99.1% of the remittance value arriving in Mexico did so by electronic transfer, according to the Bank of Mexico's remittance report. Cash and money orders, together, don't reach 1%. The remittance stopped being the man at the window collecting bills; it's a digital, instant flow seeking the cheapest and fastest rail. And cost matters: sending money to the region still costs around 6% on average, well above the 3% target the UN set in Sustainable Development Goal 10.c. Every point of cost your institution can shave with better technology is a direct competitive advantage.

Why a legacy core loses the flow

The problem isn't that banks don't want remittances; it's that their core doesn't know how to capture them. Three concrete technical reasons:

First, the language. Since November 2025, cross-border payments speak only ISO 20022—we covered this in another article. And in the migration to that standard, many institutions hit problems, the most common being that their legacy systems couldn't handle the new format's structured data: J.P. Morgan itself warns (as the bank providing the service) that the standard's enriched information can be truncated or omitted within existing reporting formats. A core that truncates that data creates friction, rejections, and compliance delays in exactly the flow it wants to capture.

Second, the rails. Capturing remittances today requires integrating with multiple payment rails and handling multiple currencies, with fast settlement. A monolithic, closed core, where connecting a new partner is a months-long project, simply doesn't compete with the fintechs that make it their business.

Third, the cost. If your infrastructure is expensive to operate, you can't offer the cheap remittance the customer wants. And the customer, increasingly, goes with whoever charges less: fees on modern digital rails are well below those of traditional services.

How a modern core captures it

A modern core flips all three. It speaks ISO 20022 natively, without truncating the enriched data the standard brings—data that improves compliance and reduces rejections. It integrates with multiple rails and handles multi-currency, so connecting a corridor or a new partner is consuming an API, not standing up a project. And its lower operating cost lets you offer a competitive remittance without losing margin. The difference between losing the flow and capturing it isn't commercial will; it's architecture.

The flow will only grow

This isn't an opportunity that closes. Cross-border payments and digital remittances keep growing at double digits, and new rails—including stablecoin-based ones, which already move a growing share of the US-Mexico corridor, according to the Inter-American Development Bank—are pushing costs down. The institution whose core can integrate whatever comes will capture that growth; the one that depends on a closed system will watch it pass to nimbler competitors.

How we see it at WAU

At WAU we design cores that capture the cross-border flow instead of losing it: native ISO 20022 without truncation, integration with multiple rails and currencies via API, and an operating cost that lets you compete on price. Remittances shouldn't be the fintechs' business because your core couldn't; they should be your flow.

If you watch the remittance flow go by and suspect your core isn't capturing it, let's talk. We'll help you see how much you're leaving on the table. 👉 Book a conversation with our team.

Sources

• BBVA Research — Mexico: record in remittances, $64,745 million in 2024 (Feb 2025)

• World Bank / KNOMAD — Remittances slowed in 2023, expected to grow faster in 2024 (Mexico 2nd recipient behind India) (Jun 2024)

• Inter-American Development Bank (IDB) — Remittances to Latin America and the Caribbean moderate their growth in 2024 ($161 billion) (Nov 2024)

• Bank of Mexico — Remittances, balance of payments (99.1% by electronic transfer in 2024)

• World Bank — The cost of sending remittances is higher than 3% in 28 countries (global cost ~6%, SDG 10.c target of 3%)

• J.P. Morgan (bank provider) — ISO 20022 migration: November 2025 as the exclusive standard and truncation of enriched data

• Inter-American Development Bank (IDB) — Stablecoins, remittances, and regulatory risks