What to do when cross-border payments in LATAM go wrong

This content is provided for informational purposes only. It does not constitute financial, legal, tax, or regulatory advice. Each company should evaluate its implementation with its own internal teams and professional advisors. Holiday calendars and rail behavior described here reflect information available as of September 2026; confirm critical dates with your Treasury and Compliance teams before scheduling payments. 

A payment leaves on Tuesday. By Thursday, Finance still cannot confirm it landed. Was it returned? Is a bank reviewing it? Did the receiving company dispute it?

For a team paying suppliers, payroll or contractors across more than one Latin American country, that three day gap is not rare. An estimated 14% of cross-border payments fail on the first attempt worldwide, and every failure carries a real cost before anyone has even confirmed what went wrong.

Most guidance on cross-border payments in Latin America covers what to check before a payment leaves: the right rail, the right beneficiary data, the right cutoff window. Fewer answer what Finance teams ask once something has already gone wrong. This is that answer: what a returned, disputed or delayed payment looks like inside SPEI, Pix, PSE and CBU/CVU transfers, and what to have ready before it happens.

A payment “going wrong” is not one problem, it is three

Under “the payment did not work,” Finance teams usually mean one of three different situations, and each one needs a different response.

• Returned. The money bounces back, usually because of an incorrect account, a closed account or a rejected beneficiary. Nobody disputes anything; the funds simply did not settle where they were sent.
• Disputed. The recipient, the sender or a bank flags the transfer as unauthorized, fraudulent or a mistake, and a formal review decides whether it gets reversed.
• Delayed. The payment is not rejected. It is paused inside a compliance review, a cutoff window or a manual check, and it settles later than expected, if it settles at all.

Treating the three the same is what slows a Finance team down the most. A returned payment needs corrected data and a resend. A disputed payment needs evidence and a formal claim. A delayed payment needs a status check, not a claim.

If your company is still deciding whether to launch in a new market at all, our readiness checklist for cross-border payments in LATAM covers the gates to clear before the first payment moves.

How four LATAM rails actually handle it

What to do in the first hours 

1. Contact your bank or IFPE immediately. Speed is still the single biggest factor in whether funds can be traced or frozen before they move again.
2. Pull your proof of payment. Reference number, timestamp and confirmation screen; every following step needs it.
3. Check the transfer status if a tracking tool exists. In Mexico, MI SPEI shows this directly; in other markets, your bank is the source.
4. Log the case as returned, disputed or delayed in your own records. Each path resolves differently, and mixing them into one “failed payments” bucket slows all three down.
5. Escalate if the bank or IFPE does not resolve it. Condusef in Mexico, the MED process in Brazil, BCRA in Argentina, or your bank's own complaints channel in Colombia.

Reduce how often this happens 

A few habits cut how often your team needs the steps above.

• Validate beneficiary data before the first payment to a new account, not after the first failure.
• Give every corridor a named contact inside your bank or IFPE before you need one.
• Track returns, disputes and delays as separate categories, not one “failed payments” total. A pattern inside a single rail is easy to miss inside a combined number.

How Bitso Business helps

None of this changes just because your company runs cross-border payments in Latin America instead of a single domestic rail. Bitso Business connects the outbound and inbound legs of a payment through one API for cross-border payments in LATAM, so a return, dispute or delay shows up against a single transaction record instead of a local bank statement and a separate spreadsheet.

In Mexico, that connection runs through SPEI. The same infrastructure supports mass payouts in Latin America at scale and, where it fits, funding through stablecoins for business payments and USD to MXN liquidity, so Finance traces one payment through every leg instead of reconciling each corridor on its own.

Before a dispute ever reaches this stage, our guide on fraud detection with AI in cross-border payments in LATAM covers how transaction screening works across these same corridors.

FAQs
 

What is the difference between a returned payment and a disputed payment?

A return has no dispute attached: the money did not settle where it was sent, usually because of incorrect account data, and it comes back on its own. A dispute means someone has formally flagged the transfer as unauthorized or mistaken, and a review decides the outcome.

Does Circular 14/2017 protect my company if a SPEI payment goes missing?

It sets the technical rules banks and IFPE follow to process, reject and return SPEI transfers between each other. It protects how the rail operates, not whether your company recovers funds sent to the wrong or a fraudulent account; that depends on how fast you contact your bank or IFPE.

Do mass payouts carry more dispute risk than single payments?

Not more risk per transaction, but more exposure at once. A batch inside mass payouts in Latin America can include hundreds of transfers, so even a low error rate produces several cases in the same cycle, which is why tracking each payment individually matters.

*NVIO México enables direct access to SPEI and delivers payment services fully compliant with Mexican regulation. NVIO Pagos México, S.A.P.I. de C.V., IFPE (“NVIO México”) is authorised and regulated by the Mexican National Banking and Securities Commission (CNBV). Learn more at nvio.mx/terms.