#the correct way to handle subscriptions

1 messages · Page 1 of 1 (latest)

near chasm
#

Hello Mollie Community,
I am currently working on developing an app that will offer subscription-based services to users. I am looking to integrate Mollie as the payment gateway for handling these subscriptions. Can anyone share their experience or knowledge on the best way to set up Mollie for this purpose? Any tips or examples of how to handle the subscription flow through Mollie would be greatly appreciated. Thank you!

ruby remnant
#

Hmmm so basically there are two core ways of approaching it.
a. Use our subscriptions API. This will automagically handle renewal payments and such. I would only suggest using this if you do not want to build a large amount of backend logic and your product is relatively simple (no variable fees)
b. Use the sequenceType:recurring in the payments or orders api. This will allow for more control and on demand charges.

In either case you need to create customers (via the customer API) and mandates (either via sequenceType:first payments or the mandates API (SDD only))

You can find quite comprehensive documentation on the topic here: https://docs.mollie.com/payments/recurring

ruby remnant
#

oh yes, i can confirm what Tim says.

so my experience and what I did.
I did a huge integration in the shopware 6 plugin, as well as custom integration in my private project.

so 2 options to go with indeed...either store mandate ID and charge on your own in cronjob, or use the mollie subscription and let them schedule. if its your system, then i would do it with the cronjob approach.
i have the same thing. you need to do the scheduling, but you are super free when it comes to being flexible on what to charge.
short concept -> create first payment, store the mandateId on successful payments in the subscription table. and then simply create cronjob that charge