Build the payment message in Migma after your billing owner has defined what the event proves. A checkout attempt, a pending payment, and a completed payment can require different wording. A receipt-shaped email should not tell a customer that money was received when the underlying record has not established that result.
This Migma-published guide is for SaaS teams preparing payment creative for Loops or another transactional sending workflow. It concerns message accuracy and review ownership. It does not prescribe payment processing, accounting, tax treatment, or platform-specific status mappings. Official example sources were inspected on October 27, 2026.
Write down the fact you can confirm
Ask the billing owner for the accepted event definition and a representative test record. What exactly happened? Which account, amount, currency, and billing period does it concern? Is the event final enough to support the word “paid,” or does it only confirm that a request was received?
Loops’ payment confirmation examples highlight the reader’s need to understand a charge and find the associated billing information. Use that problem as the starting point. Do not copy a historical receipt’s renewal terms, plan prices, or payment-method description.
Keep payment state and account access separate. Your service may have its own rules for enabling a plan, and those rules need an owner. The designer should not infer successful activation merely because an email event contains a plan name.
Give each state its own message purpose
A short decision record prevents contradictory copy:
| Accepted fact | Message job | Claim to avoid without evidence |
|---|---|---|
| A request was submitted | Acknowledge the request | Payment received |
| The owner confirms a pending state | Explain the pending status | Your receipt is ready |
| The owner confirms successful payment | Confirm the payment details | All account changes completed |
| The owner confirms a refund | Explain the accepted refund facts | Funds already visible at the bank |
These rows are editorial distinctions, not a universal financial-status model. The billing owner must map the actual provider events and decide which are appropriate to communicate.
An original fictional example makes the issue concrete. A team receives a checkout submission for an annual plan, but the payment is still being processed. The email can acknowledge that submission under the approved workflow. It should not silently inherit “Thanks, we received your payment” from a successful-payment template.
Prepare clear billing creative in Migma
Migma keeps copy, links, buttons, and layout editable. Use that flexibility to make the accepted status prominent in live text. Keep decorative artwork secondary to the account context and the reader’s next step.
For a confirmed payment, ask the owner which approved fields belong in the message. These might include the amount and currency, payment date, plan or product, billing period, and a useful reference. Include only what the actual record supports.
Do not invent card details or expose more billing information than the message needs. Use approved sample records in the design process. Keep private customer payment information out of public screenshots or reusable creative references.
If the email links to billing history or a receipt, use wording that accurately describes the destination. “View billing” is different from “Download receipt.” Test the intended action instead of selecting a familiar label.
Review changes as separate facts
A payment can coincide with a plan change, seat change, renewal, or refund, but one fact does not automatically prove all the others. Ask the owner which state the application has accepted before combining them in one sentence.
When a billing period appears, check both endpoints and the account context. A workspace owner managing several subscriptions needs to know which one the message concerns. Avoid a generic “your account” if that would obscure the relevant workspace.
Renewal and cancellation wording must come from the approved billing policy. Do not let an AI draft infer future renewal dates or cancellation conditions from the shape of a receipt. Have the responsible reviewer approve those sentences directly.
Verify the populated email and billing destination
In a Loops or other transactional handoff, provide the final Migma creative, the accepted event definition, and sample values for each supported state. The sending owner must verify how those values reach the message. A template name is not proof that it is attached to the right event.
Check the amount, currency, account, dates, reference, and destination in the populated preview. Test a missing optional value. The result should remain clear without presenting an empty label as a completed fact.
Open the billing link using an authorized test account. Confirm that it reaches the right account and that its status agrees with the email. Include a supported route for payment questions and verify that the team receiving those questions can investigate the reference provided.
Keep the release record small and useful
Run Migma Email Preflight, resolve relevant findings, and rerun after edits. It can help with previews, links, and writing. It cannot determine whether a transaction completed or guarantee inbox placement.
Record the approved message version, accepted billing event, reviewed sample, and final sending-platform preview. Preserve the distinction between successful preview, authorized test delivery, and production billing behavior.
Use Migma to present payment information clearly, then let verified billing facts govern every sentence that says what the customer paid or what will happen next.
Frequently Asked Questions
Can a checkout submission be called a successful payment?
Only the accepted billing record can support that claim. Ask the billing owner what the actual event establishes before using payment received or receipt wording.
Does payment success prove that a plan change completed?
Do not infer one from the other. The billing and product owners must confirm which account changes occurred before the message combines them.
Which payment details should the email include?
Use approved fields supported by the actual record, such as amount, currency, account, date, billing period, and a useful reference. Avoid unnecessary private billing information.
Can Preflight confirm the transaction completed?
No. Migma Preflight helps review previews, links, writing, and common sending risks. The billing owner must verify transaction state and the populated message.