Your customers hear from you after every purchase, renewal, refund and failed payment. Until now the only payment emails Flopay sent them were a receipt and a payment-failed notice. Every customer email Flopay sends is now laid out in your brand, you decide which ones go out and what they say, and replies come straight to you.
Check your switches first
Every email type has its own on/off switch in Settings → Emails → Email templates.
- New clients start with every email switched on, so customers get the full set with no setup. Abandoned-cart reminders are the exception: they wait until you turn them on.
- Existing clients start with every new email switched off, so nothing new reaches your customers until you have looked at it. A receipt or payment-failed notice you already had on keeps its earlier setting.
Until you confirm you have reviewed your emails, the Emails pages show a prompt, and the setup checklist on Overview lists the review as a step. An email you switch off is not sent, but its webhooks still fire, and the email log records it as skipped so you can tell it apart from a delivery problem.
The emails Flopay sends for you
- Order confirmation for a checkout purchase, including a one-click upsell, in place of the receipt.
- Payment receipt for renewals and every other paid invoice.
- Subscription activation, with the plan, billing cycle, next renewal and any trial terms.
- Cancellation confirmation, with the plan and the cancellation date.
- Refund confirmation, with the refunded amount, and the original amount for a partial refund.
- Payment declined when a payment fails while your customer is not on your checkout: a one-click upsell on Stripe, PayPal or Worldpay, an invoice payment, a payment capture, or a payment created through the API. A decline the customer already sees on your checkout sends nothing.
- Failed renewal emails at the first failure, at each failed retry, and when retries end. They follow your dunning policy's retry schedule and each has its own switch.
- Renewal reminder, by default 7 days before a renewal on plans billed every 3 months or longer, and trial ending, by default 3 days before a trial's first paid charge. You choose how many days ahead.
The payment declined and failed renewal emails carry a button to your hosted manage page, where the customer updates their payment details. Security emails, such as one-time sign-in codes, are always sent.
Edit every email
Open any email in Settings → Emails → Email templates to change its subject, preheader, heading, paragraphs, button label and footer, or replace the whole body with your own HTML. Insert variables, such as the customer's name or the order total, from a picker.
Every change starts as a draft, so nothing your customers receive changes until you publish:
- Preview the draft with sample data, or with the payment, subscription or checkout behind your most recent email of that type.
- Send a test to any address. Tests come from the same sender as your customer emails.
- Publish. Flopay checks the email first, and shows any problem next to the field it concerns.
Build an email from blocks
Prefer to lay an email out yourself without writing HTML? Switch the editor to Blocks, next to Slots and Custom HTML. Add headings, paragraphs, buttons, images and dividers, edit each one's text or link, and drag blocks into order, or use Move up, Move down and Delete. Flopay's footer stays as a locked last row. Switching from Slots carries over your heading, paragraphs, button and footer, so you don't start from an empty email. An email built from blocks previews, tests and publishes like any other, and it reopens in Blocks next time.
Reset to default puts back Flopay's default email. Each email keeps a version history: open any published version read-only, or restore it as a draft to review and publish again. When Flopay improves a default you have edited, a notice shows what changed, slot by slot, and your email stays as it is.
Emails in your customers' languages
Selling in several languages? Keep a language variant of any email. On the email's edit screen, the Language switcher lists Default and every language you have added. Add language takes a tag such as fr-CA or de, and each language has the same editor, preview, test send, publish and version history as Default. Remove language sends customers with that language the default email again, and keeps its versions in case you add it back.
Set a locale on each customer through the API. Flopay sends the variant published for the customer's locale, then one for the same language, then your default email. Customers with no locale get your default email, as they do today.
Send from your own domain
By default your emails come from no-reply@flopay.com under your brand name, shown as "Your Brand via Flopay", and replies go to your Reply-To address. This is a complete setup and needs nothing at your DNS host. Your Reply-To is one address: set it once in Settings → Emails → Sender and every customer email uses it.
To send from your own domain, add a subdomain such as mail.shop.com and publish the four NS records the Sender page shows. Flopay hosts that subdomain and manages every record mail needs inside it, so you never change your DNS again. Once it is verified, emails come from an address such as billing@mail.shop.com. A red notice appears only while a domain is waiting for verification or has stopped working, and mail goes from the default sender in the meantime.
Abandoned-cart reminders, rolling out now
Abandoned-cart reminders bring back buyers who leave your checkout without paying:
- Send up to three reminders, each with its own delay, from the step editor on the abandoned-cart email.
- The series stays off until you turn it on and confirm that your customers have agreed to receive marketing emails.
- Every reminder links back to the buyer's cart on a checkout page in your brand, and carries a one-click unsubscribe.
- Reminders stop once the buyer pays you or unsubscribes.
Abandoned cart is the only Flopay email with an unsubscribe link. Every other email is service mail about a purchase or a subscription.
You can also turn on open and click tracking for your abandoned-cart emails. It is off by default, and no other email is ever tracked. Flopay keeps only when an email was first opened or clicked and how many times, never the IP address, location, device or the link clicked.
See what was sent, and what it earned
Settings → Emails lists every email Flopay sent or tried to send for you, newest first, with its type, recipient, time and status: queued, sent, delivered, bounced, complained, suppressed or skipped. Filter it by status, type, recipient or date, and open the payment, subscription or checkout session each email is about.
When an address hard bounces or its owner reports an email as spam, Flopay adds it to your suppression list and stops emailing it.
The Recovered revenue page in Settings → Emails totals the payments your failed renewal and abandoned-cart emails brought back, by email type, abandoned-cart step, currency and period. A payment is credited once, to the newest of those emails sent in the 7 days before it.
A guided setup
Client owners and admins see a Set up your account checklist on Overview: your brand, a payment gateway, your Reply-To, an optional sender domain, and the review of your emails. Start setup walks you through each step in turn.
For your developers
- Webhooks:
checkout_session.abandonedcarries the buyer's email, the cart and a link that brings the cart back.subscription.renewal_upcomingandsubscription.trial_will_endcarry the charge date, amount and the customer's manage link.email.sent,email.bouncedandemail.complainedkeep your systems in step with every email. These webhooks fire whether or not the matching email is switched on. - API and MCP: templates, switches and settings, the sender domain, the email log, the suppression list and the recovered revenue report are all in the Flopay API, and each is also an MCP tool for FloBot or your own assistant. An assistant asks you to confirm every change.
Read the Emails guide for how templates, variables, switches and sender domains work, the Emails API reference for every endpoint, and the email MCP tools.