subscription_options are passed during a first_in_series payment session.
When the first payment succeeds, it acts as an authorisation and sets up the underlying mandates required for future charges. The subscription is then automatically activated and payments are collected according to the recurrence parameters defined at setup.
How it works
- Create a
first_in_seriespayment session withsubscription_optionsincluding the recurrence configuration. - The customer completes the first payment, authorising future charges.
- Moment sets up the required mandates and activates the subscription.
- Subsequent payments are collected automatically on the schedule defined by the
recurrenceparameters.
Webhooks
The Subscriptions API emits events to notify you of changes to a subscription’s lifecycle.| Event | Description |
|---|---|
subscription.created | Fired when a subscription is created and activated after a successful first payment. |
subscription.ended | Fired when a subscription reaches its end date and all scheduled payments have been collected. |
subscription.cancelled | Fired when a subscription is cancelled before reaching its end date. |

