Take payments in your apps
Have the assistant build a payment into an app, test it in Preview, take real payments in Live, and follow every payment as a record.
Your apps can ask people to pay: a deposit for a booking, an order from your shop, a bill at the table. Payments go through Mollie, with your organisation’s own Mollie account. The money goes straight to that account: kvyk.ai never holds it and takes nothing from it. Mollie charges its own fee per payment.
An Administrator first adds the Mollie connector in Settings, then Connectors, and connects your Mollie account there, for Preview and for Live: see Mollie. Until a stage is connected, the assistant tells you so before it builds a payment, and the app’s payments on that stage are refused.
Ask the assistant for a payment
Section titled “Ask the assistant for a payment”Tell the assistant what should be paid, for example: “Let customers pay the deposit for their booking, 20 euro, and mark the booking confirmed once it is paid.” It builds the payment into your app. When someone pays:
- The app sends them to Mollie’s payment page, where they choose iDEAL, Bancontact, a card or another method you switched on at Mollie.
- They come back to the app, which shows whether the payment went through.
Payments are in euro, from 0.01 to 100,000 per payment. Only people who are signed in to the app can pay.
Follow your payments
Section titled “Follow your payments”Every payment is a record of the built-in Payments entity under Data, which your organisation has once Mollie is added. If Mollie is removed, the entity and its records stay. Each payment has its description, amount, payment status (Open, Paid, Failed, Expired or Canceled), when it was paid and the record it pays 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.
The person who paid can see their own payment. Administrators, and anyone whose data role has Full access, see all of them.
Because a payment is a record, an automation can start when its status becomes Paid, for example to confirm an order or send a receipt.
Test payments from Preview stay in Preview, and real payments only in Live.
For charges that come back each week, month or year, see Take subscriptions in your apps.