Insurance claim payouts across borders: Pix, SPEI and SEPA

An insurance claim payout across borders is a settlement paid to a claimant's bank account in another country, in the claimant's own currency, for the amount the insurer approved. Insurers fund it in USDC, convert at a locked rate and pay over a local bank rail, so the approved figure lands intact and the payment leaves a record.

What makes a claim payout different from a supplier payment

A supplier payment repeats, goes to a company and carries an invoice. A claim payment goes once, to a person, and carries a decision. Four traits follow. The amount is owed in the claimant's currency, and someone bears the exchange-rate move between approval and payment. The claimant is waiting, so a rail that settles on a Sunday matters, and is new to the insurer. And every payment is evidence that a regulator, a reinsurer or an auditor can ask about later. How a USDC payment becomes a local bank payment is covered in what a stablecoin corridor is, and the conversion step in what a stablecoin off-ramp is.

How does an insurer pay a claim in the claimant's currency?

The insurer approves the claim in the claimant's currency, funds the payout from a USDC balance (the dollar stablecoin explained in what USDC is), converts at a rate locked on the approved amount, and sends the result over the rail that serves the claimant's country. The claimant never handles USDC.

The six steps of a stablecoin-funded claim payout, and what each one is on Lumx.

The quote follows the screen, because a lock lasts from 30 seconds to 5 minutes. On Lumx, the insurer is the customer that completes KYB (know your business, the verification of a company and its owners, see what KYB is), holds the USDC wallet and owns every destination. The docs accept an insurance company as a business activity and list it neither as high risk nor as prohibited. Deposits into the insurer's Lumx account in BRL, MXN, USD, EUR or GBP convert to stablecoin automatically under an autoconversion rule, or the insurer transfers stablecoin to the wallet address. A payout debits that balance.

Fix the approved amount, not the USDC

If the insurer sends a fixed number of USDC, the claimant gets whatever that converts to on the day, and the move cuts both ways: the claimant can be short, or the insurer can pay more than it owed. The table uses real closing rates from the Central Bank of Brazil for a claim of BRL 12,000 approved on a Friday and paid the next Monday, because PTAX is published on business days. PTAX is a reference rate, not a traded price, and the example leaves fees out and treats one USDC as one dollar, so it shows the size of the movement only.

PTAX sell rates published by the Central Bank of Brazil, applied to a claim of BRL 12,000 approved on a Friday and paid on the next Monday.

A claimant short by BRL 546.50 calls the insurer, and a payment BRL 1,102.88 too high goes unseen until the books close. A quote on the receiving side removes both.

On Lumx, a locked quote accepts a source or a target amount, so the claim amount goes in as the target. The lock lasts 30 seconds, 1 minute or 5 minutes; only the 30-second lock has no fee. The off-ramp request carries the quote's exchangeRateId and no amount.

Which rail fits which claim?

The claimant's country and currency choose the rail. Pix (Brazil's instant payment system, run by the Central Bank) and SPEI (Mexico's interbank transfer system, run by Banxico) run every hour of every day, which suits urgent claims.

Payout rails for claim payments on Lumx, as of November 2026, from the Lumx coverage and cut-off documentation.

Bre-B (Colombia's instant payment system) is fixed per destination, so a Colombian claim that could exceed the cap needs an ACH Colombia destination from the start: a payout above the cap is refused and never split. The cap is a central bank rule.

Large claims meet the insurer's own transaction limit first, which belongs to the customer and not to the rail. A standard KYB customer has USD 50,000 per transaction and USD 100,000 per day and per month, and higher limits need enhanced verification and a documented request, as limits and cut-offs by rail explains. On Lumx, the limits are global and the remaining headroom can be read before a payout.

Checks before the money moves

Three checks sit between approval and release: sanctions, the claimant's identity and the bank account's ownership.

Sanctions screening should run again at payment. The U.S. Treasury's OFAC says in FAQ 65, updated November 13, 2024, that insurers should consider screening at policy issuance, renewal, amendment, claim submission and claim payment, because its lists change often. That guidance is written for insurers under U.S. jurisdiction, and every other insurer follows its own regulator and its reinsurers. FAQ 104 covers travel insurance and Cuba, so route any claim touching a sanctioned country to compliance before any quote. I would run the decision to pay and the release of the payment as two steps with two owners. The adjuster approves an amount in the claimant's currency, and a payments operator then re-screens the claimant, asks for the quote and submits the payout, because a quote lives for five minutes at most and a sanctions list can change between approval and payment. I would pay only the claimant's own account by default and treat a late change of bank account as the first thing to review for fraud, since that is where a stolen identity turns into money leaving the building.

The provider screens too, and that does not replace the insurer's screen. On Lumx, each destination carries the holder's name, tax ID and address plus a holder relationship from a closed list. A new destination starts as under verification, and the destinations.approved or destinations.final_rejection webhook reports the result, so release the payout only to an approved destination. The claimant's identity data is what the insurer collected at claim submission, and the insurer owns it. The SELF relationship means the customer paying its own account, so a mismatch between the holder's tax ID and the customer's returns HOLDER_TAX_ID_MISMATCH. A claimant is never SELF.

Two fields are set before the first payout. The relationship for a claimant is CUSTOMER, which the docs describe as the customer's clients for refunds, rebates or other customer obligations. The purpose is the other: none of the nine values is specific to claims, and PERSONAL_ACCOUNT is valid only with SELF, so it does not apply to a third-party claimant. Agree the purpose with the insurer's compliance team, because one that does not match the activity can hold the payment for review.

The insurer's own regulator and its reinsurers set the rules for paying a claim.

What the claims file should hold

An auditor should be able to rebuild the payment from the file alone:

• the approved amount in its currency, and who approved it

• the screening result and its date

• the quote id, the locked rate, the fee lines and the USDC amount sent

• the payout id, the rail, the delivered amount and the completion time

• for SWIFT, the UETR and the MT103 confirmation

• the destination holder and relationship

On Lumx, a transaction accepts a metadata object, so the claim number travels with the payout and returns in the webhook, and the receipt carries the rate, both amounts and the fee lines. Settlement tracking is UETR and MT103 confirmations on every SWIFT payout, a per-rail reference on every transfer and webhooks.

When a claim payout stalls

An expired lock returns EXCHANGE_RATE_EXPIRED, and the answer is a new quote on the same approved amount. A retry needs the same idempotency key, because a new key is a second claim paid. A hold shows as an RFI (request for information, a compliance hold that asks for a document), and the answer is the document. Common refusals: why a stablecoin payout gets rejected.

On Lumx, the transaction moves through TRANSFERRING_STABLECOIN, TRADING and TRANSFERRING_FIAT to SUCCESS, and offramp.failed reports a failure. Compliance asks for the relationship and the purpose, and a transaction with no reply in 24 hours may be refunded to the sender.

When a stablecoin claim payout is the wrong tool

• The claimant is in the insurer's own country and currency. A domestic bank transfer is simpler.

• The paying entity is not the insurer. An administrator paying claims for several insurers from one account is nested payments and needs written approval from Lumx; otherwise each insurer pays from its own record. Marketplace payouts follow the same rule.

• The claim is in EUR or GBP and the claimant is outside the SEPA area or the UK. Lumx's SWIFT runs in USD only, so those claims stay with the insurer's bank.

What a claim payout looks like on Lumx

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

The insurer onboards once as a business customer from a supported country and keeps USDC in a custodial wallet. Each claimant becomes a destination with the rail's own identifiers: a Pix key, a CLABE (the 18-digit Mexican bank account number), an IBAN and a BIC for SEPA, or a sort code and an account number for Faster Payments. Each destination is registered with the CUSTOMER relationship, never SELF. The claims system asks for a locked quote on the approved amount, checks it and pays with the quote id and a purpose agreed with compliance. Webhooks report each status until offramp.success. On a BRL payout the claimant sees the insurer as the payer, as the Brazil step-by-step shows, and Lumx takes no fee from a Pix or SPEI recipient's amount.

Lumx describes its pricing as: "monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans". No pre-funding means the insurer keeps no capital parked in settlement accounts before a payout: conversion and settlement happen when the payout starts, funded from the insurer's own USDC balance. The fee lines sit inside the quote. The flow is on the global payments page and current rails on the coverage page.

Methodology and sources

Lumx behavior was read from the docs on November 1, 2026: coverage, payment rail cut-off times, exchange rates, destinations, transactions, nested payments, transaction limits, Request for Information and the off-ramp API reference.

The BRL rates are PTAX sell rates from the Central Bank of Brazil's open data service, queried on November 1, 2026, using the last bulletin of each business day. The table figures are computed from them.

The sanctions guidance is OFAC's FAQ 65 and FAQ 104, read on November 1, 2026 and updated November 13, 2024. The Bre-B ceiling is the 1,000 UVB limit in Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2, sheet of March 31, 2026.

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Lukas Tennie on Unsplash.