Recurring payments can be used to charge customers on a regular basis or to offer automatic top-ups with credits-based services. Since the amount for a recurring payment is variable, other innovative use-cases are possible as well. Like doing a partial prepayment and later a final recurring payment, for more expensive products. Or charging a customer in your Dashboard manually, for orders by phone.
Recurring payments happen in the background. The customer goes through the payment steps only once, for the first payment.
Reducing the risk of chargebacks
To reduce the risk of chargebacks, it's recommended to communicate how often and how much the customer will be charged as clearly as possible. We suggest notifying the customer a couple of days in advance of the next payment, for example by sending them an email.
How to get started
In the following sections we explain the following topics.
- :ref:`Setting up the first payment <payments/recurring/first-payment>`
- :ref:`Charging immediately on-demand <payments/recurring/charging-on-demand>`
- :ref:`Charging periodically with subscriptions <payments/recurring/charging-periodically>`
- :ref:`How do webhooks for subscriptions work? <payments/recurring/subscription-webhooks>`
For more information on how to test recurring payments, please refer to our :doc:`guide </guides/testing>` for testing the Mollie API.
Setting up the first payment
In order to get started with recurring payments you need to require the customer's consent through a first payment. It's similar to a regular payment, but the customer is shown information about your organization, and the customer needs to complete the payment with the account or card that will be used for recurring charges in the future. After the first payment is completed successfully, the customer's account or card will immediately be chargeable on-demand, or periodically through subscriptions.
- Create a unique customer using the :doc:`Customers API </reference/v2/customers-api/create-customer>`.
- Save the customer's
idin your database. You need it when performing :doc:`Payments API </reference/v2/payments-api/create-payment>` calls.
- Create a payment for the customer by specifying the
customerIdand setting the
- Redirect the customer to the
_links.checkout.urlto complete the first payment. Make sure to use an HTTP
- Once completed there will be a customer mandate that you can access via the :doc:`Mandates API </reference/v2/mandates-api/get-mandate>`.
Not all payment methods support a first payment. When the
method parameter is not provided in the API, we
take care of this automatically in our :doc:`Checkout </guides/checkout>`. The following payment methods
support a first payment and are thus allowed as a value for the
method parameter of a first payment:
Charging immediately on-demand
Now that the customer has given their consent, it's possible to perform a recurring payment on-demand. Instead of the
regular payment with a
redirectUrl, a recurring payment happens in the background without a browser session, i.e.
without the customer going through payments steps. You can create a recurring payment with the
sequenceType set to
recurring when creating a payment with the :doc:`Payments API </reference/v2/payments-api/create-payment>`.
Please note that in order to do recurring payments, direct debit or credit card has to be activated on your profile.
- Make sure the customer has valid mandates. Find out using the :doc:`Mandates API </reference/v2/mandates-api/list-mandates>`.
- If there's at least one mandate with a
- Set the
recurringto charge the customer on-demand.
- Like regular payments your :doc:`webhook </guides/webhooks>` is called for retrieving status updates.
Charging periodically with subscriptions
For simple regular recurring payments with constant amounts, you can create subscriptions with the :doc:`Subscriptions API </reference/v2/subscriptions-api/create-subscription>`. Subscription payments will be spawned automatically at the specified frequency, and will show up in your Dashboard.
- Make sure the customer has a pending or valid mandate using the :doc:`Mandates API </reference/v2/mandates-api/list-mandates>`.
- Continue if there's a mandate with its
valid, otherwise set up a first payment for the customer first.
- Create the subscription using the :doc:`Subscriptions API </reference/v2/subscriptions-api/create-subscription>`.
- In the above example the customer is charged €25.00 for 4 times every 3 months, starting today.
- The webhook URL will be triggered for every payment to communicate any status updates.
Refer to the documentation of the API client you are using for more examples.
How do webhooks for subscriptions work?
When using our Subscriptions API to charge a customer periodically, new payments are created by Mollie every time the customer is charged. We will call your webhook as usual for these payments. The only difference is, the payment ID will not be known by your system yet when we call the webhook to report the payment's status.
With normal payments you know the payment ID, because you've received this when creating the payment. With subscriptions you don't know the payment ID in advance. So you'll receive a webhook call with a payment ID that you've never seen before.
The payment object will, however, contain a
subscriptionId field that contains the subscription ID you received when
the subscription was created. This allows you to recognize where the payment belongs to.
We do not provide webhooks specifically for status changes of a Subscription itself.