Take subscriptions in your apps

Your apps can sell what comes back: a weekly vegetable box, a monthly membership, a yearly licence. Subscriptions go through Mollie, with your organisation’s own Mollie account, like payments. The money goes straight to that account: kvyk.ai never holds it and takes nothing from it.

An Administrator first adds the Mollie connector and connects your Mollie account for Preview and for Live: see Mollie. In your Mollie dashboard, switch on SEPA Direct Debit or cards, which Mollie uses for the later charges. If Mollie was connected before subscriptions came to kvyk.ai, the connector asks you to Connect again first.

Ask the assistant for a subscription

Tell the assistant what people subscribe to, for example: “Let customers subscribe to the bread box for 12.50 euro a week, and let them cancel it on their account page.” It builds the subscription into your app. When someone subscribes:

1. The app sends them to Mollie’s payment page for the first payment. Paying it gives Mollie their permission to charge them again later.
2. They come back to the app, and the subscription is active.
3. Mollie charges them each week, month or year, from one period after the first payment.

Subscriptions are in euro, from 0.01 to 100,000 per charge, weekly, monthly or yearly. Only people who are signed in to the app can subscribe.

Customers cancel in the app

Customers can always cancel their own subscription in the app, without asking you: ask the assistant to put a cancel button where they see their subscriptions. Once cancelled, Mollie charges them no more. The charges made so far stay. Subscriptions cannot be paused: a customer cancels and subscribes again.

Follow your subscriptions

Every subscription is a record of the built-in Subscriptions entity under Data, which your organisation has once Mollie is added. Each one has its description, amount, interval (Weekly, Monthly or Yearly), subscription status (Pending until the first payment is paid, then Active, Cancelled, or Not started when the first payment did not go through), the date of the next charge and the record it is for. kvyk.ai keeps these fields up to date from what Mollie says, so nobody can change them by hand. You can rename the entity and add fields of your own.

Every charge is a record of the Payments entity, for the subscription. The person who subscribed sees their own subscriptions and charges. Administrators, and anyone whose data role has Full access, see all of them.

Cancel or change the price

Only Administrators do this, on the subscription’s record under Data, while it is pending or active:

• Cancel subscription, and confirm: Mollie charges it no more.
• Change price: type the new amount and choose Save price. The new price applies from the next charge on; the charges made so far stay as they are.

Act when a charge fails

A charge can fail, for example when a card has expired or an account has too little money. The charge’s payment status then becomes Failed, so an automation can act on it: start it when a Payment changes, only when Payment status changes, and only when Payment status is Failed. Let it email the customer to update their payment details, or tell your team.

Test subscriptions from Preview run in Mollie’s test mode and stay in Preview, and real ones only in Live.