Confirmation levels explained for everyday SOL payments | Core Flow Point Guides
Solana confirms transactions quickly compared to many networks, but "confirmed" in conversation often mixes up technical levels. Wallets and APIs expose different thresholds — knowing which you wait for prevents both premature relief and unnecessary delay.
Processed
The transaction landed in a block produced by a leader. Most of the time it sticks, but rare reorganisations can drop it. Suitable for low-stakes tests where you will rebroadcast if nothing appears within a minute.
Confirmed
A supermajority of the cluster has voted on the block containing your transaction. This is the default many wallets show with a single checkmark. Appropriate for paying suppliers, reimbursing volunteers, and most retail-sized transfers.
Finalised
The block is rooted under consensus rules that make rollback exceedingly unlikely. Exchanges and high-value settlements often require this level before crediting deposits. Personal users rarely need to wait unless their counterparty insists.
Matching level to your habit
Treasurers we work with often adopt a simple rule: confirmed for recurring payroll under an internal threshold, finalised above that threshold or when the recipient's policy demands it. Document the rule so multiple signers behave consistently.
Our fee reference page links confirmation timing to fee choices — higher urgency sometimes pairs with priority fees, not with skipping confirmation levels.
Questions about this topic? Send an enquiry or browse our fee reference tables.