Mollie affiliate program software, connected in one paste.

Yes, and it is a one-paste connect: you give Rekomi one advanced access token from your Mollie dashboard, and Rekomi validates it live, creates a signed webhook in your Mollie organization itself, and keeps the secret for you; there is no webhook form to fill in and nothing to paste back. Payments, subscription renewals, refunds, and chargebacks are recorded automatically, with a 30-minute check over refunds, chargebacks, and payments as the second path, and disconnecting deletes the webhook at Mollie again. Mollie allows three live webhooks per organization; if all three are already taken, Rekomi connects anyway and picks up payments, refunds, and chargebacks on the 30-minute check instead. Rekomi also runs periodic health checks on the token and the webhook, and emails you if anything needs attention.

Because Mollie's standard API keys (the ones starting with live_ or test_) are scoped to payment processing for one website profile and cannot create, read, or manage webhooks, and creating the webhook for you is the whole point of the one-paste setup; a standard key fails the connect with an error naming exactly that. An advanced access token is built from a permission checklist by an Admin user under Developers > API keys, and Rekomi asks for six: webhooks.read and webhooks.write to create and check the webhook, payments.read and refunds.read for the 30-minute check over payments, refunds, and chargebacks, profiles.read to bind your website profile, and organizations.read to confirm which organization the token belongs to. None of them can create a payment or a refund, so Rekomi never holds more of your Mollie account than it needs. The token and the webhook secret are stored encrypted at rest and never returned by the API, and disconnecting deletes the webhook at Mollie and wipes both.

Any setup where your own backend creates the payment through Mollie's API: a custom checkout on Mollie's hosted payment page, the Mollie Subscriptions API, and Mollie Components, which keep the card form on your own domain. Payment Links work too, with one honest caveat: a payment link has no metadata field, so a sale from a link is credited by matching the buyer's email to a lead the Rekomi script captured earlier, or by the customer's attribution history, never by a referral stamp. If your shop runs on WooCommerce, Shopify, or Wix with Mollie as the payment method behind it, connect the shop's own rail instead (the WooCommerce plugin, the Shopify app, or the Wix app), because the shop is where the order and the coupon code live; the same goes for Chargebee with Mollie underneath, where the Chargebee integration is the one to connect. On Shopware, Magento, or PrestaShop, the shop's Mollie plugin creates the payment for you, so there is no place to stamp the referral; track those stores with the Rekomi script on your pages and the S2S API from your backend instead.

Mollie's hosted checkout cannot run scripts, so the Rekomi script goes on your own site (your pricing, signup, and thank-you pages), captures the affiliate click in a first-party cookie, and the sale itself is credited from the webhook. Three carriers do the work. First, metadata: when your backend creates the payment or the subscription through Mollie's API, set metadata.rekomi_ref from window.Rekomi.getReferral(); Mollie forwards a subscription's metadata to every renewal payment it generates, so renewals credit the same affiliate. Second, coupon codes: Mollie has no coupon codes of its own, so if you run per-affiliate codes in your own checkout, stamp the code as metadata.rekomi_coupon and Rekomi credits the affiliate who owns it, with the coupon outranking the link. Rekomi reads the coupon on one-time and first payments only; renewals credit the same affiliate through customer and subscription history, so a coupon's commission override applies to the first charge, not to every cycle. Third, a lead email match: if the Rekomi script captured the customer's email on your signup form, pass it as billingAddress.email on the payment and Rekomi matches the sale to that lead, which is how a free trial with no card that first bills days later still credits the right affiliate. For later payments Rekomi also falls back to the customer's attribution history.

Mollie is a payment service provider, not a merchant of record, so the amount on a payment is what the customer paid, including any VAT you charge, and there is no separate tax field. If your payment carries order lines with VAT amounts (Mollie's lines array, optional on most payment methods), Rekomi computes the commission on the pre-tax total, the sum of the lines minus their VAT, so affiliates never earn on tax. If there are no lines, the commission is computed on the charge amount, which is the only figure Mollie reports. Refunds and chargebacks are scaled onto the same basis, and every clawback is bounded by what was credited. One edge worth knowing: a first payment below one unit of its currency (the 0.00 or 0.01 EUR mandate-verification charge Mollie recommends) is never a sale and never starts the recurring window, so the affiliate earns on the first real charge instead.

All of them record. Mollie's 28 payment currencies, from EUR, GBP, and CHF through the Nordic and Central European currencies to USD, AUD, JPY, and the rest, are all inside Rekomi's 135+ currency allowlist, and the two zero-decimal ones, ISK and JPY, get the right decimal math. Mollie reports amounts as exact decimal strings and Rekomi parses them exactly, never through a locale parser, so a commission is never computed on a mangled amount. Rekomi always reads the amount the customer paid, never Mollie's deprecated settlement amount, and any conversion into your home currency happens on Rekomi's side with its own rates.

By construction. Mollie's test mode has its own webhooks and its own data, and it supports EUR only, which is worth knowing before you try a test payment. In production Rekomi connects your live mode: the webhook it creates is a live webhook, and every payment is additionally checked against the connected mode and the connected website profile before it records, while a refund or chargeback only ever applies to a payment this workspace recorded, so a test payment can never book production money and a test refund can never touch a live commission.

No; Rekomi enforces one conversion source of truth per workspace so the same sale is never recorded twice, and one Mollie connection binds one website profile. Pick one connection for Mollie sales and keep it; if you genuinely sell on two platforms, run them as separate workspaces. One precise edge: if Mollie is only the payment method behind a WooCommerce, Shopify, or Wix store, connect the WooCommerce plugin, the Shopify app, or the Wix app rather than Mollie, because the shop is the platform reporting those orders and their coupon codes; the Mollie rail is for custom checkouts, the Mollie Subscriptions API, Payment Links, and Mollie Components.