Skip to main content
Use Stripe when billing or customer lifecycle context should help Migma prepare email work. Stripe is different from a sending provider. It gives Migma context such as customer, subscription, invoice, payment, or failed-payment state. Migma still sends through Migma sending or a connected delivery provider.

​
What you can use Stripe for

Lifecycle email ideas

Prepare onboarding, payment, invoice, renewal, failed-payment, or win-back email flows.

Customer context

Use Stripe customer or subscription context when shaping email content.

Agent setup

Let an agent use Stripe app context when starting Migma setup work.

Delivery stays separate

Send through Migma, Amazon SES, Resend, SendGrid, or Mailgun.

​
Common workflows

Stripe contextEmail work Migma can prepare
CustomerWelcome, onboarding, lifecycle, or account-update email.
SubscriptionTrial, renewal, upgrade, downgrade, cancellation, or win-back sequence.
PaymentReceipt follow-up, payment confirmation, or payment issue email.
InvoiceInvoice reminder, payment due, or failed-payment recovery.

​
Best practices

  • Keep payment and customer data private.
  • Review generated content before sending.
  • Do not invent billing details that are not present in Stripe context.
  • Use verified sending domains or a connected delivery provider before launch.

Lifecycle Email Recipes

Prompt patterns for lifecycle and revenue emails.

Email Service Providers

Choose how Migma sends the finished email.