## Overview

For revenue that repeats (memberships, service plans, retainers), use **subscriptions**. You set the
amount and the **cycle** (weekly, monthly, yearly, etc.), and the gateway generates the recurring
charges automatically. ConversaLabs mirrors each generated charge and the subscription state (active,
paused, canceled), and feeds the **MRR** and **churn** indicators in the reports.

On Mercado Pago you can also use reusable **plans** (a subscription template that serves many
customers). On Asaas, recurrence is configured directly on the subscription.

## Prerequisites

- A **connected** gateway that supports subscriptions (both Asaas and Mercado Pago do).
- For **reusable plans**, use **Mercado Pago** (Asaas does not expose plans as a separate entity).
- A contact/customer with valid data on the gateway.

## Step by step

1. In the Payments area, choose to create a **subscription**.
2. Pick the **gateway** (the connection) and the customer (contact).
3. Set the **amount** and the billing **cycle** (for example, monthly).
4. Set the **next charge date** and the method (PIX, boleto or card, depending on the gateway).
5. (Optional, Mercado Pago) Link it to an existing **plan**.
6. Save. The gateway starts generating charges on the defined cycle.
7. Track each generated charge and the subscription state on the platform; the customer receives the
   charge as usual.

## Settings & options

- **Cycle**: weekly, biweekly, monthly, quarterly, semiannual or yearly (the exact offering depends
  on the gateway).
- **Subscription state**: active, paused, canceled — reflected from the gateway's notifications.
- **Plans (Mercado Pago)**: create a plan once and reuse it across many subscriptions.
- **Cancellation**: cancel the subscription on the platform; the gateway stops future charges.
- **Generated charges**: each cycle becomes a mirrored charge with its own status.

## Use cases

- Monthly fee for a subscription service.
- Recurring support or consulting plan (retainer).
- Content club/subscription with automatic renewal.

## Tips, limits & best practices

- Recurrence is **delegated to the gateway** — it generates and bills each cycle; the platform
  reflects the result.
- Use **plans** (Mercado Pago) when many customers subscribe to the same offer — it's easier to
  maintain.
- The reports' **MRR** normalizes each active subscription to an equivalent monthly amount; **churn**
  counts the ones canceled in the period.
- Communicate the cycle and amount clearly to the customer before activating the subscription.

## Troubleshooting

- **The next charge wasn't generated**: confirm the subscription state (it may be paused or canceled)
  and the webhook setup.
- **Plans don't appear**: reusable plans are a Mercado Pago feature; on Asaas configure recurrence on
  the subscription itself.
- **I canceled and it still charged**: check that the cancellation was confirmed by the gateway; the
  effect applies to future cycles.

## See also

- [Payments overview](/hc/ajuda/articles/payments-overview-en)
- [Connect a gateway: Asaas and Mercado Pago](/hc/ajuda/articles/payments-conectar-gateway-en)
- [Create a charge and send it in the conversation](/hc/ajuda/articles/payments-criar-cobranca-enviar-na-conversa-en)
- [Discounts and value adjustment](/hc/ajuda/articles/payments-descontos-en)
- [Refunds, webhooks and reports](/hc/ajuda/articles/payments-reembolsos-webhooks-relatorios-en)