Payment Confirmation Email Template — Amount at Display Scale
A precise payment-receipt email with the charged amount at display scale in the layout hero and clear transaction details. Designed for SaaS billing.
Preview unavailable — view the prompt below.
The prompt
Two ways to build this email in plain language. The fastest is Temway's in-editor assistant — open the chat drawer in the email editor and paste the recipe below. Or connect Claude or ChatGPT via Temway's MCP and paste it there; the agent builds the email step by step. Either way, adapt the copy and colors to your brand.
- An email is a top-to-bottom stack of blocks — the recipe follows that order.
- A
[layout]step becomes a single image (great for heroes); everything else stays live text and links. - Theme the footer to match — the recipe's last step does exactly that.
Want this exact email? Click Use this template below to clone
it into your workspace, then ask the in-editor assistant to rebrand it. Over MCP, tell
your agent to clone the Temway share eJUoXy-JGutIY3LY5V6H9 and rebrand. For the
full model, point an MCP agent at get_concept — email-structure,
layouts-vs-emails, design-recipes.
A precise payment receipt that treats the charged amount as the hero. A quiet white layout shows the figure at 132px tabular-nums beside a kicker rule, then the native stack gives the timestamp, the card and reference, what the payment covers, an invoice download, and a fraud-prevention note — every detail a customer needs to recognise the charge.
Snapshot
- Goal: confirm a successful payment and let the customer download the invoice without friction.
- Audience & tone: customers who just paid. Plain, precise, reassuring — never marketing.
- Palette: page
#ecedee· container#ffffff· text#111827/#6c7079(muted) · accent#1e40af - Font:
Helvetica, Arial, sans-serif - Artwork: none — fully native blocks.
Build recipe
Each step is one block in the flat stack, top to bottom.
[native]= a real email block.[layout]= a free-form layout embedded as a single image.
- [native] Logo — logo. Brand mark, left-aligned.
- [native] Kicker 1 — text. “Payment confirmation”, fontSize: 14, color
#1e40af, left, uppercase. - [native] Headline — text. “84.00 GBP received”, fontSize: 28, color
#111827, left. - [native] Body copy 1 — text. “Confirmed on 12 March at 14:22 — the details are below.”, fontSize: 16, color
#111827, left. - [native] Kicker 2 — text. “Paid with”, fontSize: 14, color
#1e40af, left, uppercase. - [native] Body copy 2 — text. “Card ending 4242 · Merchant Northbound Ltd.”, fontSize: 16, color
#111827, left. - [native] Kicker 3 — text. “Reference”, fontSize: 14, color
#1e40af, left, uppercase. - [native] Body copy 3 — text. “PM-4821 — quote this in any reply; it is what a support team will ask for.”, fontSize: 16, color
#111827, left. - [native] Kicker 4 — text. “What this covers”, fontSize: 14, color
#1e40af, left, uppercase. - [native] Body copy 4 — text. “Subscription, 12 March to 11 April — the next charge lands 12 April.”, fontSize: 16, color
#111827, left. - [native] Primary CTA — button. Label “Download the invoice”, fill
#1e40af, color#ffffff, shapeStyle: ‘0_0’, left. - [native] Body copy 5 — text. “Do not recognise this charge? Reply within 30 days and quote the reference. We will never ask for your card number or a one-time code by email.”, fontSize: 16, color
#6c7079, left. - [native] Footer rule — divider. short (96px) rule, 1px, color
#e9e9e9. - [native] Footer social — social. Icon row, social.color
#1e40af, style circle-outline, center. - [native] Footer address — address. Postal address + unsubscribe, address.color
#6c7079, address.fontFamilyHelvetica, Arial, sans-serif, center.
Make it yours
- Swap the amount, currency, reference, card last-four, and date for the real transaction row.
- Keep the amount at display scale with tabular-nums — it is the one element customers scan for.
- Recolor the accent blue to your brand, but keep the dispute and security lines muted so they read as help, not alarm.
About transactional email templates
Transactional email gets the highest open rates of any category, because recipients expect and want it — an order confirmation or shipping update gets read almost every time it lands. That makes it a branding opportunity most teams under-invest in relative to promotional email.
See all transactional templates →Why bother designing a transactional email — isn't the information all that matters?
Transactional emails have the highest open rates of any email you send, because recipients expect and want them — that makes them a real branding opportunity most teams under-invest in relative to promotional email.
What information has to be in an order confirmation email?
Order number, itemized contents, total charged, and expected delivery or next steps at minimum — the order-summary template below leads with those before anything promotional.
Can I add an upsell or review request to a transactional template?
Yes, but keep it secondary — the templates below place the transactional information first and any cross-sell or review ask below the fold, so it never competes with the confirmation itself.
Do these transactional templates work for both order and account-related events?
Yes — the collection below covers order confirmations and shipping updates as well as payment receipts and return confirmations, so both commerce- and account-triggered sends are covered.