XMR/USD
$91.60
1.12% 1 HR
24HR Change
2.91%
Price
$91.60
Market Cap
$1.561B

Proving you made a payment & verifying the proof that someone made a payment

> Tutorial > Proving you made a payment & verifying the proof that someone made a payment

Sometimes, you have to provide details about a payment that you have sent.

 

Proving that you have made a payment

For this, you must have access to the same wallet from which you previously made the payment. Due to the level of privacy that Monero allows for, people will not see a public record of payments that you have sent. In order to prove a payment, you have to have a record of something that’s called a TXKEY. This is stored against a local copy of your Monero wallet. It’s also important to note that if you have created multiple wallets for the very same address, you will not be able to use any other wallet in order to obtain the TXKEY that you will require to prove the payment.

To obtain the TXKEY for a payment that you have sent, you have to first use the show_transfers command to see a list of payments that you have previously sent out:

[wallet 47CL7F]: show_transfers

From the output of this command, you have to locate the TXID of the payment that you’ve sent. Then use the get_tx_key command in order to obtain the TXKEY for your TXID

[wallet 47CL7F]: get_tx_key 1234567890123456789012345678901212345678901234567890123456789012

Send the TXKEY or TXKEYs that have been produced by this command to the person you need to prove the transaction to, and you’re done.

 

Verifying the proof that someone made the transaction

If a person went through the process that we described above to prove a transaction to you, you could also verify that the person made the transaction. All you have to do is substitute their TXIDs and TXKEYs and also your receiving ADDRESS into the command below:

[wallet 47CL7F]: check_tx_key TXID TXKEY ADDRESS

This command will be the one that confirms the amount of Monero that was sent to your wallet.


Leave a Reply

Your email address will not be published. Required fields are marked *