Mollie

This connector uses the Mollie API v2 (docs.mollie.com/reference).

Setup:

1. Sign in to https://my.mollie.com → Developers → API keys.
2. Use a test key (test_...) for development, live key (live_...) for production.
3. Set MOLLIE_API_KEY accordingly. (Mollie tells you which environment via the key prefix.)

Authentication: Authorization: Bearer ${MOLLIE_API_KEY}.

Amount format: every monetary amount is {currency: 'EUR', value: '10.00'} — value is a STRING with exactly 2 decimals (or whatever the currency requires). Sending value: 10 (number) errors.

Payment lifecycle: created → open → pending → authorized → paid (success) | canceled | expired | failed.

Profile and mode: every payment belongs to a profile (website). On Mollie you can have multiple profiles per account. The profileId is implicit (uses the default profile of the key); for multi-profile accounts pass it explicitly.

Subscriptions and mandates: subscriptions need a mandate (a pre-authorized customer payment method). Workflow: create customer → first one-off payment with sequenceType=first → use the resulting mandate to create the subscription.

Payment links: mollie_create_payment_link returns a hosted checkout URL (_links.paymentLink.href) to send to a customer, without a website. paidAt on the link (or mollie_list_payment_link_payments) shows whether it was paid. With a live key the link is real and payable.

Webhooks out of scope (Mollie pushes payment.* events to a URL you host).

Pagination: cursor-based via from=<resourceId> + limit (max 250). Response has _links.next.href for next page.

Rate limits: 250 req per 5 sec per IP. On 429 honor headers.

Out of scope here: settlements, invoices, profile management, organizations, partners (Mollie Connect), permissions.