Your App's Receipt Is a Trust Document, Not a Transaction Log

The payment sheet closes, the spinner stops, and your app says: “Success.” For the product team, that is the end of a transaction. For the user, it is the beginning of a small pile of questions. What did I just buy? How much was VAT? Where is the receipt? What do I show my finance team? What happens if I need a refund?

Most apps treat that moment as a technical confirmation. A green tick, an order number in 11px grey text, an email that may or may not arrive. But proof of purchase is not back-office plumbing. It is a product surface, and in the UK it has to do several jobs at once: reassure the buyer, satisfy record-keeping expectations, support refunds and survive the everyday chaos of deleted emails and patchy mobile signal.

The confirmation screen is not a receipt

A success screen is a moment. A receipt is a record. They should not be the same thing.

The screen can be celebratory, but it still needs to answer the practical questions immediately. What was purchased? Was it a one-off payment or a subscription? What was the total, including VAT? What is the order reference? Which payment method was used, ideally with the last four digits? And where can the user find this again later?

If the only place that information appears is a screen the user will navigate away from in four seconds, you have designed a receipt for the app’s convenience, not the customer’s. A useful proof-of-purchase journey gives people at least three routes back to the same information: a confirmation screen, an account or order history section, and a message they can search for later.

What a UK receipt actually needs to carry

For UK users, the receipt often has a second life. It may be expensed, filed for self-assessment, forwarded to a finance team or used to prove a subscription charge during a dispute. If your app sells to businesses or sole traders, that matters even more.

A VAT invoice is not just a prettier receipt. If your organisation is VAT-registered, a proper VAT invoice normally needs clear details: your business name and address, your VAT registration number, a unique invoice number, the date, a description of what was supplied, the amount before VAT, the VAT rate and the total. Consumer-facing apps sometimes avoid this by issuing a simpler receipt, but if a customer asks for a VAT invoice, “email us and we will post one” is a poor experience in 2026.

You do not need to turn the confirmation screen into a tax document. But the journey should make the right document easy to find, download and forward. Think about what happens when someone taps “Get receipt” six weeks later. Is it a PDF that opens cleanly on an iPhone? Is it an HTML page that works without an app update? Does it include a support route if the customer’s details were entered incorrectly?

Email is not a delivery strategy on its own

Many teams ship proof of purchase as a single email and assume the job is done. Email is useful, but it is not guaranteed. It lands in spam, gets filtered by corporate tenants, arrives while the user is on a train with no signal, or gets deleted in a clear-out.

A robust journey offers options. Send an email, but also keep the receipt available in the account area. Offer a resend button that does not require a support ticket. If you use SMS, keep it short and useful: order reference, amount, and a secure link. Do not send a link that expires before the user has finished reading the message.

Accessibility matters here too. A PDF-only receipt is not much help if someone uses a screen reader and the PDF is an image. An HTML receipt with proper headings and selectable text is often kinder. And if the user is offline, the app should still show the last confirmed purchase details from local storage rather than an empty screen and a spinning loader.

Offline proof is part of the product

Mobile life is intermittent. A user may need to show a receipt at a till, on a train, in a basement café or at an airport gate. If your receipt lives only behind a network request, it disappears exactly when it is needed.

A simple local cache of recent purchases, clearly labelled with the date it was last updated, can be enough. Add a “download” option that works once the document has been fetched. And make sure the order history does not silently lose older purchases when the app is reinstalled or the user switches devices. If account recovery is required, the receipt should come back with it.

Refund wording should reduce anxiety, not create it

Refund wording is where many apps sound either defensive or vague. “All sales final” may feel efficient, but it can clash with UK consumer expectations and it does little to build trust. A better receipt explains the route in plain English: how to request a refund, where to find the relevant terms, what information to include, and roughly how long a response takes.

If your app sells digital content or subscriptions, be careful with cancellation language. Users should be able to see what they bought, when it renews and how to stop it without hunting through account settings. The receipt does not need to be a legal essay, but it should not leave people guessing. A short “Need help with this order?” link with the order reference pre-filled is worth more than a paragraph of policy text.

A pre-launch proof-of-purchase audit

Before you ship, run through the journey as a customer would — not as the person who knows where everything lives.

• Buy something on a real device, using a real payment method, and check what appears on the success screen.
• Find the same purchase in the account area after closing the app and reopening it.
• Turn off mobile data and Wi-Fi. Can you still see the receipt you just downloaded?
• Open the email on a phone and on a desktop. Does the layout hold up? Is the order reference easy to copy?
• Request a VAT invoice as a business customer. How many steps does it take?
• Try the resend receipt option. Does it arrive, and does the link still work the next day?
• Read the refund wording out loud. Does it sound like a human wrote it?
• Test with a screen reader or large text enabled. Is the receipt still usable?

None of this is glamorous. But proof of purchase is one of the few parts of your app that people return to after the excitement has gone. Treat it as a trust document, not a transaction log, and you will spend less time answering “where is my receipt?” and more time earning the repeat purchase.