Stablecoin settlement finality: when is an onchain payment final?

A company sends $1 million in USDC to a supplier. The transaction appears onchain almost immediately, and the recipient's wallet shows the funds. But is the payment final?

That depends on the blockchain, how many confirmations the company requires and what happens if the network reorganizes before the transaction reaches finality.

For finance teams, the distinction matters. Recording a payment before it becomes final introduces reconciliation risk. Sending funds to the wrong recipient can create a loss that no payment provider can reverse. And the legal protections companies rely on in traditional financial systems don't necessarily extend to an onchain transfer.

Understanding when a stablecoin payment becomes final is therefore an important part of managing treasury operations across fiat and digital assets.

How settlement works onchain

Traditional payment systems distinguish between clearing, settlement and finality.

Clearing is the process of transmitting, checking and reconciling payment instructions. Settlement is when the transfer discharges the financial obligations between the parties. Finality is the point at which that settlement becomes irrevocable and unconditional.

The Committee on Payment and Settlement Systems (CPSS) established these distinctions in its 2003 glossary. The 2012 Principles for Financial Market Infrastructures (PFMI) added an important legal dimension: final settlement is a legally defined moment.

In traditional banking, these stages can happen separately. A payment may be accepted and visible to both parties while settlement remains provisional.

In some net settlement systems, for example, transfers remain provisional until participants meet their obligations. If a participant defaults, unsettled transfers may need to be reversed and the remaining positions recalculated. This process is known as unwinding.

Blockchain transfers work differently.

When an ERC-20 token moves from one wallet to another, the blockchain updates the token balances and records the transfer within the same transaction. There is no separate clearinghouse processing the payment afterward.

The Financial Stability Board (FSB) recognized this distinction in its 2020 analysis of cross-border payments, describing peer-to-peer models as combining clearing and settlement.

But a successful onchain transaction does not necessarily mean the transfer has reached finality.

The network still needs to confirm that the transaction is final, and different blockchains do this in different ways.

When does a blockchain transaction become final?

There is no universal confirmation threshold for stablecoin payments.

Each blockchain has its own consensus mechanism, confirmation process and approach to finality. A payment that appears settled on one network may still be vulnerable to reorganization on another.

Bitcoin: finality increases with confirmations

Bitcoin uses probabilistic finality. Each new block after a transaction makes reversing it progressively harder.

Satoshi Nakamoto described reversing a sufficiently confirmed transaction as computationally impractical, rather than strictly impossible.

Ethereum: finality through proof of stake

Ethereum uses proof of stake and has a more explicit finalization mechanism.

Blocks are proposed in 12-second slots, with 32 slots per epoch. Under normal conditions, finalization takes roughly 13 to 15 minutes, although it can take longer.

Once a block is finalized, reversing it would require a severe violation of Ethereum's consensus rules, with at least one-third of the total staked ETH subject to penalties.

That gives finance teams a clear distinction between a transaction that has appeared onchain and one the network has finalized.

Solana: confirmation and finalization are different states

Solana exposes three commitment levels:

• Processed: The transaction has been processed by a node.
• Confirmed: A supermajority of stake has voted on the block containing the transaction.
• Finalized: The block has reached the network's highest commitment level.

An accounting system that records a transaction at confirmed rather than finalized is accepting a different level of settlement risk.

That may be reasonable for some payments. But it should be a deliberate policy decision, particularly for high-value transfers.

Why this matters for treasury

A company processing payments across Ethereum, Solana and other networks cannot apply one confirmation rule to every transaction.

Its treasury policy needs to define when payments are considered final for each supported network. The accounting system must then recognize those states consistently.

Under MiCA Article 82(2), ESMA's guidelines require crypto-asset service providers to estimate the time or number of block confirmations needed for a transfer to become irreversible, based on the relevant network.

The practical question for a finance team is straightforward: when does a payment move from pending to settled in the company's financial records?

What happens when a payment goes wrong?

Stablecoin payments are often described as irreversible, but several traditional payment systems already have irreversibility as a feature.

What matters is who can recover the funds, under what conditions and who is responsible when something goes wrong.

Consider four common payment methods.

Fedwire

Under Federal Reserve rules, a Fedwire transfer becomes final and irrevocable when the receiving bank credits the account.

After acceptance, cancellation generally requires the receiving bank's agreement. A court may still order the recovery of funds in certain circumstances, but that is separate from reversing the payment through Fedwire.

SEPA Instant

A SEPA Instant payment can be subject to a Request for Recall, but the recipient's consent is generally required for funds to be returned.

The European Payments Council's rulebook has no Return procedure for SEPA Instant. Returning the money is a new payment.

We covered these differences in more detail in what your bank account was doing that your wallet is not.

ACH

For ACH credit transfers, the originating bank can request that a payment be returned.

However, Nacha's rules leave the receiving institution to decide. The receiving bank must respond within the prescribed timeframe, but it is not automatically required to return the money.

Card payments

Card networks offer stronger dispute and chargeback mechanisms.

Visa's rules generally provide a 120-day dispute window for certain transaction categories, subject to specific conditions and, in some cases, longer outer limits.

Chargebacks exist because card networks require them. They are not inherent to the movement of money.

What changes with stablecoins?

With a direct onchain payment, no institution may operate the transfer and be able to process a recall request.

A company can send funds directly from its wallet to another address without relying on a bank or payment network to execute the transaction.

Of course, many businesses use custodians, exchanges and payment providers to manage stablecoin transactions. Those intermediaries have customer agreements, support teams and legal obligations.

But even when an intermediary is involved, it cannot simply reverse a finalized blockchain transaction.

Some stablecoin issuers have additional powers, including the ability to freeze certain token balances. That does not create a general right for a sender to recover funds.

For example, Circle states in its USDC terms that transactions cannot be reversed or recalled once initiated.

This has a direct operational consequence: the recipient, amount, asset and relevant approvals need to be checked before the transaction is broadcast.

After settlement, recovery may depend on the recipient's cooperation, the issuer's available powers or legal proceedings.

How regulation addresses settlement finality

Stablecoin regulation has advanced significantly, but the frameworks emerging in Brazil, the United States and the European Union address different aspects of the payment process.

They establish requirements for issuers, service providers, authorization, custody and recordkeeping. They do not generally give a payer the ability to reverse a finalized transfer.

Brazil: defining who can process cross-border payments

Brazil's Central Bank has introduced rules governing the use of virtual assets in foreign exchange and cross-border payment services.

Resolution BCB 561, effective October 1, 2026, prohibits eFX providers from settling with foreign counterparties using virtual assets.

Licensed virtual asset service providers can still use stablecoins in certain cross-border transactions under Resolution BCB 521, including a $100,000 per-transfer limit where the counterparty is not authorized to operate in foreign exchange.

Another restriction took effect on October 30, 2026. Under Article 91 of Resolution BCB 520, institutions authorized by the Central Bank can no longer deal with virtual asset service providers that are neither authorized nor undergoing authorization.

These rules set out which institutions can participate in specific transactions and under what conditions.

They do not introduce a mechanism for reversing a stablecoin transfer once it has reached blockchain finality.

United States: issuer obligations under the GENIUS Act

The GENIUS Act, signed into law on July 18, 2025, establishes a federal framework for payment stablecoins.

Its provisions cover issuer authorization, reserves, redemption and compliance with lawful government orders.

Section 4(a)(6)(B) requires issuers to maintain the technical capability to comply with orders to seize, freeze or burn stablecoins.

That capability serves a legal and regulatory purpose. It does not give an individual payer a right to reverse a transaction after sending tokens to the wrong address.

The Act also requires issuers to publish redemption policies and procedures for timely redemption, without prescribing a universal number of days for completion.

Redemption and settlement serve different purposes. Redemption allows an eligible holder to exchange tokens with the issuer under applicable terms. It does not recover tokens already transferred to another party.

The GENIUS Act is scheduled to take effect on the earlier of January 18, 2027 or 120 days after the relevant federal regulators issue final implementing rules.

European Union: requiring transparency on irreversibility

MiCA approaches crypto-asset transfers primarily through service-provider obligations.

Article 82 requires providers offering transfer services to establish agreements with clients covering the service, applicable security arrangements, fees and governing law.

ESMA's February 2025 guidelines further develop those requirements, including how providers communicate execution times and when transfers are expected to become irreversible.

Providers must make their estimates based on the relevant blockchain. ESMA does not prescribe a single confirmation threshold for all networks.

The guidelines also address liability for provider-attributable failures.

However, they do not establish a general recovery mechanism for payments correctly executed to an unintended recipient. They also do not directly apply to a company transferring assets from its own wallet without using a crypto-asset transfer service provider.

MiCA also establishes redemption rights for different token categories.

Under Article 49, holders of e-money tokens have redemption rights at par. Article 39 sets out redemption provisions for asset-referenced tokens based on their referenced assets.

Those rights concern the token holder's claim against the issuer. They do not reverse an underlying payment.

Companies operating across multiple networks need settlement policies that account for each blockchain's finality rules.

Why traditional payment protections don't transfer directly onchain

Europe already has a legal framework for settlement finality in traditional financial infrastructure.

Directive 98/26/EC, the Settlement Finality Directive, protects transfer orders in designated settlement systems, including in certain insolvency situations.

Under the Directive, each designated system defines when a transfer becomes final and when an instruction can no longer be revoked.

These protections apply within the systems covered by the Directive. They do not automatically extend to a company's direct stablecoin transfer to a supplier.

Other payment regulations introduce controls before funds move.

Since October 9, 2025, euro-area payment service providers must provide Verification of Payee checks under Regulation (EU) 2024/886.

The provider checks whether the recipient's name matches the account identifier before the payer authorizes the transfer.

A mismatch generates a warning, although the payer can still proceed. Non-consumer customers can also opt out of the service for batches of payment orders.

If a provider fails to perform the required verification and that failure causes a defective transaction, the regulation provides for reimbursement.

Brazil's Pix system takes another approach through its fraud recovery procedures.

Under the applicable rules, an infraction notification can trigger the blocking of funds remaining in the recipient's account, with an 80-day window linked to the original transaction.

Recovery still depends on whether funds remain available. The receiving institution is not generally required to reimburse the payer using its own money when the balance has already been withdrawn.

These mechanisms differ, but they share one important feature: they operate through financial institutions with defined responsibilities and procedures.

A direct stablecoin transfer has no equivalent process built into the blockchain itself.

For businesses, this makes recipient verification, transaction screening and internal approvals especially important before execution.

What finance teams need to record

Once a stablecoin payment is final, a company's ability to explain and audit it depends on the information captured by its own systems and service providers.

The blockchain records the transaction, including the addresses, amount and timestamp. But that record alone cannot explain why the payment was authorized, who approved it or whether it complied with the company's internal policies.

Those details need to come from the company's operational records.

Regulatory requirements vary by jurisdiction and institution type.

• Brazil: Regulated entities must submit supervisory reports, including client-level reporting under applicable Central Bank requirements.
• European Union: MiCA Article 68(9) requires crypto-asset service providers to maintain records of their services, activities, orders and transactions for five years, with the possibility of extension to seven.
• United States: The GENIUS Act requires payment stablecoin issuers to publish monthly reserve disclosures with executive certifications, including potential criminal liability for knowingly false certifications.

These obligations apply to different entities and concern different information. A payment services company is not automatically subject to every requirement imposed on a stablecoin issuer.

However, organizations operating across multiple jurisdictions may need to produce several forms of reporting from overlapping financial and transaction data.

For finance and compliance teams, the practical challenge is maintaining a consistent record that connects the payment to its business context.

That includes the counterparty, the account or wallet involved, approval history, relevant screening results, transaction status and supporting financial records.

The same information is needed for reconciliation, internal reviews and regulatory examinations.

And while blockchain settlement can happen quickly, the surrounding financial processes often take much longer. We explored that difference in why stablecoin instant settlement rarely lands instantly.

How Range helps manage stablecoin payments

Range starts from the regulatory and reporting requirement rather than the product: what a supervisor expects, what an examiner needs to see and on what clock. It turns those requirements into controls and gives finance and compliance teams a unified view of payments and treasury activity across stablecoins and fiat.

It connects wallets, custodians, exchanges and bank accounts, bringing transaction activity and counterparty information into a single operational record.

For onchain payments, Range supports pre-execution screening and policy-based controls, letting teams evaluate a transaction before broadcasting it.

These controls can identify sanctions exposure, counterparty risk and transactions that fall outside a company's approved policies.

Range also integrates with existing risk and compliance providers through customers' own API keys. Companies can continue using their preferred vendors while combining their signals with treasury and counterparty data.

That helps finance and compliance teams work from consistent information, including when a counterparty appears across several accounts, wallets or payment channels.

From the same transaction record, Range supports monitoring, reconciliation and reporting. Enriched onchain data can be fed into accounting systems such as Xero, QuickBooks, NetSuite and SAP, reducing the manual work required to reconcile stablecoin activity with the rest of the company's finances.

Regulatory responsibility remains with the company and its regulated service providers. Range provides the controls, transaction visibility and supporting evidence needed to operate within those responsibilities.

As stablecoin payments become part of day-to-day financial operations, companies need clear policies on when transactions are final, what to check before execution, and how to record each payment.

Get in touch to see how Range helps finance teams manage stablecoin payments, compliance and reconciliation across their existing infrastructure.