Bitcoin against traditional payment rails

Bitcoin produces a block roughly every ten minutes, and the difficulty adjustment retargets every 2,016 blocks to hold that interval steady as mining power changes. A transaction included in a block is not immediately final: each subsequent block makes a reversal more expensive, and the convention for high-value transfers is to wait for six confirmations, which is about an hour. Below that threshold the transaction is best understood as increasingly improbable to reverse rather than settled. The Lightning Network exists to move small payments off this clock, at the cost of holding funds in a channel.

A card payment inverts the sequence. Authorisation is near-instant, but the settlement between banks typically occurs one to two business days after the transaction is captured, and the merchant's funds remain subject to clawback for the whole dispute window. So the merchant on a card rail has fast authorisation and slow finality, while the recipient of a bitcoin payment has slow authorisation and fast finality. Which one is better depends entirely on whether the merchant values the certainty of the funds or the speed of the handshake.

Against irrevocable bank transfers the comparison is cleaner. A Fedwire transfer settles the same day and cannot be recalled once processed; a SEPA Instant credit transfer settles in seconds and is likewise irrevocable. Bitcoin's hour to high confidence is slower than both, and its cost does not depend on the amount transferred or on the banking hours of either party. That is the honest framing: Bitcoin is not faster than the fastest bank rails, and it is available when they are closed.

The chargeback is the defining feature of the card rail and the clearest illustration of the trade-off. Under the card networks' dispute rules, a cardholder can raise a chargeback for a substantial period after the transaction — the standard window is measured in months, and certain reason codes extend it further. The merchant receives the funds provisionally and bears the risk that they are reclaimed. That risk is not a defect; it is the mechanism that makes consumers willing to hand card details to strangers, and it is priced into the merchant discount fee.

Bitcoin has no equivalent. Once a transaction is confirmed, there is no issuer to petition, no reason code to cite, and no counterparty obliged to reverse it. A payment sent to the wrong address is gone unless the recipient chooses to return it. This is usually described as a disadvantage for consumers, and for a mistaken payment it is. For a merchant it is the reverse: the funds are final, and the chargeback fraud that costs card-accepting merchants money does not exist on this rail. The risk has not been removed; it has been moved from the merchant to the sender.

That relocation has a second-order effect worth stating. Because there is no reversal, the burden of verifying the payment falls on the sender before the transaction is broadcast, and the burden of deciding when to release goods falls on the merchant, who must choose a confirmation threshold. A merchant accepting zero-confirmation payments is extending credit in exactly the way a card network does, without the dispute machinery that makes card credit safe. The threshold is a risk decision, not a technical setting.

A card payment carries an interchange fee paid by the merchant's bank to the cardholder's bank, a network assessment, and the acquirer's margin, all bundled into the merchant discount rate. The cardholder sees none of it, which is why the cost of the card rail is invisible to the person choosing to use it. Bitcoin's cost is the opposite: the fee is paid by the sender, it is visible before the transaction is broadcast, and it is set by competition for block space rather than by a schedule. When blocks are full, the fee rises; when they are not, it falls.

The practical consequence is that Bitcoin's fee is volatile in a way a card fee is not, and it is denominated per transaction rather than as a percentage of value. A fixed fee is cheap relative to a large transfer and expensive relative to a small one, which is precisely why the base layer is a poor fit for retail payments and why the layer above it exists. A card fee, being proportional, behaves in the opposite way.

There is a further cost on the Bitcoin side that comparisons usually omit: the cost of custody. Holding bitcoin safely requires key management, and for an institution that means a qualified custodian and the fees that come with one. A bank account carries no equivalent line item because the bank absorbs it. A fair comparison of the two rails has to include the cost of holding the asset on each side, not only the cost of moving it.