Mollie
Keep Mollie in step with your orders, invoices and payments without re-keying, with the right person approving what changes.
46 ways to read, 6 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with Mollie, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create customerApproval by rule
- Create payment linkApproval by rule
- Get balance reportRead
Example flow
- Mollie · Get balance reportDone
- Mollie · Create customerNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches Mollie.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to Mollie
- Mollie's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect a Mollie test account before you go live.
For developers
Technical detail
Mollie payments, refunds, captures, chargebacks, settlements, balances, payouts, invoices, profiles and webhooks (read); payment links, customers and draft sales invoices (write).
Mollie API docs- Source actions
- 46
- Destination actions
- 6
- Data types
- 28
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Balance reports1
- Get balance reportSource
Opening and closing balance with totals by status or transaction category for a date range.
Balance transactions1
- List balance transactionsSource
Every movement on a balance (payments, refunds, chargebacks, fees, transfers) with net amounts.
Balances2
- Get balanceSource
Get balance by ID.
- List balancesSource
Mollie balances with available and pending amounts.
Capabilities1
- List capabilitiesSource
Organization capabilities (payments, settlements ...) and their status.
Captures2
- Get captureSource
Get capture by ID.
- List capturesSource
Captures already made on one payment. Nexra never creates captures.
Chargebacks2
- Get chargebackSource
Get chargeback by ID.
- List chargebacksSource
Chargebacks for the profile or one payment.
Customers4
- Create customerDestinationProvider duplicate protectionApproval before production
Create a customer for recurring payments and reporting.
- Get customerSource
Get customer by ID.
- List customersSource
Customers in the profile.
- Update customerDestinationProvider duplicate protectionApproval before production
Update name, email, locale or metadata.
Invoices2
- Get Mollie invoiceSource
Get Mollie invoice by ID.
- List Mollie invoicesSource
Invoices Mollie issued to you for fees, optionally by reference or year.
Mandates2
- Get mandateSource
Get mandate by ID.
- List mandatesSource
A customer's mandates; account numbers and holder names are omitted.
Methods2
- Get payment methodSource
Get payment method by ID.
- List payment methodsSource
Payment methods enabled on the profile, or every method Mollie offers, with amount limits.
Onboarding1
- Get onboarding statusSource
Whether the organization can receive payments and settlements.
Organization1
- Get current organizationSource
The organization behind the credential: name, locale, registration and VAT.
Payment links4
- Create payment linkDestinationProvider duplicate protectionApproval before production
Create a Mollie-hosted payment link with a fixed or minimum amount. No money moves until the customer pays.
- Get payment linkSource
Get payment link by ID.
- List payment linksSource
Payment links in the profile.
- Update payment linkDestinationProvider duplicate protectionApproval before production
Change description, minimum amount, allowed methods or archived state.
Payment routes1
- List payment routesSource
Split-payment routes already set on a payment (read only).
Payments2
- Get paymentSource
Get payment by ID.
- List profile paymentsSource
Read payments in the API key’s profile; preserve decimal value and currency. Optionally scoped to a customer, payment link, subscription or settlement.
Payouts2
- Get payoutSource
Get payout by ID.
- List payoutsSource
Payouts from a balance to your bank account (read only).
Permissions2
- Get permissionSource
Get permission by ID.
- List permissionsSource
Permissions granted to the current credential.
Profiles2
- Get profileSource
Get profile by ID.
- List profilesSource
Website profiles of the organization.
Refunds2
- Get refundSource
Get refund by ID.
- List refundsSource
Refunds already issued, for the profile or one payment. Nexra never creates refunds.
Sales invoices4
- Create draft sales invoiceDestinationProvider duplicate protectionApproval before production
Create a sales invoice as a draft. Drafts are not sent, issued or collected; finish them in the Mollie Dashboard.
- Get sales invoiceSource
Get sales invoice by ID.
- List sales invoicesSource
Sales invoices you issue to your customers through Mollie.
- Update draft sales invoiceDestinationProvider duplicate protectionApproval before production
Change the recipient, lines, payment term or memo of a draft sales invoice.
Settlement captures1
- List settlement capturesSource
List settlement captures included in one settlement.
Settlement chargebacks1
- List settlement chargebacksSource
List settlement chargebacks included in one settlement.
Settlement refunds1
- List settlement refundsSource
List settlement refunds included in one settlement.
Settlements2
- Get settlementSource
Get settlement by ID.
- List settlementsSource
Settlements (payouts to your bank) with optional year, month and currency filters.
Subscriptions2
- Get subscriptionSource
Get subscription by ID.
- List subscriptionsSource
Subscriptions for the profile, or for one customer.
Terminals2
- Get terminalSource
Get terminal by ID.
- List terminalsSource
Point-of-sale terminals linked to the account.
Webhook events1
- Get webhook eventSource
Get webhook event by ID.
Webhooks2
- Get webhookSource
Get webhook by ID.
- List webhooksSource
Next-generation webhook subscriptions (secrets are never returned).
Access and limits
- Authentication
- Profile-scoped Mollie test/live API key
- Plans and access
- Any Mollie account. Profile API keys cover payments, links, customers and subscriptions. Settlements need an organization access token (or OAuth token) with settlements.read; the other operations work with a profile API key.
- Test environment
- Use a test_ API key; test-mode records are separate from live.
- Rate limits
- Mollie returns HTTP 429 when request limits are exceeded. Nexra honours Retry-After; creates use the Idempotency-Key header so retries do not duplicate links or customers.
- Pagination
- Cursor pagination through _links.next.href (up to 250 records per page).
- Provider events
- Mollie calls your webhookUrl on payment, refund, chargeback and payment-link status changes. Flows can start the moment something happens: when a payment succeeds; when a payment fails; when a payment is cancelled or expires; when a payment link is paid.
Before you build a flow
- Intentional exclusions: creating, updating or cancelling payments, captures, releasing authorizations, refunds and refund cancellation, creating payment routes, creating or revoking mandates, creating, updating or cancelling subscriptions, deleting payment links, customers or sales invoices, issuing or marking sales invoices paid, payouts and their cancellation, Connect balance transfers, business-account transfers, matching or returning unmatched credit transfers, enabling or disabling payment methods, profile, webhook, onboarding and client-link writes, terminal pairing codes, and Apple Pay sessions.
- Sales invoices are created as drafts only; status, payment details, email details and mandate IDs are never sent.
- Balances, balance reports, balance transactions, payouts, invoices, profiles list and organization need an organization access token or OAuth token with the matching read scope.
- Balance bank account numbers and beneficiary names, business accounts and webhook event entity snapshots are not mapped.
- Mollie lists have no date or updated-since filter (payments, refunds, chargebacks, settlements, payouts and balance transactions take only an ID cursor named from), so no read is incremental; sync by creation order with sort=asc and the next-page link. Settlements filter by calendar year and month only, and the balance report takes a from and until date range for totals, not records.
- Organization-level OAuth tokens need profileId and testmode parameters, which are not exposed; use a profile API key for profile-scoped data.
- Mandate account numbers, holder names and emails are omitted.
Developer reference
- Create the Mollie credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose Mollie, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/mollie and the Connections API.