WEIMI INSIGHTS / PAYMENT EXPERIENCE
Connect the purchase reference, customer support and payment records without making receipt collection unnecessarily complicated.
CUSTOMER
A clear route to the correct purchase record.
OPERATOR
A reference that support can actually trace.
BUYER
A tested feature in the quoted configuration.
A bank notification confirms a card event; a useful sales receipt should help the customer identify what they bought and how to resolve a problem.
01 / BUYER NOTES
Someone buying lunch at work may need an expense record. Another customer may want evidence of a missing item or an unexpected charge. Decide which needs the receipt must meet before comparing printers, QR codes or email options. A payment terminal’s generic transaction slip may not contain product-level detail.
Ask to see a sample generated by the proposed machine and payment setup. Check the seller information, date, currency, items, amounts and transaction reference. Tax and invoice requirements differ between countries, so have the required fields reviewed for the market where you will operate.
02 / BUYER NOTES
A QR code on a screen can mean several things: a link to that purchase, a general receipt portal or simply a support page. Test what the customer sees after scanning it, how they locate the right transaction and whether the process still works after the machine returns to its home screen.
If email or a phone number is requested, check when and why it is collected. Keep optional marketing consent separate from obtaining a purchase record. Customers should be able to understand who receives their details and where to find the relevant privacy information.
03 / BUYER NOTES
Try a cancelled selection, a payment that fails, a successful purchase and a refund. For a smart fridge, also check the relationship between an initial authorisation and the final purchase amount. A temporary hold should not be presented as though it were the final itemised sale.
Support teams need to match a receipt reference to the appropriate sales and payment records. Establish which reference they should ask the customer to provide. Avoid workflows that require full card numbers or screenshots containing unrelated financial information.
04 / BUYER NOTES
Confirm which company supplies the receipt feature and who supports it if it stops working. It may depend on the terminal provider, vending software or a connected service. Ask about recurring charges, supported markets, retention periods and what happens when connectivity is interrupted.
Keep the tested sample and written feature description with your purchase specification. Then repeat the check on the installed machine. A demo receipt from different hardware or another country does not establish that your final configuration offers the same customer experience.
Useful when: Customers can scan a code during or after purchase.
Check: Visibility, link lifetime and protection against access to other customers’ records.
Useful when: Customers want a record they can retrieve later.
Check: Address entry, delivery failures and the stated data purpose.
Useful when: The site needs a physical record or a phone-free option.
Check: Paper replenishment, printer faults and maintenance access.
PRACTICAL ANSWERS
No. The available receipt method depends on the terminal, software, integration and local setup. Confirm it explicitly in the quotation.
Not necessarily. The required details and the process for requesting an invoice depend on the applicable rules and the seller’s system.
A static code can lead to a portal, but the portal still needs a reliable and appropriately protected method of finding the customer’s transaction.
YOUR NEXT STEP
Describe the receipt format your customers need, the countries of operation and the support workflow. Review mobile-wallet compatibility alongside the receipt experience.
Explore equipment →Discuss your requirements →