Subscriptions and recurring plans

Open in

View as Markdown

Open in ChatGPT Open in Claude

Conversa Labs

Last updated on Aug 12, 2026

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. Conversa Labs mirrors each generated charge and the subscription state (active, paused, canceled), and feeds the MRR and churn indicators in the reports.

You can also use reusable local plans: they store connection, amount, currency, and cycle for many subscribers. When each subscription is created, the platform sends the recurrence to the gateway; a local plan does not mean a plan entity already exists in the gateway dashboard.

Prerequisites

A connected gateway that supports subscriptions (both Asaas and Mercado Pago do).
To use a reusable plan, keep its linked connection active. The plan currency must match that connection's settlement currency.
A contact/customer with valid data on the gateway.

Step by step

In the Payments area, choose to create a subscription.
Pick the gateway (the connection) and the customer (contact).
Set the amount and the billing cycle (for example, monthly).
Set the next charge date and the method (PIX, boleto or card, depending on the gateway).
(Optional, Asaas) Set a maximum number of charges or an end date. The every-two-months cycle also appears when the connection supports it.
(Optional) Select a local plan. Connection, amount, currency, and cycle are filled and locked so the subscription remains consistent with the chosen template.
Save. The gateway starts generating charges on the defined cycle.
Track each generated charge and the subscription state on the platform; the customer receives the charge as usual.

Settings & options

Cycle: weekly, biweekly, monthly, every two months (Asaas), quarterly, semiannual or yearly. The screen shows only cycles supported by the connection.
Asaas limits: maximum number of charges stops after a number of cycles; end date stops at the chosen boundary and cannot be before the first charge. You can also adjust the end date later under Edit subscription; the maximum number of charges is set at creation.
A subscription is not an installment plan: the gateway bills the amount once per cycle. To split one purchase into installments, create a one-off card charge.
Subscription state: active, paused, canceled — reflected from the gateway's notifications.
Local plans: create a template once and reuse it across compatible subscriptions. The gateway still receives and runs each individual subscription.
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

If the network fails during creation, retry without closing the form: the same operation resumes, and an uncertain gateway response never blindly creates another subscription.
Recurrence is delegated to the gateway — it generates and bills each cycle; the platform reflects the result.
Use local plans when many customers subscribe to the same offer — it keeps connection, price, currency, and cycle consistent.
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: confirm that the plan is not archived, its connection is active and supports subscriptions, and its currency matches the settlement currency.
I canceled and it still charged: check that the cancellation was confirmed by the gateway; the effect applies to future cycles.