less than a minute read • Updated 3 minutes ago
What is the web receipt?
An overview of what the web receipt is, why it matters for tracking and analytics, and how receipt URLs and privacy protection work.
The web receipt is the page customers land on immediately after a successful checkout. It displays the details of their completed transaction, and like the cart and checkout, it’s fully customizable using the same Twig templating system.
Why the receipt matters
It might seem like a page you’ll never need to touch, but the receipt is where several important things happen:
Analytics and goal funnel tracking — most conversion tracking scripts fire on the receipt, since it only loads after a successful purchase.
Affiliate sales tracking — affiliate programs typically confirm a sale from the receipt page.
Advertising and campaign tracking — ad platforms often use the receipt to record a completed conversion.
Downloadable product links — if a customer purchases a downloadable product, their download links appear on the receipt.
The receipt will generally contain nearly all the information about a transaction, with a few exceptions.
What’s included on the receipt
Downloadables — linked product names to download any digital products purchased.
General — the payment gateway/processor response, your store’s name, and the date and time.
Order — order ID, payment method (including last 4 digits and card type, if paying by card), subtotal, shipping total, tax total, and order total.
Billing address — first name, last name, address, country, email, and phone.
Shipping address (if different from billing) — first name, last name, address, country, email, and phone.
Shipping method (e.g. “FedEx Home Delivery”).
Custom fields included on the checkout.
What’s not included on the receipt
“Sensitive” custom checkout fields.
Session variables.
Credit card details (card number, CSC, expiration, issue date, etc.).
Where the receipt fits in the order flow
The full flow is: your site → the cart → the checkout → the transaction datafeed (if configured) → the receipt → back to your site.
It’s worth noting that the datafeed fires before the receipt loads — so by the time a customer sees their receipt, the datafeed has already been sent to your endpoint, if you have one configured.
You can also configure the “continue” link shown on the receipt — see the dedicated article on setting a custom continue link.
Receipt URLs and privacy protection
To prevent personally identifiable information on a receipt from being exposed on a shared or public computer, Foxy automatically converts the full receipt URL to simply /receipt after it first loads. This keeps a customer from reopening their own receipt just by hitting the browser’s back button.
This same protection can make development and testing harder, since reloading the page won’t show the receipt again. If you need to keep working with the full URL, see the dedicated article on revisiting a past receipt.
How the receipt relates to checkout and email receipts
The receipt is the last step in the Foxy purchase flow: cart → checkout → receipt. It shares the same Twig-based customization approach as the checkout, so if you’re already familiar with customizing your checkout template, the receipt will feel familiar.
Email receipts are closely related, but not identical — they include almost everything shown on the receipt, plus some additional sections that only appear in specific situations (such as a subscription cancellation).
Notes
You can find a completed transaction’s receipt URL from the “view” link in the transaction history in the Foxy admin.
For a full list of the variables available to your receipt template, see the web receipt template variables reference.