A support enquiry may need a transaction reference, date, amount and purchased plan. It usually does not need an entire bank statement or unrelated transactions. Share a limited receipt through the verified contact, and mask full card numbers, account balances and personal information that does not help identify the purchase.
Keep the matching fields visible
The amount, currency, date and reference help distinguish similar purchases. Keep those together rather than cropping the receipt so tightly that the relevant transaction cannot be identified. Use the actual payment record instead of a manually retyped claim.
Remove unrelated material
A statement can expose spending history, addresses and account numbers. Export or crop the relevant transaction and redact unnecessary values. Keep the original privately in case the payment provider later needs it.
Separate proof from permission
A receipt is evidence of a transaction, not authorization to take control of your payment account. Do not share one-time payment codes, banking passwords or remote access in order to “verify” the receipt.
A practical sequence
0 of 3 steps completed on this page.
An example to work through
A receipt showing a $24.99 three-month purchase and its transaction reference is more relevant than a screenshot of an entire monthly bank statement.
Questions about this topic
Does support need my banking password?
No. A receipt enquiry does not require that secret.
Should I discard the original receipt?
Keep it privately for your own records and any payment-provider enquiry.


