# How to confirm a payment is final before shipping or releasing goods A practical guide for settlement professionals on what blockchain finality really means, how it varies by network, and how onchain payment routing eliminates ambiguity before goods change hands. --- There is a moment in every commercial transaction where someone has to make a decision without complete certainty: has the money actually arrived, or does it just look like it has? In traditional banking, that question can take days to resolve definitively. In crypto, it can take anywhere from a few seconds to an hour — depending on which network carries the payment, and whether the person receiving it understands the difference between *confirmed* and *final*. This distinction is not academic. For merchants and payment processors, finality affects everything from how long to wait before releasing goods to how many confirmations to require for high-value transactions. For settlement agents, closing attorneys, escrow officers, title companies, and OTC desks, getting this wrong is a professional liability, not just an operational nuisance. The purpose of this article is to give those professionals a working framework: what finality means onchain, how it differs across networks, what the common failure modes look like in real commercial scenarios, and how tools like shaka.deal can give every party at a closing table — or a deal table — a single, unambiguous signal that the payment has settled and disbursed simultaneously.
13–19 minpractical finality window on Ethereum, at epoch finalisation
~60 minsix confirmations on Bitcoin, the threshold for large transactions
4–8 hourstypical time to hard finality on Starknet, a zero-knowledge rollup

Finality times as given in the network sections of this article.

## Why "confirmed" and "final" are not the same thing Before discussing what to look for, it helps to be precise about the words. Confirmation usually means a transaction has been included and recognised by the network. Finality means the result has reached a stronger settlement guarantee and is no longer expected to change. That gap between inclusion and finality is where risk lives. A transaction can be confirmed without being final. It may appear inside a valid block, show one or more confirmations, and still remain vulnerable to chain reorganisation, validator failure, bridge delay, or rollup settlement rules. In practice, this means that seeing a transaction in a wallet explorer — or even receiving a notification that it has been included in a block — does not necessarily mean the funds are yours to act on. Wallets can show a transaction as confirmed quickly, but settlement quality depends on the consensus design underneath the chain. The professional parallel is instructive. A card swipe feels instant, but the merchant does not have irrevocable funds for days. Disputes can arrive months later. Onchain transactions do not work that way. Once a transaction reaches true finality on a well-designed network, it is immutable — the payment is settled, the distribution is complete, and no party can reverse it. That is a materially stronger guarantee than anything traditional payment rails offer. But reaching that guarantee requires understanding the specific mechanics of the network being used. ## How finality works on the networks that matter for B2B settlement ### Ethereum Ethereum is the network on which shaka.deal operates, and it uses a proof-of-stake consensus model with a well-defined finality mechanism. Validators stake ETH, and a transaction is considered finalised once two consecutive epochs (about 12.8 minutes) attest to it. Once that threshold is reached, reversal becomes economically catastrophic for any attacker. A finalised block cannot be reverted without at least one-third of all staked ETH being slashed. With over 34 million ETH staked, an attacker would need to control and sacrifice roughly 11 million or more ETH — tens of billions of dollars — to revert a finalised transaction. Finality requires two consecutive epochs to be justified and finalised, producing a practical finality window of approximately 13 to 19 minutes depending on attestation timing. That is the number settlement professionals on Ethereum should build their release checklists around: wait for epoch finalisation, not just block inclusion. ### Bitcoin Bitcoin is the most widely held reference point, but it uses probabilistic rather than deterministic finality. A transaction is never strictly final; it becomes exponentially harder to reverse with each block built on top. After six confirmations — roughly 60 minutes on Bitcoin — the probability of a reorg drops below the threshold most exchanges and custodians treat as settled. How many confirmations to require on Bitcoin depends on the amount at stake: | Confirmations | Approximate wait | Reasonable security for | | --- | --- | --- | | One | 10 minutes | Small transactions | | Three | 30 minutes | Moderate amounts | | Six | 60 minutes | Large transactions or exchange deposits | At six confirmations, reversal becomes economically impractical. For a settlement professional handling a seven-figure transaction in Bitcoin, the operational implication is clear: nothing moves until six blocks have been built on top of the transaction. Anything less is a policy decision about risk tolerance, not a statement about finality. ### Layer 2 and rollup networks Layer 2 blockchains built on Ethereum publish transaction data in batches to Ethereum Layer 1. The finality characteristics of L2 chains depend on when batches are posted and when those batches achieve finality on Ethereum L1. This is a meaningful operational wrinkle. A transaction that shows as "confirmed" on an OP Stack chain such as Base or OP Mainnet may have fast soft finality — meaning it is very unlikely to be reversed — but hard finality, anchored to Ethereum L1, can take considerably longer. OP Stack-based chains post state updates approximately every 15 minutes. Some providers wait for the Ethereum L1 block containing the batch to finalise, which typically takes around 65 blocks (13 to 19 minutes) after the batch is posted. For rollups that use zero-knowledge proofs, the timeline is longer again. The typical time to reach hard finality on Starknet is 4 to 8 hours, as finality depends on when the zero-knowledge rollup proof is posted to Ethereum and when its corresponding L1 block finalises. Settlement professionals routing large transactions through Layer 2 networks should understand exactly which finality model their counterparty or platform applies. ## Real commercial scenarios where finality gaps cause problems ### The wholesale goods shipment A supplier in one jurisdiction ships a container of manufactured goods to a buyer in another. Payment is agreed in USDC on Ethereum. The buyer's team sends the transaction and shares a block explorer link showing one confirmation. The supplier's logistics manager, under pressure to release the shipment, sees "confirmed" and authorises the truck. Eighteen minutes later, the transaction has reached epoch finalisation and everything is fine — but the decision to release was made before that guarantee existed. In lower-stakes transactions, the probabilistic risk is negligible. But as transaction sizes grow — say, a consignment worth $500,000 USD (approximately $770,000 AUD) — the standard that a professional should apply is epoch finalisation on Ethereum, not block inclusion. The 13-to-19-minute wait is a small price for a settlement guarantee that no traditional wire transfer can match. ### The OTC desk trade with a multi-party payout An OTC desk facilitates a block trade where proceeds need to be distributed simultaneously to three parties: the selling institution, the broker, and a placement agent. Counterparty risk in OTC is the risk that the other party fails to deliver what was agreed. In a bilateral trade, there is a window between execution and final settlement during which one side has committed but the other has not yet delivered. This is where the structure of the settlement tool matters as much as the finality of the network. If the OTC desk has to make three sequential transfers — first to the selling institution, then to the broker, then to the placement agent — there is a window between each step where one party has received funds and others have not. Network congestion, a fee spike, or a human error can leave the distribution incomplete. Pre-settlement risk arises between trade execution and final settlement. During this window, one party can default before the exchange of assets is complete. The professional solution is not to wait longer — it is to restructure the payment so that all distributions happen in a single atomic transaction. When shaka.deal routes a payment, it splits and distributes the total amount to every party at preset shares in one transaction. There is no sequential risk, no partial settlement state, and no window between disbursements. The moment the payment reaches Ethereum finality, every party's share is already in their wallet. ### The real estate closing Title companies and closing attorneys operate in an environment where payment verification is already a high-stakes discipline. The FBI reports cybercrime losses exceeded $16.6 billion in 2024 alone — a 32% jump from the previous year. The FBI's Internet Crime Complaint Center reported more than $3 billion in Business Email Compromise losses in 2025, and real estate-related complaints accounted for more than $275 million in reported losses. Much of that risk in the traditional wire world comes from the gap between instruction and irrevocability. Most cases of real estate wire fraud stem from Business Email Compromise scams. In these attacks, cybercriminals hack or spoof legitimate email addresses belonging to real estate agents, title companies, or attorneys. Once inside the communication thread, they quietly monitor the transaction, waiting for the right moment to intervene. When the time is right — typically right before closing — the scammer sends a convincing message with "updated" wire transfer instructions. An onchain payment routed through a pre-configured smart contract changes the threat model fundamentally. The destination addresses and distribution shares are encoded in the contract before the transaction occurs. There is no wire instruction to intercept, no "updated banking details" email to fabricate, and no moment at which a social engineering attack could redirect the funds mid-flight. After finality, the payment cannot be reorganised out of history, double-spent, or unwound by a chain reorg. The closing attorney's job shifts from verifying that funds arrived at the right place to simply confirming that epoch finalisation has occurred — a fact that any block explorer can verify in seconds. ### The import/export transaction with multiple counterparties Consider a cross-border import deal with four parties: a buyer, a freight agent, a customs broker, and the original supplier. Payment terms require that upon delivery confirmation, the freight agent, the customs broker and the supplier receive their agreed shares simultaneously. In the traditional model, the settlement agent initiates three sequential wire transfers. Banking hours, correspondent bank delays, and currency conversion windows mean the supplier in one time zone may not see their funds for a business day after the buyer's bank initiates the first wire. With a pre-configured onchain payment routed through shaka.deal, the settlement agent initiates one transaction. All three recipients receive their preset shares in the same block, at the same moment, on the same chain. The settlement agent's role is elevated: they now manage the deal structure and the routing parameters, rather than manually executing multiple sequential transfers and chasing confirmations across time zones. ## Building a finality confirmation checklist for professional use The right checklist depends on the network, the transaction size, and the professional context. The following framework is designed for settlement agents, closing attorneys, escrow officers, and OTC desk operations teams.
Finality confirmation checklistBefore releasing goods or transferring title
  1. Identify the network and its finality modelEthereum uses epoch-based finality (approximately 13 to 19 minutes). Bitcoin uses probabilistic finality with a practical threshold at six confirmations (approximately 60 minutes). Layer 2 networks have variable finality depending on batch posting and L1 anchoring schedules. Confirm which network the payment is arriving on before the transaction is initiated, not after.
  2. Distinguish between inclusion, confirmation, and finalisationDo not release goods or transfer title on block inclusion alone. Inclusion is not the finish line. On proof-of-work chains, a string of unlucky block production can cause a short reorg that knocks a transaction back into the mempool. On Ethereum, wait for epoch finalisation — the point at which reversal would require a catastrophic and economically irrational validator attack.
  3. Verify on-chain, not by screenshotRequire that all parties confirm finality against a public block explorer, not via a screenshot shared in a messaging thread. For crypto users, finality awareness prevents common mistakes and risks. Never consider transactions final based solely on seeing them in your wallet — understand your blockchain's finality requirements. A screenshot can be falsified. A block explorer entry at a confirmed epoch checkpoint cannot.
  4. Confirm the distribution, not just the inboundIn any multi-party settlement, confirmation of the inbound payment is only half the picture. The settlement professional must also confirm that the distribution to all parties has occurred. This is where onchain routing through a tool like shaka.deal provides a structural advantage: because all disbursements happen in a single transaction, there is one transaction hash to verify, one block to confirm, and one finality event that covers every party simultaneously. The settlement log is transparent, immutable, and auditable by all parties without any of them needing to trust the others' representations.
  5. Set written policy thresholds by deal sizeThe finality requirements for payments depend heavily on the context. A useful framework considers transaction value, reversal risk, and the speed expectations of the payment environment. A professional firm should document its own thresholds: for transactions below a certain notional value, soft finality (a small number of block confirmations) may be acceptable per internal risk policy. For transactions above that threshold — real estate closings, large OTC trades, commercial goods shipments — full epoch finalisation should be non-negotiable.
## Why the settlement professional's role becomes more valuable onchain A persistent misconception about blockchain payments is that they reduce the need for professional oversight. The opposite is true. The technical complexity of finality models, the importance of pre-configured routing parameters, the need to verify distribution across multiple parties, and the legal documentation that accompanies any significant commercial transaction all require expert coordination. Managing OTC settlement well means more than finding a good price. Your team needs a clear view of counterparty risk, a defined custody approach, and internal controls that match the approval requirements your organisation already applies to large financial transactions. Every OTC trade should produce a trade confirmation document that your finance team can reconcile against your internal records. This should include the executed price, the notional amounts on both sides, settlement timestamps, and any on-chain transaction references. The same principle applies to real estate closings, commercial goods transactions, and any B2B deal where multiple parties need to receive simultaneous payment. The settlement agent or closing attorney who understands finality mechanics — and who can explain to their clients exactly when a payment is irrevocable and why — is providing a materially superior service to one who simply forwards a wire confirmation email and hopes for the best. shaka.deal is built for exactly these professionals. It does not replace the settlement agent; it gives the settlement agent a tool that matches the certainty their clients expect. When a deal is configured on shaka.deal, the routing logic — who receives what share — is established before any payment is sent. When the buyer sends the total amount, shaka.deal routes it instantly and simultaneously to every party at their preset share, in a single Ethereum transaction. The settlement agent oversees the configuration. The parties receive their funds. The block explorer provides the immutable audit trail. ## The stablecoin dimension: what asset to use, and why it matters for finality The choice of asset is inseparable from the finality question. Stablecoins, primarily USDT and USDC, are dollar-pegged digital currencies that settle payments in seconds. Total stablecoin on-chain transfer volume hit $33 trillion in 2025, a 72% year-over-year jump. Real-world stablecoin payments volume doubled in 2025 to $400 billion, with an estimated 60% attributed to B2B payments. For settlement professionals, stablecoins denominated in USD remove the volatility problem entirely. A deal agreed at $1,000,000 USD (approximately $1,540,000 AUD) settles at $1,000,000 USD, regardless of what happens to ETH or BTC prices in the 15-minute window between payment initiation and epoch finalisation. The stablecoin is the unit of account, the medium of exchange, and the settlement asset — all in one. B2B stablecoin payments are commercial transactions between businesses settled in dollar-pegged tokens, typically USDC or USDT, on public blockchains rather than through bank wires, ACH, or SWIFT. The economic case is straightforward: settlement compresses from days to seconds, fees fall to single-digit cents on most chains, and the dollar balance becomes programmable, meaning a payment can carry conditions and chain into longer treasury workflows. When stablecoins are routed through shaka.deal, each party receives their exact contracted share in the same asset at the same moment. There is no FX conversion step, no correspondent bank delay, and no ambiguity about which party's share settled first. The payment is split, instant, and certain — the three properties that define a truly settled deal. ## A practical timeline: what "waiting for finality" actually looks like To make this concrete, consider the timeline for a $750,000 USD (approximately $1,155,000 AUD) commercial real estate disbursement routed through shaka.deal on Ethereum, with four parties: seller, seller's broker, buyer's attorney's firm, and a lender payoff. - **T+0**: Buyer initiates a single USDC transaction to the shaka.deal routing address. Transaction enters the mempool. - **T+12 seconds**: Transaction is included in a block. All four parties can see the pending disbursement in their wallets. Nothing is final yet. - **T+6.4 minutes**: First epoch checkpoint. The transaction is not yet finalised. - **T+12.8 to 19 minutes**: Second epoch is justified and finalised. Under normal conditions, finalisation takes approximately 12.8 minutes (two full epochs). At this moment, all four disbursements are simultaneously irrevocable. The settlement agent records the transaction hash and the finalisation block number. Closing documents are countersigned. Keys are released. The entire process from payment initiation to confirmed, irrevocable distribution to four parties takes less time than a domestic wire transfer takes to show as received — and far less than the days required for that wire to reach true settlement finality. ## Closing: certainty is a professional standard, not a feature The question of when a payment is truly final is not a technical curiosity. It is the foundation of every commercial transaction involving goods, property, or financial assets. Settlement professionals have always understood this — their entire practice is built around managing the gap between agreement and irrevocable delivery. Onchain payments do not eliminate that gap. They compress it to minutes, make it mathematically verifiable, and — when payments are structured correctly — ensure that every party receives their share simultaneously in a single atomic event rather than through a sequence of manual transfers that each carry their own timing risk. shaka.deal is built on that principle. One incoming payment. Preset shares. Simultaneous distribution. Ethereum finality. The settlement agent manages the deal structure; the chain handles the certainty. For professionals whose reputation depends on transactions closing cleanly — and whose clients trust them to confirm that a payment is genuinely final before goods change hands or title transfers — that combination is not a convenience. It is the standard.