What on-chain settlement means
Settlement is the point at which a payment is complete and irrevocable — the value has actually moved and the recipient can rely on it. On-chain settlement is settlement that happens on the blockchain itself: the transaction is broadcast, included in a block by the network's consensus, and recorded on the shared ledger. There is no clearing house, acquirer, or issuing bank in the middle; the network of validators is what records and orders the payment, and the blockchain is the authoritative record of who holds what.
Inclusion in a block is the start of settlement, not the end of it. Most chains can briefly produce competing versions of their most recent history and then discard one branch, which is a chain reorganization. A transaction that was only in the discarded branch drops back to unconfirmed. On-chain settlement is therefore not final the instant a transaction appears — it becomes final once the transaction reaches the network's settlement guarantee, which on many chains means accumulating enough confirmations that reversing it is infeasible. Different chains reach that point at different speeds, so the same block depth does not represent the same strength of settlement everywhere.
On-chain settlement is distinct from off-chain settlement, where a provider credits balances on its own internal ledger and only periodically — or never — moves the underlying funds on the blockchain. With on-chain settlement, the payment that the merchant relies on is the one recorded by the network, not an entry in a private database.
Why it matters in a crypto payment
For a merchant, on-chain settlement is what turns a detected payment into money in hand. A deposit can show up in a wallet or block explorer within seconds, but acting on it before it has settled on-chain — fulfilling the order, releasing goods, recognising the sale — carries the risk that a reorganization pulls the transaction back out. Waiting for the chain to settle the payment is what removes that risk. After that point, the payment is final.
Finality is what gives on-chain payments their defining property for merchants: no chargebacks. There is no issuing bank to claw the funds back and no dispute channel that can move coins out of the recipient's address weeks later, so a settled on-chain payment cannot be involuntarily reversed. The trade-off is symmetrical — because the network will not reverse a payment, returning money to a customer is always a deliberate, merchant-initiated transfer rather than something a bank can force. That return is a refund, a separate outbound payment, not a reversal of the original settlement.
On-chain settlement on halfin
halfin settles crypto payments on-chain, so an invoice is only treated as paid once the deposit has actually settled on the network it arrived on. A detected payment does not jump straight to paid: the invoice first reflects that a payment is confirming, and is marked paid once the transaction has reached the per-chain confirmation threshold that stands in for finality on that network. Crediting is reorg-aware, so a deposit undone by a reorganization before it is final does not leave a paid invoice behind — the credit only sticks once the transaction is deep enough to rely on.
Because thresholds are tuned per chain, the same invoice settles at a different pace depending on which network the customer paid on — a fast-finality chain can settle sooner than one that needs more blocks to be safe. Webhooks follow the same path, emitting a confirming event and then a paid event, so an integration can wait for on-chain settlement rather than reacting to a raw block count. Once settled, the payment is final: there is no card-style chargeback to defend against, and any money returned to the customer is an explicit refund the merchant initiates.