Subscriptions
Recurring revenue, on autopilot.
Automate payments, reduce failed transactions, and get repeat revenue — without chasing invoices. Subscription payments have two parts: a recurring payment item, such as a gym membership, and a customer's subscription to it.
A subscription is a billing schedule: how often to charge (weekly, monthly or annually), how many intervals between charges, and when to start and stop. On its own it charges nobody. Customers sign up by paying a payment link that the subscription is attached to; each customer who does becomes a subscriber, and Mamo charges their saved card on every billing date.
How it fits together
- Create the schedule with Create subscription.
- Attach it to a payment link by passing its identifier as
subscription_idto Create payment link, withlink_typeset toinline. - The customer pays the link. That first payment signs them up and saves their card.
- Mamo charges them on schedule. You get a
subscription.succeededorsubscription.failedwebhook for every renewal.
Managing subscriptions
| You want to | Use |
|---|---|
| See who's subscribed | Fetch subscribers |
| See every renewal payment | Fetch subscription payments |
| Move a subscriber to another plan | Change customer subscription |
| Stop billing one customer | Unsubscribe subscriber |
| Retire the whole plan | Cancel subscription |
Unsubscribe vs. cancelUnsubscribing stops billing for one subscriber. Cancelling deactivates the subscription itself: its payment link is switched off so no one can sign up again, and every active subscriber is unsubscribed. The record is kept.
The Subscription object page describes the subscription webhook payload field by field.
Build it
The Subscriptions section of the API Reference has every subscription endpoint.
Try it
Follow the Bill a customer every month recipe in the sandbox.
Updated 5 days ago