Stablecoin settlement is already in production. What payment institutions can take from Latin America

Plenty of payment institutions still file stablecoins under "interesting, but later." That's a fair call. It's also getting harder to defend. 

In December 2025, Bitso Business, the B2B arm of Bitso, one of Latin America's leading digital financial services providers, said it was on track to process $82 billion in annualized total payment volume for more than 1,900 institutional clients. That figure is expressed in US dollars and covers every rail Bitso Business runs: local peso payments, US wires, SEPA and the stablecoin rails it uses for FX and treasury between pesos, dollars and euros. That's not a pilot. That's a payments business.

So what is stablecoin settlement? Stablecoin settlement is the transfer of value between two parties in a regulated, FIAT-backed stablecoin, such as USDC or EURC, instead of through correspondent banks or a card scheme. It runs 24/7, reaches finality in seconds to minutes, and leaves a record both parties can verify.

For a payment institution, it is one leg of an ordinary payment, not a new product. Your customer pays in their currency. Your beneficiary receives theirs. Only the leg in between settles in a stablecoin. That leg runs on weekends, needs less money parked in advance, and you can start with a single flow.

Polygon's 2026 report on Latin American payments maps the companies doing this, corridor by corridor. The interesting part isn't the volume. None of these companies won because of the stablecoin. They won because of everything they built around it: connections to local payment systems, liquidity, compliance, reconciliation and exception handling, all running as one flow. At NetiRails, we build the operating layer these companies built for themselves.

Here's what they built, which of your problems it solves, what you shouldn't copy, and how to work out whether one of your flows is worth moving.

What does stablecoin settlement look like in production?

It looks like ordinary payments with a different settlement leg in the middle. FIAT goes in, FIAT comes out, and the customer sees one payment and one price. Behind it, a production flow runs in five steps:

1. Pay-in. The customer pays in local currency on a local rail, for example into a virtual account.
2. Screening. Sanctions screening, transaction monitoring and Travel Rule data run before any value moves.
3. On-ramp. The FIAT amount converts into a regulated stablecoin.
4. Settlement. The stablecoin moves to the beneficiary side. This leg is final once confirmed, on a Sunday as on a Tuesday.
5. Off-ramp and payout. The stablecoin converts back to FIAT and pays out on the beneficiary's local rail.

Three patterns from Latin America are worth knowing, because each maps to a problem European institutions already have.

• Collection from any rail, settlement in one currency. BlindPay's Named Virtual Accounts let a business receive US payments by ACH, wire, RTP or SWIFT into an account in its customer's name. The deposit converts automatically into a stablecoin. Several inbound rails, one settlement asset.
• Direct connection to local instant payment systems. Bitso Business reports $15.6 billion in annualized real-time payments in Mexico alone, with direct access to local real-time payment infrastructure. Brazil's Pix and Mexico's SPEI run around the clock, so a flow that settles in a stablecoin can also pay out on a Sunday.
• Banks and regulated firms on the issuing side. In Brazil, Braza, a group built around an FX bank, issues a real-backed stablecoin. A consortium of Mercado Bitcoin, Bitso, Foxbit and CAInvest issues another, BRL1. This is not a market of startups alone.

The regulators noticed. Brazil's central bank published Resolutions 519, 520 and 521 on 10 November 2025, in force since 2 February 2026. They bring international payments with stablecoins inside the foreign exchange framework, with reporting to match. That is the signal a supervised institution should read: stablecoin settlement is being treated as payments and FX, not as an experiment.

Why does weekend liquidity matter for stablecoin settlement?

Because cross-currency settlement still stops when the banks stop, and your treasury pays for every hour of it. A domestic euro payment can be instant on a Saturday. A payment that needs a US dollar leg often cannot: the Fedwire Funds Service runs Monday to Friday, and the Federal Reserve's own plan to add Sundays and weekday holidays is set for no earlier than 2028.

For a payment institution, Friday afternoon to Monday morning is where capital gets locked. Funds sent on Friday sit in transit. Liquidity has to be held on both sides to cover the gap. Treasury plans around the calendar instead of around demand.

Stablecoin settlement runs 24/7. Combined with local instant payment systems at either end, it lets part of your volume settle on a Saturday the same way it settles on a Tuesday.

The honest version of this argument is narrower than most vendor pages make it. You do not need to move 100% of your traffic. The case is strongest for the specific flows where weekends and holidays lock the most capital: B2B payouts to markets with slow correspondent chains, treasury moves between your own entities, and corridors where volume peaks on Fridays. Moving even part of that volume to instant settlement changes how much liquidity you have to hold.

How does stablecoin settlement reduce prefunding?

It lets you stop parking money in every market. Instead of a balance per corridor, you hold one settlement asset and move it when a payment actually needs it.

You know the correspondent version. Every new corridor means another nostro account, funded for your busiest day and sitting idle the rest of the month. Add a market, add capital you can't use.

The Latin American operators flipped that. They hold value in one settlement currency and convert at the edge, only when a payment leaves. So the question stops being "how much do we park in each country?" It becomes "where do we get liquidity for this payment, and what does it cost?"

That leaves you two models, and you pick per flow:

• Pre-funded. You keep a balance with your on-ramp or off-ramp provider. At high, steady volume, it's often the cheaper option.
• Per transaction. You source liquidity for each payment from a provider you contract directly. Parked capital turns into a cost you pay only when a payment completes.

Neither one wins by default. We break down both in who holds the money in transit. What matters is that the choice is yours, and you can switch when your volume changes.

What happens when a payment stops halfway?

It happens, and any provider who tells you otherwise is not describing a real payment system. The question is whether you can see it, attribute it and resolve it with evidence. In a flow that crosses a bank, a stablecoin transfer, a conversion and a payout, one payment becomes several separate balance positions, each with its own timing, fee and failure mode.

This is where most of the work sits, and it is the part the Latin American operators rarely talk about in public. Take a customer paying a euro invoice with a stablecoin. The customer sees one instruction at one price. Internally, the funds sit in at least five places in turn: the paying wallet, a pooled settlement wallet, a position at the FX provider, the customer's euro account and the outbound bank transfer. Each has its own timing, fee and evidence.

What makes a flow like this production-grade is not the transfer itself:

• A defined owner of the funds at every step, including the moments where a transfer stopped halfway.
• A self-hosted double-entry ledger that records every leg, fees included, as immutable entries.
• Daily reconciliation against what each partner reports, with a defined resolution path for every class of mismatch.
• An exception list with financial answers: underpayment, failed screening, funds on the wrong network, a rejected payout. Each one mapped to a refund, a manual credit or a confirmation, with a record of who changed what.

The team behind NetiRails built this ledger and exception model in production for Damisa.

None of these can be added once the flow carries live volume, because every balance and every reconciliation rule depends on them. We cover the reconciliation mechanics in why reconciliation is the final frontier of payment orchestration.

Will stablecoin settlement pass compliance?

Only if compliance is designed into the flow, not attached at the end. Sanctions screening, transaction monitoring, Travel Rule data, limits and approvals have to fire before value moves, and each has to leave its own evidence.

In the EU, the perimeter is already defined. MiCA regulates e-money tokens, the category most FIAT-backed stablecoins used for payments fall into. The Travel Rule applies to transfers of crypto-assets under Regulation (EU) 2023/1113. DORA governs how you manage the third parties in the flow. None of this is optional, and none of it is new work only for stablecoins: it is the same control discipline you already apply to card and bank payments, extended to a new settlement leg.

What matters in procurement is simple. Not what a vendor claims about compliance, but what evidence the platform produces on the day your supervisor asks for it.

Ready-made rails already do this. Why build around them?

For many institutions, a ready-made provider is the right choice. The real question is which operating model you accept with it. There are three, and each fits a different institution.

• Hosted stablecoin platforms, such as Bridge (part of Stripe) or BVNK. Strong products, fast to launch, one API. You also get their model: their FX, their liquidity and custody partners, their compliance stack, their roadmap and their pricing. That works when your flows fit it.
• Custody and wallet infrastructure, such as Fireblocks. It secures and moves the asset. FX, screening, the ledger, reconciliation and exception handling around it stay yours to build.
• An in-house build. Your IT team can write the code, but in our experience the code is about 20% of the work. The other 80% is payments domain: custody, on-ramp and off-ramp, compliance, exceptions and reconciliation, all of which have to be right from the first live payment.

NetiRails is built for institutions that need the speed of a ready platform and the control of their own build. It is a stablecoin payment orchestration platform for licensed payment institutions. It connects payment execution, FX, compliance and reconciliation into one operational system, and it runs on your infrastructure, not ours. That changes three things:

• Your providers. Custody, on-ramp and off-ramp, FX, screening and reporting are modules you choose per market, on your contracts. Replace one without rebuilding the flow, so you are never locked into a single vendor.
• Your rates and your rules. Your own FX at your own rates, your own KYC and AML providers, your own approval processes.
• Your supervisor's questions. Data and infrastructure stay inside your institution, so DORA third-party reviews and data-residency questions start from your perimeter, not a vendor's.

If a hosted platform fits your flows today, use it. If you need to own the FX, the compliance stack and the infrastructure, that is the gap NetiRails is built for. For a wider map of the provider landscape, see how to choose a stablecoin infrastructure partner.

What not to copy from Latin America

Two things.

Concentration on one provider. By Polygon's own figures, more than 43% of non-USD stablecoin transfers run on its network, and the operators it profiles lean on a small set of partners. That works while conditions hold. For a supervised institution, a single point of dependence in the settlement path is a DORA finding waiting to happen. Design the flow so a provider can be replaced without rebuilding it.

Growth-stage risk appetite. Many of these operators were built on venture funding, in markets where the alternative was very slow or very expensive. A European payment institution has a different starting point: working rails, a regulator, customers who expect nothing to break. The lesson is the operating layer, not the pace.

Is stablecoin settlement worth it for your institution?

For some of your flows, yes. Not for all of them. The good news: you can find out which ones before you spend anything.

It pays off where a flow already hurts. Settlement takes days, capital sits parked to cover it, or your ops team spends hours fixing exceptions. If none of that is true today, leave the flow alone.

To check one flow, pull six numbers:

1. How much you settle a month, and in how many transactions
2. How long settlement takes today, weekends and holidays included
3. How much capital you hold in advance to cover it
4. What you pay providers and correspondents now
5. What exceptions and manual reconciliation cost you
6. What the new path would cost: on-ramp, off-ramp, screening, liquidity and the platform

Watch number six. Whatever the pricing model, the platform lands in your budget as a fixed cost before a single payment has saved you anything. So here's the test: the platform has to pay for itself on one flow. Not on the five flows you might add next year.

If the numbers work at your real volume, start there. One flow, one market, with compliance and reconciliation live from the first payment. With NetiRails, an MVP of that flow is installed at your institution in three months. And if the numbers don't work? You've lost an afternoon, not a budget.

What NetiRails doesn't do

A few things you should hear from us now, not find out in procurement.

• We don't hold your clients' money. Not at any step, not for a minute.
• We don't provide liquidity. We're not a party to your on-ramp or off-ramp contracts. Those stay yours.
• We don't take a cut of your FX.
• We don't hold a licence for you. The regulatory call stays with you and your counsel.

And we won't tell you exceptions never happen. They do. What we'll show you is how each one gets caught, resolved and evidenced.

Bring us the flow that costs you the most

You probably already know which one it is. The flow that stalls every Friday afternoon. The corridor where more money sits parked than you'd like. The one your ops team dreads at month end.

Bring that flow to a 45-minute call with us. Book it at netirails.com/contact.

What to bring:

• Monthly settlement value and number of transactions
• How you settle it today, weekends included
• Roughly how much capital sits under it

What you leave with:

• A straight answer on whether stablecoin settlement makes sense for that flow
• A first view of the capital and operating cost it could free up
• If the answer is yes, what the first three months look like: providers, compliance and reconciliation, in that order

If the answer is no, you'll hear that too. Either way, you walk out knowing more about that flow than you did walking in.

Book your 45-minute flow review with NetiRails