Redact a Receipt Before Posting or Sending It
Receipts get shared for expense claims, warranty proof, returns, and resale listings. They carry more identifiers than most people expect, and the small ones at the bottom are the ones that matter.
Free, no account, and the image never leaves your browser.
A receipt is a compact identity document
A printed receipt often contains the last four digits of a card, the cardholder's name in some jurisdictions, a store and register number, a cashier identifier, a timestamp to the minute, a loyalty account number, and a QR code or barcode that resolves to the full transaction on the retailer's system. Individually these are minor. Together they are enough to answer verification questions or to retrieve the complete order record.
The resale-listing case is the most exposed. Someone photographs a receipt to prove a device was purchased, posts it publicly with the item, and publishes a timestamp, a store location, and a payment identifier alongside the serial number. That is a strong correlation set for anyone building a profile.
Expense claims have a different problem: the receipt travels through an internal system and often a third-party processor, and it is retained. Redacting the payment digits before submission is both a data minimization step and, in a growing number of jurisdictions, the expected handling for payment data that is not needed for the claim.
What to cover on a receipt, top to bottom
Receipt layouts vary, but the fields cluster in the same places. Work downward.
- Card digits and payment method
- Usually near the total: 'VISA ****1234' or a masked number. Cover the digits; the card network alone is not identifying.
- Cardholder name and signature line
- Printed on some merchant copies and on signed slips. Both identify a person.
- Store number, register, and cashier ID
- These identify which transaction it was, not just where. Useful for a retailer to look up the full record.
- The QR code or barcode
- Retail receipts increasingly print a code that opens the digital receipt. It is a direct pointer to the full transaction and usually encodes an order identifier.
- Loyalty or membership number
- Links the purchase to a named account, which is a stronger identifier than the payment digits.
- Exact timestamp
- To the minute, plus a store location. Consider whether your use case needs it; a warranty claim usually needs the date, not the time.
- Order and invoice numbers
- Frequently usable as a lookup key on the merchant's order-tracking page, sometimes with just an email address.
- Delivery address on shipped orders
- Printed in full on packing slips. Cover it when the receipt is being shared publicly.
Receipts are the hardest input for text recognition
Thermal paper is low contrast, glossy, and often photographed at an angle. Expect the detection pass to find less here than it would on a screenshot, and plan to draw most boxes by hand.
Found automatically
- Card numbers of 13 to 19 digits that pass the Luhn checksum, when printed in full
- Email addresses, which appear on e-receipts and loyalty sign-ups
- US phone numbers, on merchant footers and customer service lines
- IPv4 addresses, rarely, on network-printed receipts
Needs a box by hand
- Masked card digits such as ****1234. Four digits alone do not match the card pattern, and they are exactly what a receipt prints.
- The QR code and barcode. These are graphics, not text, and detection does not read them at all.
- Store numbers, register IDs, and cashier identifiers.
- Order numbers, which are usually alphanumeric and not one of the matched patterns.
- Most text on a curved, glossy, thermally printed receipt, where recognition accuracy drops significantly.
Getting a receipt clean enough to share
Photograph or scan it flat, then redact the image. Trying to redact a photo taken at an angle makes every box harder to place accurately.
Get a flat, even image
A scanner or a flat-lay photo in even light gives the recognition pass and your own eye the best chance. Curved thermal paper with a highlight across the middle is the worst case.
Open it here
Drop, paste, or choose the file. PNG, JPEG, and WebP up to 25 MB and 40 million pixels. Nothing is uploaded.
Cover the payment block first
Card digits, cardholder name, signature. This is the group with the most direct abuse path and the one that is most consistently overlooked on expense receipts.
Cover the codes
The QR code and the barcode, completely — not just the middle. A partial code can still be reconstructed if enough of the finder patterns survive.
Cover the lookup keys
Order number, loyalty number, cashier and register IDs. These are what let someone else retrieve the full transaction.
Decide on the timestamp
Keep the date for warranty purposes, and consider covering the exact time if the receipt is going somewhere public.
Export and check the edges
Thermal receipts fade at the edges, and a box that looks complete on screen may leave a sliver of a digit visible in the exported file. Zoom in.
A four-digit tail is still a disclosure
Receipts almost never print a full card number. They print the last four digits, sometimes with the card network. That feels safe, and it is much safer than the full number — but it is not nothing.
The last four digits are one of the standard verification fields for a merchant. Combined with an order number, a name, and a date, they are often sufficient for a phone agent to discuss an order or change a delivery address. In a resale listing, they sit next to a serial number and a timestamp, which is a coherent set for someone assembling an identity.
This is where the tool's detection has a blind spot worth stating explicitly. The card pattern requires 13 to 19 digits. A four-digit tail does not match, so detection will never find it. If you run auto-detect on a receipt and it reports nothing, that is not evidence the receipt is clean — it is evidence that no full-length number was found.
The QR code has the same property for a different reason. It is not text, it encodes the transaction identifier, and a redaction of the surrounding text leaves it completely intact. Cover it as a block.
Frequently asked questions
- Auto-detect found nothing on my receipt. Is it clean?
- Not necessarily. Receipts usually print masked card digits rather than full numbers, and masked digits do not match the card pattern. If detection reports nothing, check the payment block, the QR code, and the order number by hand.
- Should I cover the QR code?
- Yes, if the receipt is going anywhere public. Retail QR codes typically resolve to the full digital transaction, so leaving one visible defeats the purpose of covering the text.
- Do I need to hide the total?
- Only if the amount itself is sensitive. For a warranty or expense claim, the total is usually the point. For a public post, consider whether the amount says something about you that you did not intend to publish.
- Can I photograph the receipt instead of scanning it?
- Yes, and phone photos are usually fine. Get the receipt flat, avoid a highlight across the middle, and check the exported file at full zoom — thermal printing fades unevenly and can hide a partially visible digit.
- What format do I get back?
- A PNG at the original resolution. It is drawn on a fresh canvas and encoded from pixel data, so the file is rebuilt rather than edited in place.