Mollie subscriptions, payments and fees in one dashboard
Connect a Mollie Advanced access token with read scopes only. Sumly reads subscriptions, payments, refunds, chargebacks, Mollie's fee on each payment and your balance.
Connected in three steps
A read-only key, pasted once. Sumly does the rest.
-
1
In Mollie (as an Admin): Developers → API keys → Build your own advanced access token. Name it Sumly.
-
2
Give it only payments.read, refunds.read, subscriptions.read, balances.read and profiles.read. Nothing to write.
-
3
Paste the
access_…token below. A live API key (live_…) works too, for one website profile, but it can also write and shows no fees. -
4
To trace payments to visits, pass
metadata: { sumly_visitor_id: sumly.visitorId }when you create the payment or subscription.
Or let your coding assistant do it
Paste this into Claude Code, Cursor or Codex in your project. It fits the code to how your project is built, asks you for the dashboard steps and leaves the keys to you.
See what it says
Set up Mollie for Sumly in this project.
Sumly (https://sumly.dev) shows revenue next to the visits and app users it came from. The full guide is https://sumly.dev/integrations/mollie; read it if anything below is unclear.
Steps:
1. In Mollie (as an Admin): Developers → API keys → Build your own advanced access token. Name it Sumly.
2. Give it only payments.read, refunds.read, subscriptions.read, balances.read and profiles.read. Nothing to write.
3. Paste the `access_…` token into Sumly. A live API key (`live_…`) works too, for one website profile, but it can also write and shows no fees.
4. To trace payments to visits, pass `metadata: { sumly_visitor_id: sumly.visitorId }` when you create the payment or subscription.
So each payment shows which visit it came from: Pass metadata named sumly_visitor_id, holding the sumly_vid cookie, when you create a payment or a subscription; Mollie copies a subscription's metadata to each payment it makes. Each payment then counts for the source, campaign and country of the visit that started it. In the EU and UK there is a visitor only after they agree.
Keep in mind: Built from Mollie's API reference and checked against responses shaped like it, not yet against a live Mollie account. Tell us if a number looks off. Mollie is not the merchant of record: like Stripe, a payment counts what the buyer paid, VAT included, unless it lists its lines with their VAT. With a live API key instead of a token, Sumly reads one website profile and shows no fees or balance. Mollie's payment links take no field Sumly could carry the visitor in, so they are not traced.
How to work:
- Look at how this project is built first, and fit the code to its framework and its way of doing things; the examples above are a starting point, not something to paste as is.
- Steps that happen in a dashboard (Sumly, or Mollie's own) are mine: tell me exactly what to click, then wait for me.
- The Mollie key goes into Sumly (Projects and payments), not into this project: Sumly reads Mollie itself. Your part in the code is only carrying the visitor into checkout, as above.
- Keys the code needs belong in environment variables, never in the code or the repository. Never ask me to paste a secret key into this chat; tell me which variable to set.
- Change only what this needs, show me the changes before you commit, and tell me how to check that it works.
What you see after connecting
Mollie next to every other project and provider, on the same pages.
Overview
MRR, ARR, revenue per customer, paying customers, trials and your Mollie balance.
Payments after Mollie's fee, with the buyer's name and country.
Metrics over time, with churn, LTV and quick ratio.
Plans by subscription description, customers, the outlook and a CSV export.
With the visitor in the payment metadata
Revenue by source and campaign, and ROI for each cost.
Which visit paid
Pass metadata named sumly_visitor_id, holding the sumly_vid cookie, when you create a payment or a subscription; Mollie copies a subscription's metadata to each payment it makes. Each payment then counts for the source, campaign and country of the visit that started it. In the EU and UK there is a visitor only after they agree.
How attribution works →Counts toward your plan
Nothing: payments, customers and refunds never count toward your plan. Only the page views and app screens Sumly keeps do. Plans →
The details
What Sumly reads
- Subscriptions across every website profile, with their interval and trial
- Paid payments, with VAT taken off when the payment lists its lines
- Refunds and chargebacks
- Mollie's fee on each payment, from your balance
- The balance available and pending
When Sumly reads Mollie
- Every 15 minutes, together with the other connections of the project. The first read takes three years of payments.
- Subscriptions are read whole each time; payments, refunds and chargebacks from shortly before the newest one kept.
- Fees come from the balance transactions of the same days.
- With the webhook added, each payment is read again from Mollie the moment it is paid, with its refunds, chargebacks and subscription.
How Mollie money is counted
- Monthly value
- The subscription's amount spread over its interval: "3 months" a third each month, "14 days" by the day, "1 week" 52 ÷ 12.
- Trials
- A subscription whose first payment is set for a later date counts from that date.
- Cancellations
- A cancelled subscription stops on the day it was cancelled. A suspended one (its payments kept failing) or a completed one stops on the day Sumly first sees it so, as Mollie keeps no time for it.
- VAT
- Mollie is not the merchant of record. Payments count what was paid; when a payment lists its lines, their VAT comes off.
- Fees
- The deductions on each payment's balance transaction. A refund's own fee comes off too.
- Refunds and chargebacks
- Each on the day it was made, without its share of VAT where there is one. A reversed chargeback does not count.
- Currency
- Payments in their own currency, turned into euros at the ECB rate of that day. MRR converts at today's rate.
Good to know
- Built from Mollie's API reference and checked against responses shaped like it, not yet against a live Mollie account. Tell us if a number looks off.
- Mollie is not the merchant of record: like Stripe, a payment counts what the buyer paid, VAT included, unless it lists its lines with their VAT.
- With a live API key instead of a token, Sumly reads one website profile and shows no fees or balance.
- Mollie's payment links take no field Sumly could carry the visitor in, so they are not traced.
Mollie questions
Can Sumly change anything in Mollie?
Not with an Advanced access token that has only the read scopes above. An API key can also write; Sumly never does.
Why a token rather than an API key?
A token can be limited to reading, sees every website profile, and may read your balance, where Mollie's fees are.
Do I need the webhook?
No. Sumly reads Mollie every 15 minutes either way. With the webhook, payments show up within seconds.
Does Sumly read test mode?
No, only live payments.
Why is the webhook not signed?
It does not need to be: the address holds a secret of its own, and Mollie's classic webhook only says which payment changed. Sumly reads it again from Mollie with your token.
Other integrations
ShopifyTry it with your own projects
Sign in with Google or a code by e-mail and connect your first project. Free for one project, and 14 days of a paid plan with no card.
Start freeOr look around first: open the live demo.