Subscriptions
Migo runs recurring billing for your merchant. You define the price and the cadence; Migo hosts the checkout, stores the card, creates the subscription when the customer pays, and runs the charge at every renewal, notifying your backend by callback at every event.
You never touch card data, and you don't need PCI scope.
The whole journey, in four stepsβ
1. You create the PLAN POST /api/v1/plans
(how much, how often) β
βΌ
2. You generate the PAYMENT LINK POST /transactions
from that plan (customKeys.plan.uid)
β β returns the checkout URL
βΌ
3. Your customer PAYS at checkout (webview hosted by Migo)
β Migo creates the SUBSCRIPTION automatically
β β callback to your backend
βΌ
4. Migo CHARGES on every renewal (automatic, no code of yours)
β callback on every charge
You make one call per sale (step 2). Steps 3 and 4 are executed by Migo.
Integration routesβ
AI agent guide
A self-contained document you hand to your AI assistant so it implements the integration β one-time payments and subscriptions β with a verification for every step.
Integration in 4 steps
The same journey, written for a human: the four calls in order, with real
curl commands and what to verify before moving on.
Referenceβ
| Page | What it solves |
|---|---|
| Plans | Create, list, read and update plans β the price and the cadence |
| Subscription payment link | Turn a plan into a checkout URL you can send by email, WhatsApp or SMS |
| Subscriptions | Read, list, update and cancel; the four states and their transitions |
| Subscription callback | How Migo tells you about every signup, charge and cancellation; it is your source of truth |
| Charges | Automatic billing on renewal, variable-amount charges (JSON and CSV) and payment history |
| Payment methods | Stored cards: add, change the default, delete |
| FAQ | The real limits of the API: what you can do, what you can't, and the workaround |
Before you startβ
You need three values from your account, provided by Migo:
| Value | What it's for |
|---|---|
| Merchant token | Authenticating every call |
client (slug) | Identifies your merchant on every request |
| Callback URL and secret | Where Migo notifies you, and how you verify the notice is really theirs |
Environments and base URLs are in Environments & Base URLs. Always start in sandbox.