Monero hides payments. How do you prove you paid someone?
Monero users can prove that a transaction directed money to a particular address without publishing their whole wallet history, using transaction-specific information that lets a recipient or mediator check the payment, while the wallet’s separate spend and view keys remain subject to different disclosure rules and an ordinary transaction hash does not reveal a public receipt.
- Monero’s public blockchain does not display a conventional list of identifiable senders, recipients and transferred amounts, so sending someone a transaction hash alone does not give them the same payment information they could inspect on a transparent blockchain.
- The project’s payment guide describes verification using the transaction ID, destination address and transaction-specific key, while its wallet software also supports signed transaction proofs that can include a message agreed by the parties.
- A payment proof, a proof of spending and a wallet-balance proof serve different purposes, making the question being verified important before the sender discloses additional information or the merchant accepts the result.
- Sharing a private view key opens a much larger window into wallet records than disclosing a single transaction, and a basic view-only wallet needs additional information to track spent outputs accurately without receiving the private spend key.
- A valid proof does not automatically settle an invoice, reverse a payment or establish that every associated output remains spendable, leaving address verification, confirmation status and the recipient’s wallet records central to resolving a dispute.
A merchant says an invoice remains unpaid. The buyer opens a Monero wallet, sees the outgoing transaction and sends its hash, expecting that to settle the disagreement.
The merchant cannot use the hash to read the destination and amount from a public explorer in the usual way. Monero keeps those details private, but its wallets provide ways to disclose and verify a specific payment when the parties need a receipt.
The buyer can provide a transaction-specific proof for the merchant to check against the address and amount on the invoice. A recovery phrase or private spend key is not needed for that check, and sharing either would expose authority over the wallet rather than simply document the purchase.
Why the merchant cannot just check the hash
Monero’s blockchain records the transaction without displaying the recipient and amount as a conventional public receipt. A merchant can recognize its own incoming payments through its wallet, but an outside observer cannot obtain the same information merely by opening a transaction hash.
The network is still checking that the transaction follows its rules. Keeping payment details private does not mean the sender can invent a balance or spend the same funds repeatedly.
The difficulty appears when someone outside the two wallets needs to check a payment. A mediator handling an invoice dispute does not possess the merchant’s wallet information and cannot simply inspect the receipt as the merchant can.
Monero’s official payment guide describes the additional information used for that check: the transaction ID, the destination address and the transaction-specific key. Together, they allow the amount directed to the selected address to be verified.
The address connects the claim to the merchant. A valid hash can refer to any transaction, including one that had nothing to do with the invoice being disputed.
A screenshot of the buyer’s wallet supplies more detail, but the merchant still needs to verify it. The amount and address shown on an image are claims made by the person supplying it, rather than a result the merchant has independently checked.
The recipient’s own wallet has a different starting point. It holds the information needed to recognize incoming transfers, which is why a merchant does not have to request every customer’s wallet secrets to accept routine payments.
Monero’s merchant documentation covers receiving through its wallets and through payment integrations. The business can keep its own payment records while the same transaction remains private to ordinary blockchain observers.
The comparison of privacy coins published by crypto.news describes different approaches to hiding payment details. An explorer-based receipt procedure used for a transparent network should not be assumed to work unchanged for XMR.
For a dispute, the parties can begin with the address issued for the order and the buyer’s transaction ID. Those records establish the payment they are investigating before additional information is disclosed.
One payment can be opened for verification
The sender’s wallet can retain transaction-specific information for later checks. It is separate from the recovery backup and private spend key that control the whole wallet.
The traditional process in Monero’s guide has the sender retrieve the transaction key and provide it with the transaction ID and recipient address. A checking wallet uses those details to decode the amount directed to that destination.
The guide describes “a one time key” generated for the transaction. Despite the similar terminology, sharing that transaction-specific information is different from giving someone the private key needed to spend the wallet’s funds.
The graphical wallet and command-line wallet provide ways to retrieve the relevant information. The checking functions do not require sending the wallet recovery phrase to the person requesting payment evidence.
A merchant checking one purchase therefore does not need to begin by demanding access to every payment the buyer has made.
The recipient of the proof still learns private payment details. Sending those details through an agreed support channel keeps the disclosure more limited than publishing the transaction key, destination and invoice in a public complaint.
Monero also supports signed transaction proofs. Its wallet RPC documentation describes get_tx_proof, which takes a transaction ID, destination address and optional message and returns a signature for checking.
The other party verifies the proof using the expected information. If the sender included a message when generating it, the same message is used in the verification process.
For a hypothetical invoice called INV-104, the parties could agree on text identifying the payment dispute. The resulting proof binds that selected text to the verification, while the invoice itself retains the business terms and payment request.
The message does not create an independent record showing when the invoice was issued. It also does not authenticate a merchant simply because the merchant’s name was typed into the text.
The wallet needs the information required by the proof being generated. Keeping transaction history and payment records can therefore matter after funds have moved, even when the owner has safely preserved the recovery material needed to regain wallet access.
A provider asking for evidence should identify which proof it can check and what it needs to verify. That gives the sender a defined request instead of an open-ended demand for a wallet file or recovery phrase.
The invoice decides which receipt matters
Take a hypothetical order requiring a payment of 2.5 XMR. Before investigating an unpaid message, the merchant needs to compare the destination used by the buyer with the address originally supplied for that order.
A genuine 2.5-XMR transfer to another address does not satisfy the invoice merely because the number is right. The checkout record, invoice or previously agreed instructions establish where the merchant asked the buyer to send the funds.
The payment amount then needs to be checked in XMR. A dollar figure displayed in a wallet can change with the price source and time, even while the underlying coin amount stays the same.
If the invoice was denominated in dollars, its conversion and expiry terms become part of the investigation. The transaction proof establishes payment information; the invoice establishes whether the amount met the agreed price at the relevant time.
The buyer’s total deduction can also include the network fee. A wallet spending 2.5 XMR plus a fee has sent a different amount to the merchant from a payment in which 2.5 XMR describes the total wallet reduction.
A provider can also show a requested withdrawal amount that differs from the net amount sent after its charge. In a hypothetical 2.5-XMR invoice, a transfer delivering 2.49 XMR would leave a 0.01-XMR shortfall even if the customer authorized a 2.5-XMR deduction at the sending service.
The figures illustrate why the receipt amount matters. The provider’s withdrawal record and fee policy can explain the difference, while the merchant still has to reconcile what actually reached the destination.
A purchase funded in several transactions needs each relevant receipt. The official guide says the verification process must be repeated for each transfer, rather than treating one proof as evidence of an entire series of payments.
In the example, receipts of 1 XMR and 1.5 XMR could together meet a 2.5-XMR amount if they reach the agreed destination under the invoice terms. Producing only the first proof would leave the rest unexplained.
The same payment should not be credited to two orders. A customer can present a genuine historic receipt again, leaving the merchant’s records to establish whether it was already applied to another completed invoice.
A late payment creates another possible disagreement. The transfer can be valid while the original quote has expired, requiring the merchant to apply its published terms for the remaining price or refund.
The merchant’s wallet must also be synchronized. A stale local view can leave a payment absent from the screen even though the transaction is already recorded on the chain.
Monero’s wallet command reference distinguishes incoming, outgoing, pending, failed and pool records. Those statuses help a business identify whether it is looking at a prepared transfer, an unconfirmed submission or a recognized receipt.
Checking those details before requesting a second payment can prevent an unnecessary overpayment. An incorrect destination, a shortfall and an uncredited full receipt require different responses, even if the order page calls all three unpaid.
The wallet offers more than one kind of proof
Monero provides transaction proofs, spend proofs, reserve proofs and signed messages. They serve different purposes, so choosing a proof starts with the claim the other party wants to check.
A transaction proof helps verify a transfer involving a selected address. A spend proof addresses whether the proving wallet made the payment, while a reserve proof concerns a balance claim.
The command reference lists separate generation and checking functions for those tasks. The existence of a genuine transaction does not, by itself, show that the person presenting its hash was the sender.
A merchant considering a refund may know the same transaction ID as several other people. A spend proof can help check the claimant’s role in making the payment, instead of treating knowledge of the hash as evidence of who sent it.
The distinction also matters when a business claims it still holds money. A valid proof of a payment made months earlier cannot establish the amount available in that business’s wallet now.
Monero’s technical documentation contains an explicit warning about transaction-key and related payment-proof checks. A successful check can show that an amount was directed to an address without guaranteeing that the associated output remains spendable.
The funds could have been spent afterward or be subject to a lock. The documentation also identifies other technical conditions affecting output spendability, which the recipient’s wallet needs to account for before relying on the amount as available funds.
A payment proof is consequently useful as evidence of a transfer, while confirmation and availability remain part of the recipient’s own checks. The business should not treat one historic receipt as a continuously updated balance statement.
| Evidence | What it helps verify | What the parties still need |
| Transaction hash | The blockchain record being discussed. | The destination and payment details claimed. |
| Transaction-specific proof | Information about an amount directed to the selected address. | The invoice match and recipient’s current wallet status. |
| Spend proof | The proving wallet’s role in making the payment. | The order or obligation the payment was intended to satisfy. |
| View-only access | Incoming activity recognized through the disclosed viewing information. | Spent-output updates for accurate outgoing tracking. |
The proof checker supplies a technical result; the merchant then reconciles it with its order records. That avoids assigning a stronger meaning to a valid proof than the wallet documentation gives it.
A view key opens a much larger record
A private view key can be used to create a view-only wallet. Instead of checking just one disputed transfer, the observer receives access to incoming activity recognized through that viewing information.
The official view-only guide says such a wallet can recognize incoming transactions without holding the private spend key. It cannot sign transactions to move the funds.
A merchant can use that separation for monitoring, or give an accountant visibility into receipts without granting spending authority. The access is useful precisely because it reveals more than one isolated payment.
For a customer settling a single invoice, that can be more disclosure than necessary. Transaction-specific verification allows the parties to investigate the receipt without starting a longer-term viewing arrangement.
A basic view-only wallet also needs additional information to track outgoing spends accurately. The command reference describes exporting and importing key images so it can learn which outputs have been spent.
Suppose the wallet recognized 10 XMR of receipts and later spent 4 XMR, ignoring fees in this illustration. A viewing copy that knows the incoming transfers but has not learned which outputs were spent cannot reproduce the full available balance.
The receipt total is still valid history. It is not evidence that all 10 XMR remains available for a refund or another payment.
Updating spent-output information is different from sharing the private spend key. The former helps the observer account for activity; the latter supplies authority that the observer did not need for a receipt check.
Earlier Monero security guidance stressed protecting private wallet credentials. The proof functions give users a narrower way to answer an appropriate payment question without handing over the recovery backup.
The local wallet password has a different role again. Changing it protects the wallet files under the new password, but the command reference says that operation does not change the underlying secret keys or backup.
Someone already holding a disclosed view key is therefore not locked out merely because the owner changes the password on a local installation. Future visibility has to be assessed against the information that person actually received.
A support request should make that scope clear before the owner agrees to it. Read-only access prevents spending, but it can still expose financial records the owner never intended to share with a merchant.
Exchange payments bring the provider into the dispute
A customer can pay from a personal wallet, an exchange or a service converting another asset into XMR. The sending arrangement determines who holds the transaction information and can generate the requested evidence.
An exchange controls its own sending wallet. The customer may have a withdrawal reference and a transaction hash without possessing the transaction secrets retained by the exchange.
The customer then needs assistance from the provider to obtain the appropriate proof. Installing another wallet locally does not recreate information from a transaction that a different wallet prepared and sent.
The withdrawal record still matters. It shows the amount requested, the destination supplied and the reference the provider can use to locate the payment inside its own system.
The receiving side can also involve an intermediary. A payment processor may control the merchant’s receiving address and report the result to the merchant’s order system after applying its confirmation requirements.
Monero’s address documentation describes the address types used by wallets and services. A unique address or associated payment-identification information can help the provider connect a receipt to the right account or invoice.
The subaddress guide describes assigning a different subaddress to an anticipated payment. Replacing that invoice destination with the merchant’s main address during a dispute can break the connection the business’s software expected.
A provider can also recognize a transaction before it credits the customer’s account. Its confirmation policy and internal reconciliation determine when the order page changes, separately from when the transfer first appears.
The comparison of Monero exchange routes discusses order references and confirmation requirements alongside blockchain payments. Those records are especially useful when one provider sends the funds and another is responsible for crediting them.
If the receiving processor has recognized the full payment but the invoice remains unchanged, the remaining problem may be in that connection. Sending the amount again could create an overpayment while the original record still needs repair.
The support investigation therefore needs both sides’ records where intermediaries are involved. The blockchain can supply the transfer evidence, while the exchange and processor explain how their accounts were updated.
Keeping a receipt is different from backing up the wallet
A dispute may arise after the owner replaces a phone, restores a wallet or loses access to the original invoice page. Preserving transaction records makes that later investigation easier without requiring the recovery backup to be shared.
Monero’s wallet reference includes transaction notes, transfer exports and proof-generation functions. Those tools can keep an order reference attached to the transaction the owner intended to use for payment.
A local note can help the owner remember the purpose of a transfer, but it is not a new payment recorded on the chain. Renaming an entry to match an invoice does not change the destination, amount or the proof that another person can verify.
The business should preserve the invoice separately, including the address and terms originally supplied. That gives a later support investigation something to compare with the transaction rather than relying only on labels added after the dispute began.
The recovery backup restores access to keys. It should not be assumed to reproduce every local note, merchant identifier or transaction-specific record retained by the previous installation.
A business can therefore keep accounting records separately from the secrets used to authorize spending. The invoice and its proof can be stored together while recovery material remains protected under the owner’s backup arrangements.
Export options require attention before a file is sent to support. The command reference allows transfers to be exported with transaction private keys where available, potentially disclosing more than the single payment under investigation.
A full history export can reveal unrelated purchases and receipts. The narrower proof is preferable when those other records do not help resolve the invoice.
Public complaints can expose the same information in another form. A transaction key posted beside an invoice, shipping details or a named business can give observers the context needed to identify a payment that the chain itself kept private.
Deleting the post afterward cannot reliably recover copies other people made. The protocol’s privacy protections do not remove information the parties voluntarily published elsewhere.
The software used to prepare and verify the proof also belongs in a technical support record. The application name and version can help reproduce an error without giving support a seed or spending key.
A 2021 report about Monero wallet-code privacy illustrates why implementation details have mattered to users. It is historical context, rather than evidence that a current wallet still contains the same flaw.
The history of Monero merchant adoption has included the ordinary needs of receiving payments and keeping accounts. A private transaction can still need an invoice, a receipt and a record of what the business delivered.
The proof leaves the refund to the parties
Once a merchant verifies the payment, it can update the invoice in its own records. The blockchain transaction does not need to be rewritten to record that administrative decision.
The proof also does not decide whether goods were delivered or a refund is owed. Those questions depend on the purchase terms and the dispute process the parties use.
A buyer can have paid correctly and still disagree with the merchant about the product. Conversely, a failed receipt claim does not establish every fact about the underlying order.
Refunding the payment requires another transfer or an agreed alternative. A proof supplies evidence; it is not an instruction allowing the sender to pull the original funds back from the recipient.
The return destination should be agreed through the genuine support channel. The merchant should not assume it can identify a suitable refund address from the public transaction or from an unsolicited message claiming to be the buyer.
If several transfers funded the purchase, the refund record can identify which receipts are being returned. That keeps the commercial record consistent with the separate payments already verified.
Neither side needs the other’s recovery phrase or private spend key to complete that receipt check. The wallet tools separate evidence of a payment from authority over the remaining funds.
The official graphical-wallet guide puts verification in the Prove/Check interface. Given the expected transaction information, the checking function reports the amount associated with the selected destination and the transaction’s confirmations.
What to Watch
- Invoice destination: The exact address or payment-identification details originally supplied, compared with the destination used in the transaction being presented as evidence.
- Proof type: Whether the request concerns a payment, sender spending, a balance claim or ongoing wallet visibility, with only the information needed for that question disclosed.
- Recipient status: Confirmation, synchronization and spendability in the receiving wallet, distinguished from the narrower result of a successful transaction-proof check.
- Provider records: Exchange withdrawal references, processor invoice identifiers and deposit-crediting policies that connect an onchain transfer with the service’s internal account.
- Data disclosure: The contents of screenshots, exports and proof messages before sharing, particularly when a file could reveal payments unrelated to the invoice in dispute.
FAQs
Why does a Monero transaction hash not prove the invoice was paid?
The hash identifies a blockchain transaction without publicly displaying the recipient and amount in the usual transparent-chain format. The merchant also needs the relevant destination and verification information, then has to match the result to the invoice. A valid transfer to another address is not payment of that order. Likewise, a genuine old receipt may already have been credited, so its validity alone does not establish a new payment.
What information does the traditional payment guide use?
It describes providing the transaction ID, recipient address and transaction-specific key. A checking wallet uses those details to verify the amount directed to the selected address, without receiving the private spend key or recovery backup for the wallet. The disclosure still reveals information about that transaction, so it should be shared with the party who needs the receipt rather than automatically published alongside an invoice or identifying customer details.
Can a sender provide a signed proof instead?
Monero supports generating and checking a transaction proof, with an optional message included in the process. The verifier uses the expected transaction, address and message with the supplied proof. The parties should agree on the claim they want checked, because transaction proofs, spend proofs and reserve proofs serve different purposes. Adding an invoice reference supplies context but does not independently authenticate the business or establish when the invoice was issued.
Does a valid proof establish the recipient’s current balance?
No. Monero’s technical documentation warns that a successful transaction-proof check does not guarantee the associated funds remain spendable. They could have been spent afterward, be locked or have another technical spending limitation. The proof can help establish a transfer while the recipient’s own wallet establishes its current status. A merchant should not turn evidence of a historic receipt into a claim about money available for a refund today.
Should the sender share a view key to settle one invoice?
A transaction-specific proof normally offers a narrower way to investigate one payment. A view key can reveal incoming wallet activity beyond that receipt, although it does not itself authorize spending. Basic view-only tracking also needs additional spent-output information for an accurate account of outgoing activity. A support request should explain why that larger disclosure is necessary before the owner provides access to records unrelated to the disputed purchase.
What if an exchange sent the Monero?
The exchange controls the sending wallet and may hold transaction information the customer does not have. Keep the withdrawal reference, requested amount and exact destination so the provider can locate its own transfer and supply appropriate evidence. A local wallet cannot reconstruct every proof for a transaction prepared elsewhere. The merchant’s processor may also need to reconcile the recognized receipt with its invoice, separately from the exchange’s withdrawal record.
Can the proof cancel or refund the payment?
No. It supplies evidence about the original transfer rather than an instruction allowing the sender to reclaim it. A refund requires another payment or an agreed alternative, with the return destination verified through the genuine support channel. The dispute about delivery or product quality also remains a commercial matter. Neither party needs to surrender a recovery phrase or private spend key to verify the original receipt.
Does sharing a proof remove Monero’s privacy entirely?
It reveals selected information to the people receiving it rather than automatically exposing the wallet’s full history. Posting that information publicly with an invoice, customer name or shipping address can identify the payment more widely, and deleting the post cannot reliably remove copies. Share the evidence needed for the dispute and keep spending credentials separate from the receipt. This is educational analysis, not investment advice.
Disclaimer: This article is for information and educational purposes only and does not constitute financial or investment advice. Figures reflect regulatory filings and reporting available at the time of writing and change with each disclosure. Nothing here is a recommendation to buy, sell, or hold any security or asset. Always do your own research. Information is accurate as of Nov. 17, 2026. Legal and tax questions should be discussed with qualified professionals.