Through the API
With Mollie, your server reports the sale to Meritt through the API, in three calls, as soon as Mollie confirms the payment. Attribution and the ledger are the same as for Stripe.
POST /v1/conversions to report the sale, POST /v1/identify to tie a customer to a visit, POST /v1/conversions/reverse for a refund. A sale sent twice is counted once.metadata at checkout.id: your server fetches the payment to learn its status before reporting it to us.metadata.paid, call POST /v1/conversions with the amount, the currency, the click and the customer id.refunded, call POST /v1/conversions/reverse with the payment reference.One key, and two calls added to your webhook handling.
At that moment the payment is not confirmed, and when it is, in the webhook, the cookie is gone. The Mollie passthrough field carries the click between the two.
No. With the same reference, the second call answers “already received” and nothing is added.
According to Mollie, the subscription's metadata is copied onto every payment it generates: the click travels from one term to the next.
About 1 kB according to Mollie: the click id fits easily.
Mollie documentation checked on October 19, 2026: docs.mollie.com › webhooks, docs.mollie.com › create payment, docs.mollie.com › create subscription
Your affiliates' links run through your site, so ad blockers do not cut them.
An affiliate program on Razorpay: the click in notes, payment.captured and refund.processed reported to Meritt through the API.
Meritt connects to Stripe in one click and reads payments, renewals, refunds and disputes, then pays your affiliates.
Free until your first commission. No card asked for.