Transactional Email Examples and Templates: Order Confirmation, Receipt, Password Reset and More

Good transactional emails are plain, fast and specific. They tell people what happened, what to do next and how to get help, and they do it in a few lines. Bad ones bury the key fact under a banner, hide the link in a block of small print or read like a legal notice. This guide gives you examples and templates for the transactional messages almost every product needs: account verification, password reset, order confirmation, payment receipt, invoice, shipping notice, failed payment, security alert and support acknowledgement. For each, it explains what to include, suggests subject lines and gives sample wording you can adapt. It also covers design rules for transactional templates, what to leave out and how the legal rules treat messages that mix transactional and promotional content. For the definition and background, start with what a transactional email is.

Principles for every transactional template

• Subject line states the event. "Your order 10482 is confirmed", not "Great news!".
• Put the key information first. Order number, amount, date or the code itself.
• Keep it short. People scan these messages looking for one thing.
• Use the recipient's name and real data from your system, with safe fallbacks if a field is empty.
• Give a way to get help, with a real reply address or a support link. Avoid dead ends; see the no-reply address guide.
• Make the sender recognisable. A consistent sender name and a dedicated subdomain build trust.
• Send a plain-text version alongside HTML.
• Keep marketing out, or confine it to a clearly separate, minimal line, subject to the legal notes below.

Examples and templates

1. Account verification

Subject: Confirm your email address for Example

Hi Priya,

Please confirm your email address to finish creating your Example account.

[Confirm email address]

This link works for 24 hours. If you did not create an account, you can ignore this message.

Include an expiry, and say what happens if the person did nothing. If you use a code instead of a link, show it in large type and state how long it is valid.

2. Password reset

Subject: Reset your Example password

Hi Priya,

We received a request to reset the password for your account. Use the button below to choose a new password.

[Reset password]

This link expires in 60 minutes and can be used once. If you did not ask for this, ignore this message; your password will not change.

Security details matter here: short expiry, single use and no sensitive data in the message. Our guide to password reset email best practices covers token design and magic links.

3. Order confirmation

Subject: Your order 10482 is confirmed

Thank you for your order, Priya.

Order number: 10482
Date: 12 October 2026
Total: 2,499.00 INR

Items: 1 x Desk lamp, 1 x USB cable

Delivery to: 12 Example Street, Jaipur

We will email you again when it ships. Questions? Reply to this message or visit our help page.

4. Payment receipt or invoice

Subject: Receipt for your payment of 1,200.00 INR

Hi Priya,

We received your payment. Details are below and a PDF copy is attached.

Invoice: INV-2026-0188
Amount paid: 1,200.00 INR
Payment method: card ending 4242
Date: 14 October 2026

Show only the last digits of a card, never the full number. Keep attachments small; see email attachment size limits and consider a download link instead.

5. Shipping notice

Subject: Your order 10482 has shipped

Good news, Priya. Your order is on its way.

Carrier: Example Courier
Tracking number: EX123456789
Expected delivery: 16 to 18 October

[Track your parcel]

6. Failed payment or subscription renewal

Subject: Action needed: your payment did not go through

Hi Priya,

We could not process your payment for the Example plan. Your service continues until 20 October. Please update your payment method to avoid interruption.

[Update payment method]

Be calm and specific. State the consequence and the date. Do not use scare language.

7. Security alert

Subject: New sign-in to your Example account

We noticed a sign-in to your account on 14 October 2026 at 10:42 from a new device (Chrome on Windows, near Jaipur).

If this was you, no action is needed. If not, secure your account now.

[Review account activity]

Users are trained to be suspicious of such alerts because phishing copies them. Link only to your own domain, never use a shortened link, and tell users they can go to the site directly. See how to spot a phishing email.

8. Support ticket acknowledgement

Subject: We received your request (ticket 7731)

Hi Priya,

Thanks for contacting us. We have opened ticket 7731 and a member of our team will reply by email. You can add more details by replying to this message.

Design rules for transactional templates

• Use a single column and a width of around 600 pixels so it reads well on phones. See HTML email templates.
• Keep the logo small and the layout light. Heavy graphics slow loading and look like marketing.
• Use real text for key facts, so the message works with images blocked.
• Make buttons large enough to tap and add a plain link below them. See links and buttons in HTML email.
• Check contrast, dark mode and screen reader behaviour. See accessible HTML email.
• Store templates centrally with variables and versions. See email templates.

Transactional versus promotional content

It is tempting to add a banner to the receipt, because everyone opens receipts. Be careful. In the United States, CAN-SPAM looks at the primary purpose of a message; a message with both transactional content and commercial content is treated according to the overall impression, and the transactional part should come first. Other regions have different rules. Beyond the law, promotions in security and billing messages reduce trust and can raise complaint rates that harm delivery of critical mail. If you want to promote something, send a separate marketing message to people who agreed to receive it, through a separate stream. See separating transactional and marketing streams. This is general information, not legal advice.

Localisation and tone

If you serve customers in more than one language, translate the whole message, including the subject line and the button label, and pick the language from the account setting, not from the browser that happened to trigger the event. Format dates, currencies and addresses for the recipient's region. Keep the tone calm and direct in every language; transactional messages are not the place for jokes or slang, especially for payment problems and security alerts.

Testing checklist

1. Send each template to Gmail, Outlook, Yahoo and a mobile app.
2. Check with images off and in dark mode.
3. Test with long names, missing fields and non-English characters.
4. Confirm links work and expire as designed.
5. Inspect headers for SPF, DKIM and DMARC results.
6. Verify the plain-text version.
7. Use a staging environment so tests never reach customers. See the staging guide.

References and further reading

• FTC: CAN-SPAM Act compliance guide for business
• W3C Web Content Accessibility Guidelines (WCAG) 2.2
• RFC 5322: Internet Message Format