Proving Payments with View Keys & Proofs

If Monero hides transaction details from outsiders, how could anyone ever demonstrate that a payment was made? The answer lies in two mechanisms the owner controls: the private view key and transaction proofs. This lesson describes how they work as concepts and where people find them useful — for record-keeping, audits, or resolving disputes. It is educational, not tax or legal advice; rules vary by country — consult a qualified professional in your jurisdiction.

Recap: The Keys Behind a Wallet

As covered in Monero Public and Private Keys, a Monero wallet is built from more than one key. The important pairing here is that spending funds requires the private spend key, while merely seeing incoming funds only requires the private view key. Separating "look" from "touch" is what makes read-only disclosure possible.

What a Private View Key Reveals

Sharing a private view key gives someone the ability to scan the blockchain for incoming transactions to your address — to see what arrived and when — without any ability to move or spend those funds. It is a read-only lens onto received payments. This is the mechanism behind a watch-only wallet, where an accountant, auditor, or the owner themselves can observe activity while the spend key stays safely elsewhere.

A few conceptual limits are worth noting:

• A view key mainly illuminates incoming transactions; reconstructing outgoing details is more limited.
• Sharing a view key is not reversible — once someone has it, they retain the ability to view.
• It exposes viewing, never spending; funds remain controlled solely by the spend key.

Proving a Single Payment

Sometimes you do not want to reveal a whole address history — only that one specific payment happened. Monero wallets can generate a transaction proof (sometimes called a payment proof or spend proof) for exactly this. It lets you demonstrate to a chosen party that a particular transaction sent a particular amount to a particular address, without handing over your keys. Our dedicated lesson Payment Proofs walks through the idea in more depth.

How a Proof Is Used, Conceptually

The pattern is straightforward in outline:

1. The sender's wallet generates a proof tied to a specific transaction and recipient address.
2. They share the proof (often alongside the transaction identifier) with the party who needs to verify it.
3. The other party checks the proof in their own wallet software, confirming the payment without needing to trust the sender's word.

The result is a verifiable receipt: cryptographic evidence that a payment occurred, produced voluntarily by the person who made it.

View Keys vs. Proofs

These tools answer different questions. A view key is broad and ongoing — it reveals a stream of incoming activity to an address. A transaction proof is narrow and specific — it demonstrates one payment. Choosing between them is a matter of how much you wish to disclose: continuous visibility versus a single confirmed fact.

Where People Find This Useful

• Personal record-keeping — saving proof that a payment you made or received really happened.
• Audits or reviews — letting a trusted reviewer see incoming funds through a watch-only view.
• Disputes — showing a counterparty that a payment was sent, if a disagreement arises.

Whether any of these carries legal or official weight depends entirely on your country and situation, which differ widely and change over time. These mechanisms simply make voluntary demonstration possible; they never make it mandatory.

A Note on Sharing Carefully

Because disclosure is one-directional, it is worth understanding what each tool exposes before sharing it. A view key reveals more than a single proof does. Matching the tool to the amount you actually intend to reveal keeps you in control of your own privacy.

Understanding how to reveal a payment naturally raises a related question — how might you keep useful records for yourself in the first place? That is where we turn next.