Review Bitcoin change outputs before sharing a payment screenshot

A transaction screenshot can reveal more than the payment

Bitcoin spends previous outputs and can create both a recipient output and change back to the sender. A screenshot or explorer link may therefore reveal unrelated balances, addresses or transaction history. Before sharing evidence, identify which fields actually prove the payment and remove everything support does not need.

Bitcoin Core's send RPC documentation treats recipients, selected inputs, change address, change position, fee policy and wallet bookkeeping as separate transaction controls and results. Annotate the privacy consequence of the source title, access date and jurisdiction on the transaction-privacy annotation before adding a sharing evidence of a Bitcoin payment conclusion. reconstruct the sequence in chronological order.

List every transaction output

A transfer can include the intended recipient, change and additional outputs created by wallet behavior. Write each output index, amount and likely role before labelling the payment. Do not assume the largest or last output is always change. Annotate the privacy consequence of output index, address, amount and tentative role while examining sharing evidence of a Bitcoin payment. Maintain a private original and a deliberately redacted share copy of the transaction-privacy annotation. Attribute the list every transaction output observation to Bitcoin Core 30.0 send RPC documentation, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For output index, address, amount and tentative role, name the origin of every copied value. Explain every redaction while retaining the public proof; preserve both timestamped versions whenever the transaction-privacy annotation still shows a conflict.

Match the recipient independently

The receiving address should come from the authenticated invoice rather than from visual similarity. Compare the complete address or supported checksum through the wallet's review screen. A truncated explorer display cannot prove that two addresses are identical. Annotate the privacy consequence of invoice address, full output address, checksum and source while examining sharing evidence of a Bitcoin payment. Maintain a private original and a deliberately redacted share copy of the transaction-privacy annotation. Attribute the match the recipient independently observation to Bitcoin Core 30.0 send RPC documentation, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For invoice address, full output address, checksum and source, avoid turning a current status into a permanent promise. Explain every redaction while retaining the public proof; preserve both timestamped versions whenever the transaction-privacy annotation still shows a conflict.

Keep change ownership private

A change address may link the payment to other wallet activity if published unnecessarily. Crop or redact unrelated change details when the support question does not require them. Redaction should not alter the transaction hash or recipient output used as evidence. Annotate the privacy consequence of change output, redaction area, retained hash and recipient output while examining sharing evidence of a Bitcoin payment. Maintain a private original and a deliberately redacted share copy of the transaction-privacy annotation. Attribute the keep change ownership private observation to Bitcoin Core 30.0 send RPC documentation, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For change output, redaction area, retained hash and recipient output, reconstruct the sequence in chronological order. Explain every redaction while retaining the public proof; preserve both timestamped versions whenever the transaction-privacy annotation still shows a conflict.

Avoid address-reuse assumptions

Reuse can expose patterns but does not by itself identify the human controlling an address. Document whether the wallet generated a new address and avoid public labels that overstate ownership. Blockchain heuristics are interpretations rather than identity proof. Annotate the privacy consequence of address reuse, wallet behavior, public label and confidence level while examining sharing evidence of a Bitcoin payment. Maintain a private original and a deliberately redacted share copy of the transaction-privacy annotation. Attribute the avoid address-reuse assumptions observation to Bitcoin Core 30.0 send RPC documentation, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For address reuse, wallet behavior, public label and confidence level, name the origin of every copied value. Explain every redaction while retaining the public proof; preserve both timestamped versions whenever the transaction-privacy annotation still shows a conflict.

Choose the minimum evidence set

Most credit investigations need the transaction hash, network, output amount and account reference. Ask support what is necessary before sending a full wallet screen. Balances, contact names and unrelated history can create needless exposure. Annotate the privacy consequence of hash, network, recipient output and account reference while examining sharing evidence of a Bitcoin payment. Maintain a private original and a deliberately redacted share copy of the transaction-privacy annotation. Attribute the choose the minimum evidence set observation to Bitcoin Core 30.0 send RPC documentation, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For hash, network, recipient output and account reference, avoid turning a current status into a permanent promise. Explain every redaction while retaining the public proof; preserve both timestamped versions whenever the transaction-privacy annotation still shows a conflict.

Store the private annotation securely

A full internal map can be useful for the account owner even when the shared version is redacted. Keep access limited and record when and where the redacted copy was sent. Do not upload the internal map to a public image host. Annotate the privacy consequence of private copy, shared copy, recipient and retention date while examining sharing evidence of a Bitcoin payment. Maintain a private original and a deliberately redacted share copy of the transaction-privacy annotation. Attribute the store the private annotation securely observation to Bitcoin Core 30.0 send RPC documentation, an authenticated page, a public ledger, an official scorecard or a shown calculation as appropriate. For private copy, shared copy, recipient and retention date, reconstruct the sequence in chronological order. Explain every redaction while retaining the public proof; preserve both timestamped versions whenever the transaction-privacy annotation still shows a conflict.

Assemble the transaction-privacy annotation as six working rows

1) List every transaction output — output index, address, amount and tentative role; 2) Match the recipient independently — invoice address, full output address, checksum and source; 3) Keep change ownership private — change output, redaction area, retained hash and recipient output; 4) Avoid address-reuse assumptions — address reuse, wallet behavior, public label and confidence level; 5) Choose the minimum evidence set — hash, network, recipient output and account reference; 6) Store the private annotation securely — private copy, shared copy, recipient and retention date.

Use Bitcoin Core to identify change-related controls

The Bitcoin Core RPC reference documents explicit recipient outputs, wallet-selected or caller-supplied inputs, optional change address and change position, and the resulting transaction identifier. Open Bitcoin Core 30.0 send RPC documentation over HTTPS and date that sharing evidence of a Bitcoin payment source on the transaction-privacy annotation.

It does not identify which output a different wallet selected as change or establish who controls a public address. Explain every redaction while retaining the public proof. The site's source-checked guides explain related terms.

Share proof of payment without publishing the wallet

Retain the hash and recipient output in the evidence copy, remove unrelated wallet context and note every redaction so the record remains honest. Keep the transaction-privacy annotation in date order and keep secrets outside it.

Privacy matters for every adult 18+, yet redaction does not reduce house edge. Share only necessary payment proof, cap discretionary spend beforehand and stop instead of using another wager to offset an exposed transaction. Use the responsible-play centre when stronger separation or confidential support is needed.