The client paying you
Can see
Their own invoice, the contract address, one single use key
Cannot see
Your account, your balance, everyone else who pays you
Private stablecoin invoicing on NEAR
Get paid privately.
Prove it when it counts.
Every invoice gets its own sealed envelope. Your client pays it without seeing your wallet, your balance, or the other people who pay you. When a landlord or a lender asks what you earn, you open only the payments you choose.
Live on NEAR testnet. No sign up, no account, and no Cachet server to send your details to.
The same invoice, kept two ways
You keep the document. The chain keeps a hash, an amount and a timestamp. Below is a payment that really settled, shown both ways.
Your copy
- Paid to
- Demo Earner
- Paid by
- cachetpayer.testnet
- For
- Brand identity, phase one
- Amount
- 250.00 USDC
- Issued
- Nov 13, 2026
- Settled
- Nov 13, 2026, 11:20 AM
The public record
- Paid to
- Demo Earner
- Paid by
- cachetpayer.testnet
- For
- Brand identity, phase one
- Amount
- 250.00 USDC
- Issued
- Nov 13, 2026
- Settled
- Nov 13, 2026, 11:20 AM
- Seal
- 3925220bca…ce35415d
The right-hand column is everything the contract holds. The seal is a salted hash, so it proves the invoice without carrying it.
One address tells them everything
Hand a client your wallet address and you hand them your books. Cachet splits apart the two things an address wrongly fuses: taking money, and giving up your history.
- 01
Seal
Fill in the invoice. Cachet derives a key for that one invoice in your browser and writes nothing to any server. The details ride inside the link, in the part of a web address that browsers never send anywhere.
- 02
Pay
Your client opens the link and pays in USDC. The money lands in the Cachet contract under that single key, not in your account. Nothing on the page points back to you.
- 03
Open
Sign with the envelope's own key and send the money wherever you like. The destination sits inside the signature, so even the person who submits the transaction cannot redirect it.
- 04
Prove
Pick the payments a landlord, a lender or an accountant should see. Cachet turns them into a link they can check against the chain, with no wallet and no account of their own.
A proof that answers to the chain
Not a screenshot and not a promise. The person you send it to runs three checks in their own browser, against NEAR, with nothing to install.
Three checks, every time
- 1
The invoice matches its seal
The details are hashed again with the salt you disclosed, and must equal the value stored on chain. One edited character breaks it.
- 2
The payment really settled
The envelope is read from the contract: amount, token and the moment it arrived, straight from NEAR rather than from your file.
- 3
The earner signed it
Each disclosed payment carries a signature from the key that owns it, over a statement naming the reader and an expiry date.
The third check is the one that matters. A client who paid one of these invoices knows every detail of it, and still cannot present it as their own income, because they never held the envelope key.
Check a real proofWho sees what
Anyone reading the chain
Can see
That some envelope received an amount from some account
Cannot see
Which envelopes belong to one person, and every invoice detail
Whoever you hand a proof to
Can see
Exactly the payments you selected, and when they settled
Cannot see
Every payment you left out of that proof
Where the privacy stops
Amounts, paying accounts and settlement times are public on NEAR. Opening two envelopes into the same account links those two payments to each other. Cachet hides you from the people who pay you. It is not a mixer, and it does not pretend to be. Settling through NEAR Confidential Intents on mainnet, which would hide where the money lands as well, is on the roadmap and is not part of this release.
Send your next invoice sealed
One form, no account, and no server to send your invoice to.