Explainers

Are Stablecoin Payments Safe? Business Risks and How to Cut Them

Are stablecoin payments safe? Eleven business risks, from reserves and custody to wrong addresses and limits, each with the control that reduces it.

Caio Barbosa

Founder & CO-CEO

Forbes Under 30. One of the leading voices in Fintech & Crypto in Brazil. Writes weekly about stablecoins, payments, and the future of financial infrastructure in Latin America.

Cover image for Lumx blog article: Are Stablecoin Payments Safe? Business Risks and How to Cut Them
Cover image for Lumx blog article: Are Stablecoin Payments Safe? Business Risks and How to Cut Them

Stablecoin payments are safe for a business when four layers hold: the stablecoin is fully backed and redeemable, the network confirms reliably, the provider's custody and controls are clear, and your own team checks each destination before money moves. They are not deposit-insured, and each layer fails in a different way.

Nothing can recall a confirmed transfer, so checks come before sending. The useful question is which risks below you have a control for. The instrument itself is in what a stablecoin is.

What are the risks of a stablecoin payment?

Eleven are worth a line in a risk register. Each row gives the failure, the control and the Lumx mechanism.

Eleven stablecoin payment risks, the control for each, and the matching Lumx mechanism.

Risk

What goes wrong

Control

On Lumx

Issuer and reserves

The coin trades below one dollar or redemption slows

Hold only issuers that publish reserves (what USDC is, what USDT is)

Wallets hold USDC and USDT only

Freeze

The issuer blocks an address

Screen counterparties before receiving

Transactions flagged by Chainalysis monitoring are held for review (RFI)

Contract or bridge failure

A bug in the coin's contract or in a bridge behind a wrapped copy depegs it

Use the issuer's own coin, not a wrapped or bridged copy

USDC and USDT only, on the networks in the next row

Network outage

A blockchain halts or fees spike

Use more than one network per coin

Ethereum, Polygon, Base and Tron for payouts and transfers, chosen per request

Wrong address or network

Funds land where nobody can return them

Confirm the address and network with the recipient before a first payment, and reject an unsupported coin and network pair

Fiat payouts go only to a destination registered under the customer; the Transfer endpoint takes coin and network together

Duplicate or forged instruction

A retry pays twice, or a fake webhook reports a payment

Idempotency keys, signature checks

Idempotency-Key header and signed webhooks

Custody

The party holding the funds fails or cannot release them

Get written answers to the four custody questions below

BitGo custody, one segregated wallet per customer and network, no omnibus (custodial wallets)

Funding-leg fraud

A deposit is reversed after the coins left

Hold unusual deposits; monitor the fiat leg

Flagged deposits held pending review

Cash exit

You cannot convert back, or hit a cap

Check the corridor, the cap and the quote lock first

Published limits; 30-second locked quotes (Lumx coverage)

Sanctions and holds

A payment is paused for a document

Describe the parties and purpose accurately

RFI compliance hold (what KYB is)

Quote movement

The rate moves between quote and payout

Lock the rate before quoting

Locks of 30 seconds, one or five minutes on one-off transactions

Chargebacks are in are stablecoin payments reversible.

A stablecoin is a claim on reserves

A dollar stablecoin promises that the issuer holds assets worth at least the coins outstanding and will redeem at par. In March 2023 USDC lost its dollar price on secondary markets after Circle said part of its reserves, held as uninsured deposits at Silicon Valley Bank, was out of reach. The Federal Reserve's FEDS Note on the episode records that the price recovered once the joint announcement of March 12 protected SVB depositors and Circle resumed redemptions on Monday, March 13. For a weekend, a finance team holding USDC could not redeem at par or say what its balance was worth.

A stablecoin is not insured like a bank deposit. The GENIUS Act (Public Law 119-27, signed July 18, 2025) will require identifiable reserves of at least one to one and bars calling a payment stablecoin federally insured. It takes effect on the earlier of January 18, 2027 or 120 days after final regulations (Section 20).

What the two largest issuers publish, read on November 1, 2026.

Issuer

What the page says

Circle (USDC)

Reserves disclosed weekly, plus monthly third-party assurance under AICPA standards

Tether (USDT)

Tokens backed 100% by reserves, circulation figures typically refreshed daily

Issuers can freeze either coin at an address: Circle's USDC terms and Tether's terms both reserve that right.

On Lumx, wallets hold USDC and USDT only, and a balance carries issuer exposure while it sits there, so pay out promptly.

Who regulates stablecoins, and the provider holding yours?

Stablecoin and provider rules in three jurisdictions, read on November 1, 2026.

Jurisdiction

Instrument

What it sets

Where it stands

United States

GENIUS Act, Public Law 119-27 (July 18, 2025)

Reserves of at least one to one; no claim of federal insurance

Takes effect by January 18, 2027 at the latest

European Union

MiCA, Regulation (EU) 2023/1114

Rules for crypto-asset issuers and providers, with a register of authorised providers kept by ESMA

In force since June 2023; issuer rules apply since June 30, 2024 and service provider rules since December 30, 2024; transitional periods end by July 1, 2026

Brazil

Res. BCB 520/2025 (November 10, 2025), with Art. 91 as amended by Res. BCB 589/2026

Authorization of virtual asset service providers; from November 6, 2026 Art. 91 bars banks and payment institutions from dealing with providers neither authorized nor in the process

In force, with a transition regime for firms already operating (Art. 88); payment institutions that settled eFX flows in stablecoins have until May 31, 2027 (Res. BCB 561/2026)

Ask the provider which regime it sits under. The Brazilian license is covered in the SPSAV license explained.

On Lumx, the position is this: Lumx has applied for SPSAV authorization and operates under the transition regime (Res. BCB 520/2025, Art. 88), so it keeps its banking access under Art. 91. External transfers are identified and reported to COAF as required, a transfer can be held through a transactional RFI (request for information, a hold that asks for a document before a transaction clears), and Brazilian customers are asked about self-custody on an external transfer. Lumx is not a bank. In the European Union Lumx holds no license of its own: EUR and GBP run through a banking partner, and Lumx does not claim MiCA authorisation.

Networks and transfers: what cannot be undone

A halted blockchain stops every payment on it until it recovers, so do not rely on one network for a payment with a deadline. On Lumx, each customer gets a wallet on every supported network: Ethereum and Polygon carry USDC and USDT, Base carries USDC, Tron carries USDT, and Stellar carries USDC only for the BRL on-ramp.

Nobody types a 42-character address, so it is copied from the wallet history, and an attacker can poison that history with a transfer from a look-alike address sharing the first and last characters. Researchers call this address poisoning and counted 6,633 successful incidents and at least $83.8 million in losses on Ethereum and BSC over two years (USENIX Security 2025).

The network will not undo it. Other mistakes are the right address on a network the receiver does not watch, or a coin it cannot accept. Confirming the address and network with the recipient before a large first payment, and a system that rejects an unsupported coin and network pair, cover most of it. A retry after a timeout can also pay twice, which an idempotency key prevents.

On Lumx, a fiat payout can only go to a destination registered under the customer, with the holder relationship declared, so there is no free-text bank detail at the moment of sending. A stablecoin transfer names the coin and network together, and limits apply per transaction type. Any POST, PUT or PATCH can carry an Idempotency-Key header: the same key with the same body returns the stored response, and a different body returns a conflict.

Where the provider holds the money

If a provider holds funds between steps, you are exposed to its solvency. Four questions, in writing, settle most of it: whose name the assets are held in, whether they are separated from the provider's operating funds, who can move them, and what happens to them if the provider stops operating. Custodial or not is a design choice, compared in custodial vs non-custodial wallets for businesses and defined in what a custodial wallet is.

<!-- OPERATOR PARAGRAPH --> I treat custody as a document request, not a feature comparison. Before a finance team signs with any provider, including us, I would ask for those four answers on paper. A provider that answers in marketing copy has told you something about the fourth question.

On Lumx, the answers are these. Wallets are custodied by BitGo, which carries insurance. Segregation is total: every customer has separate wallets, balances never mix with other customers' or with Lumx's, and there is no omnibus account. Lumx is custodial by design, so the client does not hold the keys. On the fourth question, the standard contract covers the sequence for returning funds on exit, the export of history and addresses, and a liability cap. The balance is stablecoin, not a deposit, because Lumx is not a bank. A payout debits the customer's own wallet to a destination registered under that customer, or moves to another onboarded customer's wallet, because Lumx does not allow pooling funds for unboarded third parties.

Fraud, screening and holds

Address poisoning, above, is one pattern. In wallet phishing, a fake site tricks the holder of a self-managed wallet into approving a transfer. In a reversed funding deposit, a fraudster pays in by a pull-based bank transfer, takes the stablecoin, and has the deposit returned. Confirm addresses through a second channel, never approve a wallet request you did not start, and hold unusual deposits until the funding leg settles. Verify the signature on any event before acting.

Screening is the other half. Describe the parties and purpose accurately, and screen counterparties as in stablecoin AML compliance for fintechs.

On Lumx, every customer completes KYC (an individual) or KYB (a company and its owners) before the first transaction. KYC runs through Sumsub, and every transaction, inbound or outbound, is screened before it executes. Blockchain activity is monitored by Chainalysis, which covers every kind of wallet, external receipts included, and fiat is monitored by Lumx's own systems with oversight from the banking partners. Lumx is aligned with the Travel Rule, and wallet destination addresses are coming to the API as destinations, like fiat accounts. A flagged transaction is held pending review. Compliance may send an RFI about the link between sender and receiver and the purpose. The 24-hour response window applies to every transaction, and with no reply it may be refunded to the sender. A limit increase is not an RFI unless it is a requirement to approve a transaction. See also why stablecoin payouts get rejected.

Webhooks carry a signature over the raw body, and anything older than five minutes should be rejected.

Getting back to cash: limits and quotes

The risk shows up when a business holds coins assuming it can leave at any size, then meets a cap it did not plan for.

Default Lumx limits, from the transaction limits page read on November 1, 2026. They apply to every customer.

Limit

KYC Standard

KYB Standard

Per transaction

$7,500

$50,000

Daily

$15,000

$100,000

Monthly

$15,000

$100,000

Enhanced tiers set limits from the documents submitted. A transaction over a limit is rejected with a 422, TRANSACTION_LIMIT_EXCEEDED.

On the quote side, a locked rate fixes the conversion for 30 seconds, one minute or five minutes; the 30-second lock has no fee, and an expired lock is void. Autoconversion rules always convert at market.

When a stablecoin payment is the wrong tool

It is wrong when you collect from strangers who expect chargeback rights, for months of idle treasury cash, and where no supported rail reaches the recipient. Against wires and cards, stablecoins are different rather than strictly safer: a card gives the payer a dispute process and a wire can be queried through the banks, while a confirmed stablecoin transfer has neither. The comparison is in stablecoins versus SWIFT. On Lumx, a supplier in mainland China is paid in USD by SWIFT.

What these controls look like on a Lumx payout

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.

A Brazilian company paying a US supplier registers the supplier as a destination with the SUPPLIER relationship. The off-ramp debits the company's wallet, each status change fires a signed webhook, and a monitoring hold comes back as an RFI. None of this makes a payment loss-proof; it moves the checks before the point of no recall. A named virtual account takes local currency in the customer's name; see also named virtual accounts, global payments, the operator map and supported countries.

Methodology and sources

Lumx docs read on November 1, 2026: wallets, destinations, exchange rates, transaction limits, RFI, idempotency, webhooks and the Transfer endpoint. Issuers: Circle and Tether. The BCB resolutions (520/2025, 589/2026, 561/2026) are linked in the table, and the Art. 91 amendment and the May 31, 2027 date follow our own analysis. The MiCA dates come from the ESMA page and Regulation (EU) 2023/1114. Freeze rights are from the Circle and Tether terms.

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

Cover photo: Venti Views on Unsplash.

  • Are stablecoin payments safe for businesses?

    They can be, when the coin is backed and redeemable, the network is reliable, custody is clear and your team checks each destination before sending. On Lumx, each customer is verified before the first transaction, fiat payouts go only to registered destinations, and flagged transactions are held for review.

  • Are stablecoins FDIC insured, and can they lose the peg?

    No to the first, yes to the second: USDC lost its dollar price in March 2023 when part of its reserves sat at a failed bank. Protection comes from reserves, not deposit insurance. On Lumx, a deposit converted by an autoconversion rule stays stablecoin until paid out, so paying out promptly limits the exposure.

  • Are stablecoins regulated?

    Yes, in pieces: the GENIUS Act in the United States, MiCA in the European Union and Res. BCB 520/2025 in Brazil. None insures a balance. Lumx has applied for SPSAV authorization, operates under the Article 88 transition regime and is not a bank.

  • What happens to my funds if my provider stops operating?

    It depends on whose name the assets are held in and whether they are separated from the provider's funds: if they are, you hold a claim on identifiable assets, and if not, you may queue as a creditor. Lumx is custodial by design: wallets are custodied by BitGo, which carries insurance, every customer has separate wallets with no omnibus account, and the balance is stablecoin, not a deposit, because Lumx is not a bank.

  • What happens if a stablecoin payment goes to the wrong address?

    A confirmed transfer cannot be recalled, so recovery depends on whoever controls the address. On Lumx, a fiat payout can only go to a destination registered under the customer. A stablecoin transfer names the coin and network together, with limits per transaction type. An idempotency key stops a retry from paying twice.

Stay up to date with what Lumx is developing.

Sign up to receive them by email.

Share on socials:

are-stablecoin-payments-safe

A

are-stablecoin-payments-safe

Are Stablecoin Payments Safe? Business Risks and How to Cut Them

Copy link

Copied!

are-stablecoin-payments-safe

TALK TO OUR TEAM

Ready to transform your business with stablecoins?

Discover how our infrastructure can seamlessly integrate stablecoins into your financial operations quickly, securely, and efficiently.

Explainers

In this page

©2026. All rights reserved.

Lumx US OP LLC ("Lumx") is a financial technology and payments infrastructure company. Lumx US OP LLC is a Money Service Business (MSB) registered with the Financial Crimes Enforcement Network (FinCEN) (MSB #31000316459619). Lumx is not a state-licensed money transmitter and does not, in its own capacity, engage in the provision of regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial-institution partners.


Lumx is not a bank, financial institution, payment institution, or custodian of client funds. Certain services made available through the Platform may be provided by duly authorized and regulated third-party partners, in accordance with applicable laws and regulations.

Please refer to Lumx’s Terms of Use and Privacy Notice for further information regarding the conditions governing the use of the Platform and the processing of your personal data.