> ## Documentation Index
> Fetch the complete documentation index at: https://docs.migma.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Stripe Integration

> Use Stripe customer, subscription, invoice, and payment context in Migma email workflows.

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

<CardGroup cols={2}>
  <Card title="Lifecycle email ideas" icon="arrows-right-left">
    Prepare onboarding, payment, invoice, renewal, failed-payment, or win-back email flows.
  </Card>

  <Card title="Customer context" icon="user">
    Use Stripe customer or subscription context when shaping email content.
  </Card>

  <Card title="Agent setup" icon="cpu-chip">
    Let an agent use Stripe app context when starting Migma setup work.
  </Card>

  <Card title="Delivery stays separate" icon="paper-plane">
    Send through Migma, Amazon SES, Resend, SendGrid, or Mailgun.
  </Card>
</CardGroup>

## Common workflows

| Stripe context | Email work Migma can prepare                                            |
| -------------- | ----------------------------------------------------------------------- |
| Customer       | Welcome, onboarding, lifecycle, or account-update email.                |
| Subscription   | Trial, renewal, upgrade, downgrade, cancellation, or win-back sequence. |
| Payment        | Receipt follow-up, payment confirmation, or payment issue email.        |
| Invoice        | Invoice 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.

## Related docs

<CardGroup cols={2}>
  <Card title="Lifecycle Email Recipes" icon="arrows-right-left" href="/recipes/lifecycle-emails">
    Prompt patterns for lifecycle and revenue emails.
  </Card>

  <Card title="Email Service Providers" icon="envelope" href="/integrations/email-service-providers">
    Choose how Migma sends the finished email.
  </Card>
</CardGroup>