How to Prove a Record Wasn't Changed: Bitcoin Timestamps Explained Simply
A record kept by one party can be changed quietly by that party. A seal in Bitcoin does one plain job: it proves that a record existed in exactly this form at a certain time, so any later change shows. You do not need to understand Bitcoin to rely on it, just as you do not need to understand ink to trust a signature.
Six months later
Let's meet a seller we will call Sari. She is not a real person, but her worry is a common one.
Sari sells planning templates for small cafés: menus, stock sheets, staff rotas. Since October she has sold them through a payment link, paid in USDT and USDC. Each sale lands in her wallet, minus a 1 percent fee.
Six months later, she sits down with an accountant to prepare her taxes, and later with a small lender who wants to see her sales history. Both ask the same kind of question: "How do we know these numbers are the real ones?"
Sari has her wallet history, which is public on Solana. She also has the payment service's records, which match each sale to an order and show the fee taken. But a thought bothers her. Those records live on someone else's server. What if they were changed? What if, one day, the service said the fee had always been 2 percent? What if an old sale quietly disappeared, or a date moved?
Most of the time, nothing like that happens. But "most of the time" is not proof. Sari wants something stronger: a way to show that a record today is exactly what it was then.
That is the problem a seal in Bitcoin solves. This essay explains it in plain words, without mathematics and without hype.
Records that can be changed quietly
Every record we rely on is kept by someone: a bank, a shop, an employer, a payment company. Usually we trust that the keeper will not change it. Usually that trust is fine.
But history has many examples of records changed after the fact, especially dates. In 2006, a scandal broke in the United States over "backdated" stock options: grants of shares to executives that were dated, on paper, to days when the share price had been low, which made them more valuable. CNN reported that more than 50 companies were being investigated by the Securities and Exchange Commission and federal prosecutors, and the researcher whose work drew attention to the problem believed the true number could reach into the hundreds (CNN Money).
The details of that story do not matter here. What matters is the lesson: a date on a record is only as trustworthy as whoever keeps the record. If the same party writes the record and can rewrite it, outsiders have no way to know what it said before.
For payments, this matters to both sides. A seller wants to know that their sales history and the fees they were charged cannot be revised later. A buyer wants to know that the record of their payment, or their refund, will say the same thing next year as it says today.
Why backups and screenshots are not enough
A natural answer to "what if the records change?" is "keep a copy". Sellers can download reports, take screenshots or export spreadsheets. That is a good habit, but it does not solve the problem.
A copy you keep yourself proves nothing to anyone else. A spreadsheet can be edited as easily as the original, and a screenshot is a picture. If Sari showed her accountant a file she exported in October, the accountant would still have to trust that Sari had not changed it since. The question has just moved from the company to the seller.
Backups kept by the company have the same weakness from the other side. They are made, stored and restored by the same party that writes the records. If that party wanted to change the past, it could change the backups too.
What is missing in both cases is a witness that neither side controls: something outside the seller, outside the buyer and outside the payment company, that saw the record at a certain moment and cannot be persuaded to forget.
The old ways of proving "this existed then"
People have looked for ways to fix a record in time for a long time.
A notary stamps and dates a document. A post office stamps a date on an envelope. A newspaper prints the news of a particular day, and everyone can see which day it was printed.
That last idea leads to one of the most charming stories in computing. In 1991, two researchers, Stuart Haber and W. Scott Stornetta, published a method for timestamping digital documents. A company built on their work, Surety, has since 1995 printed a short code in a small ad in the classified section of The New York Times, once a week. The code is a fingerprint that summarizes all the documents its customers registered that week. Because thousands of printed copies of the newspaper exist in libraries and homes, nobody can later claim that a different code was printed that day (Vice).
The same article notes that when Satoshi Nakamoto described Bitcoin in 2008, three of the eight papers cited were by Haber and Stornetta (Vice). Sealing records into Bitcoin is a newer version of the same idea: publish a fingerprint somewhere so public and so widely copied that nobody can quietly change it.
What a fingerprint is, in plain words
The word "fingerprint" keeps coming up, so let's make it concrete.
A digital fingerprint is a short code that a computer calculates from a piece of data, such as a line in a record book. The method PayFi uses is called SHA-256, a standard published by the US National Institute of Standards and Technology. In NIST's own words, such fingerprints "are used to detect whether messages have been changed since the digests were generated" (NIST).
You only need to know three things about it.
The same data always gives the same fingerprint. Anyone, on any computer, who calculates the fingerprint of the same line gets exactly the same code.
A tiny change gives a completely different fingerprint. Change one digit, one letter or one space, and the code changes beyond recognition. It does not change "a little"; it changes completely.
You cannot go backwards. From the fingerprint alone, nobody can work out the data it came from. A fingerprint reveals nothing about what it describes.
A kitchen comparison helps. Mixing paints is easy: blue and yellow make green in a second. Getting the exact blue and yellow back out of the green is impossible. A fingerprint works in a similar one-way fashion, except that it is precise: the same ingredients always give exactly the same shade, and the slightest change in any ingredient gives a completely different colour.
So a fingerprint is like a seal on an envelope that does not show the letter inside. If someone has the letter, they can check that it matches the seal. If someone changes the letter, it will no longer match.
A chain of fingerprints
Now imagine a record book where every new line includes the fingerprint of the line before it.
The first line, called the genesis, starts from a blank: in PayFi's book, its "previous fingerprint" is simply a row of zeros. The second line includes the fingerprint of the first. The third includes the fingerprint of the second, which itself depended on the first. And so on, line after line.
This is what the theater at the top of this essay shows: links that lock into each other, from the genesis to the latest line.
The effect is powerful. Suppose someone changed line 3, even by one cent. Its fingerprint would change. But line 4 contains the old fingerprint of line 3, so line 4 no longer matches. And because line 4's own fingerprint depends on what it contains, line 5 no longer matches either. One change in an old line breaks every link after it, all the way to the end.
There is a useful consequence. Because the last fingerprint depends on every line before it, that single short code stands for the whole book. If you know the last fingerprint is genuine, you know every line before it is genuine too.
That leaves one question. How do you make sure the last fingerprint itself is genuine, and was not swapped for a new one along with a rewritten book? That is where Bitcoin comes in.
A small example
Let's make this concrete with a tiny book of three lines. The fingerprints here are shortened to four characters to keep them readable; real ones are 64 characters long.
Line 1 is the genesis. Its "previous fingerprint" is a row of zeros. Its own fingerprint comes out as 3b09.
Line 2 records a sale: 10.00 USDT in, 9.90 to the seller, 0.10 fee. It also contains "previous: 3b09". Its fingerprint, calculated from all of that, is 7c1e.
Line 3 records another sale: 25.00 USDC in, 24.75 to the seller, 0.25 fee, and "previous: 7c1e". Its fingerprint is a41d. That last code, a41d, is what gets sealed into Bitcoin.
Now imagine someone later changes line 2 so that the seller received 9.00 instead of 9.90. The fingerprint of line 2 is recalculated, and it is no longer 7c1e; it is something completely different. But line 3 still says "previous: 7c1e". The link between them is broken.
To hide that, the person would have to rewrite line 3 as well, with the new previous fingerprint. That changes line 3's own fingerprint, so it is no longer a41d. And a41d is already sitting in a Bitcoin block, with a date, in copies all over the world. There is no way to make the edited book produce a41d again.
So the edit can be made, but it cannot be hidden. Anyone who runs the checker would see that the book no longer matches its seal, and exactly where the break begins.
Putting the last link into Bitcoin
Bitcoin is a public record that has been running since January 2009 (Bitcoin Wiki). New pages, called blocks, are added to it on average every 10 minutes (Bitcoin Wiki). Copies of the whole record are kept by many independent computers around the world, and each new block is built on top of the one before it, much like the chain of lines in PayFi's book. The deeper a block lies under newer blocks, the harder it becomes to change.
For our purposes, Bitcoin plays the role that The New York Times plays for Surety: a place so public and so widely copied that what is written there cannot be quietly replaced.
Writing directly into Bitcoin costs a transaction fee. PayFi does not do that itself. Instead, it uses OpenTimestamps, a free and open tool. Its servers, called calendars, collect fingerprints from many users, combine them into one, and put that single combined fingerprint into a Bitcoin transaction. According to OpenTimestamps, these calendar servers are free to use, need no registration, and the resulting proof can be checked against Bitcoin directly, without trusting the calendar (OpenTimestamps).
PayFi sends its latest fingerprint to four independent calendars at once. Before sending it, PayFi mixes the fingerprint with a random number, so the calendar learns nothing at all from it. What leaves PayFi's server is just a meaningless-looking code.
What comes back is a small proof file. At first, the proof is "pending": the calendar has promised to include it. A few hours later, once the calendar's transaction is in a Bitcoin block, the proof becomes complete. It now links PayFi's fingerprint, step by step, to a specific Bitcoin block that anyone can look up.
Why four calendars and not one? Because no single calendar should be a point of failure. If one is down, slow or one day disappears, the others still carry the fingerprint into Bitcoin. Each calendar is run by a different operator. None of them needs to be trusted, since the finished proof is checked against Bitcoin itself, but using several makes it very likely that at least one finishes the job on time.
A seal is not a copy
One more point is easy to confuse. A seal does not store the book. Bitcoin holds only a fingerprint, not the lines themselves.
That is deliberate. It keeps the payment details off Bitcoin entirely, and it keeps each seal tiny. But it also means the book itself must be kept somewhere: on PayFi's ledger page, in the downloadable file, and in any copies that sellers, buyers or curious strangers save. The seal's job is not to remember the book. Its job is to make sure that any copy of the book, wherever it is kept, can be tested for changes.
How often the book is sealed
PayFi's ledger page explains the timing plainly. When new lines appear, the latest fingerprint is sent for sealing at most once an hour. Even when nothing happens, it is sealed at least once a day. And it takes Bitcoin a few hours to include each stamp; until then, the seal shows a dash instead of a block number.
This means there is always a short gap at the end of the book: the newest lines, written in the last hour or so, are not yet protected by Bitcoin. PayFi lists this openly among the things it cannot promise: "The newest lines, until they are sealed into Bitcoin — within about an hour, at most a day."
Once a seal is complete, it covers every line up to that point, because the sealed fingerprint depends on all of them. One of the book's early seals, from October 5, 2026, sits in Bitcoin block 969,936. Each later seal covers everything before it, including all the lines the earlier seals covered.
What a seal proves, and what it does not
It is important to be exact here, because seals are often oversold.
A seal proves that a record existed in exactly this form no later than a certain time. If the book today produces the same fingerprint that was sealed into a Bitcoin block in October, then every line up to that point is exactly what it was in October. Not one cent, date or address has changed.
A seal does not prove that a record is true. A false line, sealed into Bitcoin, is still false; it is just permanently false. Whether each payment line matches a real payment is a different question. For PayFi's book, that question is answered by checking each line against its transaction on Solana, which the ledger's checker also does.
A seal does not stop anyone from adding lines. New payments are added every day. What a seal prevents is changing the lines that came before.
A seal does not depend on the price of Bitcoin. It does not matter whether Bitcoin goes up or down. What matters is only that its record keeps existing and keeps being copied, which it has done every day since 2009.
Put together, the two checks cover each other. Solana shows that the payments really happened. The chain of fingerprints and the Bitcoin seal show that the book describing them has not been edited since.
What this means for a seller
Let's go back to Sari and her accountant.
Every one of Sari's sales is a line in PayFi's public book: the price, the amount that reached her wallet, the fee and the Solana transaction. Each line is linked to the one before it, and the book has been sealed into Bitcoin again and again since October.
So when the accountant asks how they can know these are the original numbers, Sari has an answer that does not depend on anyone's word, including PayFi's. If any of those lines had been changed since they were sealed, the fingerprints would not match the ones already in Bitcoin, and the checker would say so in plain words.
The same applies to the fee. If the fee ever changed, the change would be written into the book as a new line, with its date. It could not reach back and alter the fee recorded on past sales. A seller can always show what they were actually charged, sale by sale.
For a lender, a tax office or a future business partner, that kind of record is unusually solid. It is not a spreadsheet the seller could have edited. It is not a statement from a company that could have changed its own history. It is a public record, fixed in time, that anyone can test.
It also changes the conversation with the lender. Small sellers who are paid informally, by transfers, cash or platform payouts, often struggle to prove their income to anyone, because their records are scattered and easy to doubt. A sales history that is public, matched to blockchain payments and fixed in time with Bitcoin seals is not a guarantee of a loan. But it is evidence that someone else can actually test, rather than a story they have to believe.
What this means for a buyer
Buyers benefit in a quieter way.
A buyer's payment is a line in the same book, found with their private order link. If they paid too much and were refunded, the refund is a line too, with its own transaction. Once sealed, neither line can be changed.
That matters most when something is disputed. Suppose a buyer remembers being refunded and the seller does not. Or suppose a buyer needs to show, months later, that a payment was made on a certain date. The sealed book gives them a record that does not depend on the seller's memory, the payment service's goodwill or a screenshot.
And because the book contains no names, emails or product details, being part of a permanent public record does not mean being exposed. What is fixed forever is the money, not the person.
How to check a seal yourself
You do not need to take any of this on faith. There are three levels of checking, depending on how far you want to go.
Look at the ledger page. On payfi.cx/ledger, each line that is already covered by a seal shows a small "BTC ✓" mark. A separate tab lists every seal, each with a link to its block on mempool.space, a public Bitcoin explorer that PayFi does not run. When you open the page, it also runs its checker in your browser and tells you whether everything adds up.
Run the checker yourself. The ledger page offers two downloads: the whole book with every Bitcoin proof in one file, and a small checking program. The program talks to Solana and Bitcoin directly, not to PayFi, and reports in plain words whether every link in the chain holds and whether every seal matches Bitcoin.
Use OpenTimestamps' own tools. Because the proofs are standard OpenTimestamps files, anyone can verify them with OpenTimestamps' own software, which has nothing to do with PayFi. This is the strongest form of checking: two independent tools, written by different people, reaching the same answer.
Most sellers and buyers will only ever do the first. That is fine. The point is not that everyone checks everything. The point is that anyone can, so the book cannot rely on nobody looking.
A simple habit for your own records
Even with a sealed public book, a few small habits make your records easier to use later.
Download a copy of the book now and then. At the end of each month or quarter, save the ledger file from the ledger page alongside your other financial records. It contains every line and every Bitcoin proof up to that moment. If you ever need to show your history, you have a copy that can be checked against Bitcoin on its own, whether or not the website is available.
Note the seal next to important payments. For a large sale or a payment that might be questioned, write down the Bitcoin block number shown in the seals tab for the seal that covers it. It is a short number, easy to keep, and it points to a public record anyone can open.
Keep your own transaction codes. For sellers, your wallet history already holds them. For buyers, the private order link leads back to everything.
None of this is required. The book and its seals exist whether you keep copies or not. But a copy in your own hands means you never have to depend on anyone, including the payment service, to show what happened.
Why seal payments on Solana into Bitcoin?
A reasonable question: the payments themselves happen on Solana, which is also a public blockchain. Why bring Bitcoin into it at all?
Because the book and the payments are two different things. Solana records each payment. But PayFi's book, which explains those payments (which order, which fee, which refund), lives on PayFi's own server. Something outside PayFi's control has to fix that book in time.
Bitcoin is a natural choice for that job. It is the oldest of these public records, running since 2009, and the most widely copied. Using it also means that the proof does not rest on a single network. The payments can be checked on Solana, and the book can be checked on Bitcoin. Each is independent of the other, and both are independent of PayFi.
Why a payment service would bind its own hands
It might seem odd for a company to make it impossible to correct its own records. Most companies keep that freedom, for good reasons and sometimes for bad ones.
For PayFi, giving it up follows from how it works. It asks sellers and buyers for no account, no name and no ID. It does not hold anyone's money. It is run by a small team of developers most users will never meet. A service like that cannot fairly ask people to trust its promises about the past. "We will never change our records" is still only a promise.
A seal turns that promise into something closer to a fact. After a line is sealed, PayFi is not choosing to leave it alone; it simply cannot change it without everyone being able to see. That protects sellers and buyers. It also protects PayFi, in a way: if someone ever claimed the records were altered, the seals would settle the question.
If something does go wrong, the book does not pretend otherwise. Mistakes are corrected by adding new lines that explain them, in public, not by rewriting old ones. That is how honest paper ledgers worked for centuries: you never erase, you write a correction underneath.
Common questions
Is my payment information stored on Bitcoin? No. Only a single fingerprint, mixed with a random number, goes to the timestamp calendars. It reveals nothing about any payment, and there are no names, amounts or addresses in it.
Does sealing cost sellers or buyers anything? No. OpenTimestamps calendars are free to use, and the seal is part of how PayFi keeps its book.
What if PayFi deleted the whole book? It could stop publishing it, but it could not make a different version match the seals already in Bitcoin. Anyone who had downloaded the book could still check it against those seals, and the payments themselves would still be on Solana.
What if Bitcoin stopped? The record up to that point would remain in the many copies kept around the world, and existing proofs would still point to blocks in those copies.
Do I need to understand any of this to use a payment link? No. Most people will only ever look for the "BTC ✓" next to their line, if that. The technical parts exist so that people who want to check deeply can, and so that nobody, including PayFi, can rely on no one checking.
Back to Sari
Six months after her first sale, Sari opens the ledger page with her accountant. She types her wallet address. Her sales appear, line by line, each with its price, its 1 percent fee and its Solana transaction. Next to each one is a small mark: BTC ✓.
The accountant clicks one of the seals. It opens a Bitcoin block from October, on a website neither of them had heard of an hour ago and that PayFi does not run. "So nobody can have changed this since then," the accountant says. "Not you, not them."
That is the shift. The old belief says a record is trustworthy because of who keeps it: a bank, a company, an official. The newer one says a record is trustworthy when anyone can test it, and when its keeper has made it impossible to change quietly.
Sari did not need to learn how Bitcoin works. She needed to know one thing: the links lock into each other, the last link is locked into Bitcoin, and anyone can check that they still fit.
Sources
- CNN Money, "More than 100 firms probably backdated options" (July 12, 2006): money.cnn.com
- Vice, "What Was the First Blockchain?": vice.com
- NIST, FIPS 180-4 Secure Hash Standard: csrc.nist.gov
- Bitcoin Wiki, "Genesis block": en.bitcoin.it
- Bitcoin Wiki, "Block intervals": en.bitcoin.it
- OpenTimestamps: opentimestamps.org
- PayFi Ledger: payfi.cx/ledger