Payment Receipt Email Template for Confirmation and Records
A receipt answers “what just happened?” quickly. It is different from a payment-failed notice, an invoice, or a renewal reminder, so the trigger must be a settled payment event.
Trigger contract
Send after the payment provider or ledger confirms the status your product calls paid. A temporary authorization, pending payment, or client-side success screen is not enough.
| Field | Example | Rule |
|---|---|---|
| Payment ID | pay_123 | Stable reference for support |
| Invoice ID | INV-1042 | Link to the accounting record |
| Amount and currency | $49.00 USD | Use settled amount |
| Paid timestamp | 2026-07-24 14:05 UTC | Format for recipient locale |
| Payment method | Visa ending in 4242 | Last four only |
| Account or order | Acme Analytics | Avoid ambiguous workspace names |
| Receipt URL | Secure portal link | Require authorization |
If the payment is later reversed or refunded, send a separate status message. Do not rewrite the original receipt as though it never existed.
Template
Subject: Payment received — {{amount}} for {{product_name}}
Preheader: Receipt {{receipt_number}} is ready.
Hello {{customer_name}},
We received your payment of {{amount}} for {{product_name}} on {{paid_date}}.
| Receipt | Details |
|---|---|
| Receipt number | {{receipt_number}} |
| Invoice or order | {{invoice_number_or_order}} |
| Payment method | {{payment_method_summary}} |
| Amount | {{amount}} |
[View receipt]
Keep this email for your records. Questions? Contact {{support_email}} and include receipt {{receipt_number}}.
{{company_name}}
Variants
- Subscription renewal: name the plan and renewal period.
- One-time order: include order reference and fulfillment link.
- Partial payment: show remaining balance and next due date.
- Tax invoice: link to the legally required document.
- Refund: use “refund issued” and state expected settlement timing.
Keep promotional recommendations out of the primary receipt body. If the product includes optional cross-sell content, separate it visually and ensure the receipt remains understandable without it.
Reliability and deduplication
Use payment ID and receipt version as the idempotency key. A provider webhook may be retried; only the first settled transition should trigger the receipt. If a payment changes from pending to paid later, send once when the ledger confirms it.
QA checklist
- Pending payments do not send receipts.
- Amount, currency, tax, and timestamp match the source.
- The last four digits are correct and no sensitive credentials appear.
- Refunded and reversed states have separate templates.
- The receipt link works for the intended billing contact.
- The message is readable in plain text and on mobile.
Pair this with the invoice template and payment-method update template.
Receipts for real-world edge cases
For a partial payment, show both the amount received and the remaining balance. For a refund, use a separate subject and state whether the refund is initiated or settled. For a subscription renewal, include the service period and plan so the receipt is useful to finance and the customer.
If the payment is pending, send a pending-payment message or wait for settlement. A receipt that later becomes a failed charge creates avoidable support work.
Record retention and accessibility
Keep the receipt number searchable in the subject and body. Use a text table or labeled facts rather than an image-only invoice. Ensure the portal link is accessible to the billing contact and that a plain-text version carries the same amount, currency, and reference.
Track delivery, receipt access, refund follow-up, and duplicate-send rate. The goal is a trustworthy record, not a promotional click.