What it means
When you hand over a $20 note, you no longer have it, and that physical fact prevents you from spending it twice. A digital token is just data, and data can be duplicated at almost no cost.
Without a safeguard, a dishonest user could send the same token to two different merchants and each would believe they had been paid. Traditional payment systems solve the problem by keeping a central record.
When you pay by card, the bank checks your balance, deducts the amount and updates its ledger (the master record of who owns what). Because only one trusted party keeps that record, the same dollars cannot be spent twice.
Cryptocurrencies remove the central party and use a shared public ledger instead. Thousands of computers hold copies of the ledger, and new payments are grouped into blocks that the network agrees on through a consensus mechanism, which is a set of rules for deciding which version of history is the true one.
Once a payment is buried under several later blocks, reversing it becomes extremely expensive. The risk is not zero, which matters to any business accepting digital payments.
A merchant who hands over goods the moment a payment appears, before it has been confirmed in a block, can be tricked by a rival transaction that sends the same funds elsewhere. Smaller networks with less computing power are also more exposed to a so-called 51% attack, where one party controls enough capacity to rewrite recent history.
For finance teams, the practical lesson is to match the confirmation requirement to the value at stake. A $5 coffee may be safe to release instantly, while a $50,000 equipment sale should wait for several confirmations or settle through a regulated payment provider.
The same logic applies in traditional finance, where cheques can bounce and card payments can be reversed through chargebacks.
In practice
Real-world examples.
Example
An online electronics retailer accepts a digital currency payment of $2,400 for a laptop. The customer broadcasts the payment, then quickly sends the same coins to another wallet. Because the retailer waits for six confirmations before shipping, the conflicting transaction is rejected and the laptop stays in the warehouse.
Example
A freelance designer invoices a client $800 and accepts payment in a cryptocurrency. She uses a payment processor that monitors the network and only marks the invoice as paid once enough blocks have been added. The processor absorbs the technical risk, and she receives dollars in her bank account.
Example
A bank building a digital token to represent deposits must prove that a token cannot be spent twice. It keeps a single central ledger and records every transfer in real time, which avoids the need for mining or consensus. The design is simpler but relies on customers trusting the bank.
Case study
Seen in the real world.
Larkspur Coffee Roasters is an illustrative, fictional business that began accepting a small, little-known digital currency to attract tech-minded customers. To keep queues short, the owner released orders as soon as a payment showed up in the wallet, with no confirmation wait. Most orders were for $15 to $40, so the risk seemed trivial.
One weekend a customer placed a $6,000 wholesale order of beans and paid in the same currency. The customer then used a rival transaction to send those coins back to himself, and because the network was small, the conflicting version was accepted. Larkspur had shipped the beans and received nothing.
The fictional owner changed the policy. Small retail orders remained instant, but any order above $500 required a payment processor that waits for multiple confirmations and settles in dollars. The illustrative lesson is that the acceptable level of risk depends on the size of the sale.
Watch out
Common mistakes.
- Assuming digital payments cannot be reversed or duplicated under any circumstances, when unconfirmed transactions on a blockchain can be replaced.
- Treating a payment that has just appeared in a wallet as final, when it may not yet be included in a confirmed block.
- Believing double spending is only a cryptocurrency issue, when cheques, card chargebacks and fake payment confirmations create similar risks.
Questions
People also ask.
How does Bitcoin prevent double spending?
It uses a public ledger and a consensus process in which computers compete to add blocks, so conflicting payments are rejected and older history becomes very costly to rewrite.
What is a 51% attack?
It is an attack in which one party controls a majority of a network's computing power and can reorder recent transactions, which makes double spending possible on smaller networks.
How many confirmations should a business wait for?
There is no universal number, but larger payments usually justify more confirmations, and many businesses use a payment processor to manage the decision.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%