A customer brings a purchase question to a second register and offers to send a photo of their card. Stop there. The fastest useful search key is usually the merchant’s receipt number, or a combination of store, date, approximate time and total. A normal service request should not create a new copy of payment credentials.
Search for the sale, not the person
Consider two $22.68 sales on the same afternoon. The customer shows a slip that identifies Lane 4 and a timestamp of 2:18 p.m. Narrow by location and time, then confirm the basket or permitted transaction reference. Finding an amount alone is not a match, and a receipt request is not permission to reveal another shopper’s purchase. If the POS only offers a lookup method you’re not authorized to use, route it to a lead rather than collecting card details off-system.
Square’s transaction-search documentation provides one example of a merchant system that can find a sale and issue another receipt from its record. Not every register can do it at every lane. Check where authorized staff can reprint and whether a paper reprint or an approved digital copy is available.
Check the customer copy, not just the screen
For the U.S. customer receipts covered by the applicable federal rule, an electronically printed debit or credit card receipt must omit the expiration date and show no more than the last five card digits. The FTC’s receipt guidance explains that rule. It is not permission to collect the rest of the digits elsewhere. The PCI Security Standards Council’s note on masking and truncation explains why a masked printout does not settle what is stored behind it.
Never photograph a payment card for a receipt lookup, copy full payment credentials into chat or paper logs, or move a customer’s digital receipt to an unapproved mailbox. If the printed copy looks wrong, report the issue through the store’s approved channel without reproducing the exposed digits. Keep the original’s security separate from the operational question addressed in checking a timed-out attempt.