Menu

Mattering Automations Mollie integration

Connect Mollie to Mattering Automations: payments, refunds, customers, mandates, recurring subscriptions, payment links, chargebacks, payment methods, and the organization level reads for settlements, balances, balance reports, invoices, profiles, and onboarding, all as workflow steps authenticated with one Mollie API key sent as a bearer token.

The Mattering Automations Mollie integration adds the Mollie API v2 to your automation canvas: create, read, update, and cancel payments, issue and cancel refunds, manage customers with their mandates and recurring subscriptions, create shareable payment links, read chargebacks, list the payment methods a profile can actually offer, and pull the reporting surface of settlements, settlement payments, balances, windowed balance reports, invoices, profiles, and onboarding status.

The credential is a Mollie API key sent as a bearer token, taken from the Mollie Web App under Developers, then API access tokens. There is one host for both modes and no environment setting: a profile API key beginning test_ reaches test data and one beginning live_ reaches live data at the same base URL, so the key you paste is the mode you get. One tier distinction matters before you start. A profile API key covers 34 of the 45 nodes; the other eleven, the settlement, balance, invoice, organization, profile, and onboarding reads, are gated by Mollie on an advanced access token, its organization level credential. Advanced access tokens are the documented exception to the prefix rule, because their mode comes from a testmode request parameter or the scope picked when the token was created rather than from the value. Setup takes a few minutes, and this guide walks each step and ends with the full node reference.

This integration moves real money, so the safety modeling is stated on the nodes rather than buried. Of the 45 nodes, 30 read and 15 act, and seven carry a destructive flag: Mollie: Create Payment Refund, Mollie: Cancel Payment Refund, Mollie: Cancel Payment, Mollie: Delete Customer, Mollie: Revoke Mandate, Mollie: Create Subscription, and Mollie: Cancel Subscription. Two of them cascade on Mollie's own statement: deleting a customer cancels that customer's mandates and subscriptions, and revoking a mandate cancels the subscriptions connected to it. Creating a payment, a customer payment, or a payment link charges nobody at call time, so those stay reversible writes, and every write node exposes Mollie's documented idempotency key as an optional field.

Before you start

  • A Mollie account, and permission to read its keys in the Mollie Web App. The test half is available as soon as the account has a website profile, so you can connect and rehearse immediately; processing real payments waits on Mollie's go live checklist, which asks for business verification, stakeholder details, and bank account information before a live key is of any use. A key carries the ability to take and return money on the account, so if your team separates duties, the person connecting Mollie to Mattering should be one who is allowed to hold that key.
  • A decision about which key you need. A profile API key beginning test_ or live_ covers payments, refunds, customers, mandates, subscriptions, payment links, chargebacks, and methods. An advanced access token, Mollie's organization level credential, is required for the settlement, balance, invoice, organization, profile, and onboarding nodes. An account that wants both can store two credentials and pick per workflow. Mind the gates on the credential page itself: Mollie restricts API access tokens to the Admin and Developer roles, says the page is not available on mobile, and allows only an Admin to create a token, so if those eleven nodes are in scope you need an Admin at a desktop browser to mint the credential.
  • A test key for the first run. Mollie issues a test key alongside the live key, and it reaches test data on the same base URL, so the payment, refund, customer, mandate, subscription, link, and chargeback nodes, including the destructive ones, can be rehearsed before anything touches a real customer. There is one exception, and Mollie states it: its API endpoints related to business operations do not support test mode, so the settlement, balance, and invoice nodes read live data whichever credential you hold. None of the destructive nodes sit in that excluded set, so the rehearsal path is intact.
  • At least one website profile on the account. The enabled payment methods, payments, and customers a workflow reads all belong to a profile, and a profile API key is bound to one of them.
  • A Mattering workspace with access to the Automations app.

Get your Mollie API key

Mattering authenticates to Mollie with an Authorization header carrying your key as a bearer token, on every request to api.mollie.com. Mollie has no separate sandbox host, so a profile API key is also the mode selector: test_ for test data, live_ for live data, same URL. Advanced access tokens work differently, taking their mode from a testmode request parameter or the scope chosen at creation rather than from the value. Choose the tier before you copy anything, because a profile API key and an advanced access token unlock different parts of the node list.

Sign in to the Mollie Web App and open Developers, then API access tokens.
Copy the key that matches the work. Take a test_ or live_ profile API key for payments, refunds, customers, mandates, subscriptions, payment links, chargebacks, and methods. Take an advanced access token, the organization level credential, if the workflow needs settlements, balances, the balance report, invoices, the organization read, profiles, or onboarding status.
Mollie shows a key once at creation and cannot retrieve it afterwards. Copy it straight into the Mattering credential rather than parking it in a note, and if it is ever lost or leaked, create a new key and revoke the old one, which invalidates it everywhere it is in use, including this integration.
For a profile API key the prefix is the mode. One beginning test_ reaches test data and one beginning live_ reaches live data at the same address, so there is no environment setting in the credential and nothing to keep in sync. Start with the test key, prove the workflow, then swap the credential value for the live key. Advanced access tokens are the exception Mollie documents: their mode comes from a testmode request parameter or the scope chosen when the token was created, so an organization level credential is not readable as test or live from its value.

Connect Mollie to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Mollie from the list.
Click Create new credential, paste the Mollie key, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection. Mattering calls Mollie's payment methods endpoint, which every credential tier can read, and a 401 titled Unauthorized Request means the key is wrong, mistyped, or revoked. Mollie scopes the popular methods fallback to test mode, so a fresh test key answers with rows even before any method is activated, while a live key on a profile with nothing activated can legitimately return an empty list. That is a configuration state, not a failed credential.
Click Connect. All 45 Mollie nodes appear in your canvas palette.
Seven of those nodes are flagged destructive because they move money or cannot be undone. Mollie: Create Subscription is the one to read twice before wiring: it bills against a mandate the customer authorized earlier, so no second approval stands between the call and a real charge, Mollie does not state what the first charge date is when the start date is omitted, and Mollie documents no refund of payments already collected, so treat those as a separate refund decision. Set an explicit start date, keep it and Mollie: Create Payment Refund, Mollie: Cancel Payment, Mollie: Cancel Payment Refund, Mollie: Cancel Subscription, Mollie: Delete Customer, and Mollie: Revoke Mandate behind a condition or an approval task, and rehearse the whole flow with a test_ key first.

Verify it works

After connecting, open any automation canvas and check the palette: a Mollie section should list the query and action nodes. Drop Mollie: List Payment Methods onto the canvas and run a test step. It is the integration's natural probe: it needs no parameters, every credential tier can call it, and rows land at data._embedded.methods[] because Mollie answers in HAL and wraps list rows under an embedded key named for the resource. Then run Mollie: List Payments and Mollie: List Customers and copy an ID from each, since the payment ID and the customer ID are the two values most downstream nodes ask for.

Everything in that path is read only, so it is safe to re-run whenever you rotate the key, and it cannot reach any of the seven destructive nodes. If you connected an organization level access token, add Mollie: Get Current Organization to confirm which organization the token belongs to and Mollie: Get Onboarding Status to see whether the account can receive payments and settlements yet. Two shapes are worth noticing while you are here: list endpoints are cursor paginated, with the next page URL at data._links.next.href and a limit that accepts up to 250 rows per call, and the payment links lister is the one embedded key that is underscored, at data._embedded.payment_links[].

Node reference

45 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 30

Mollie: Get Balance

mollie_get_balance

Read one balance: the available amount that can be paid out or refunded, and the pending amount still clearing. The alias primary works in place of an ID. The natural low balance check before a refund run. Needs an ORGANIZATION LEVEL credential.

Mollie: Get Balance Report

mollie_get_balance_report

Summarize every movement on a balance between two dates: opening and closing amounts, plus totals per category (payments, refunds, chargebacks, transfers, fee prepayments, corrections). The from date is INCLUSIVE, the until date is EXCLUSIVE, and both are read in Central European Time, so a full month runs from the 1st to the 1st of the next month. The alias primary works in place of a balance ID. Needs an ORGANIZATION LEVEL credential.

Mollie: Get Current Organization

mollie_get_current_organization

Read the organization the credential belongs to: name, email, locale, registered address, registration and VAT numbers, and when it was verified. Useful as an identity check for an organization level token. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.

Mollie: Get Customer

mollie_get_customer

Read one customer by its ID, including the stored name, email, locale, and metadata.

Mollie: Get Invoice

mollie_get_invoice

Read one Mollie invoice by its ID, with its status, amounts, fee lines, and a PDF download URL at data._links.pdf.href. To look one up by invoice number, use List Invoices with the reference filter. Needs an ORGANIZATION LEVEL credential.

Mollie: Get Mandate

mollie_get_mandate

Read one mandate by its ID and the ID of its customer. The details object carries the bank, card, or PayPal specifics of the authorization, and status tells you whether it can still be charged.

Mollie: Get Onboarding Status

mollie_get_onboarding_status

Read the onboarding state of the organization: whether it is completed, and whether it can receive payments and settlements yet. The check to run before assuming a newly connected account can actually take money. Needs an ORGANIZATION LEVEL credential.

Mollie: Get Payment

mollie_get_payment

Read one payment by its ID: status, amounts, method details, and the amounts already refunded or charged back. The isCancelable field tells you whether Cancel Payment will work right now.

Mollie: Get Payment Chargeback

mollie_get_chargeback

Read one chargeback by its ID and the ID of its payment, including the reason code and description, the settlement amount deducted, and whether it was later reversed.

Mollie: Get Payment Link

mollie_get_payment_link

Read one payment link by its ID, including whether it has been paid, whether it is archived, and the shareable URL at data._links.paymentLink.href.

Mollie: Get Payment Method

mollie_get_method

Read one payment method by its ID, including its logo and amount limits. Mollie returns 404 when the method is not available on the profile and 403 when it is available but not yet enabled, which makes this the check before offering a method in a checkout.

Mollie: Get Payment Refund

mollie_get_refund

Read one refund by its ID and the ID of its payment. The status field (queued, pending, processing, refunded, failed, canceled) is what decides whether the refund can still be canceled.

Mollie: Get Settlement

mollie_get_settlement

Read one settlement, including the periods breakdown of revenue and costs per method for the payout. The literal values next and open also work in place of an ID, for the settlement being built and the one not yet closed. Needs an ORGANIZATION LEVEL credential.

Mollie: Get Subscription

mollie_get_subscription

Read one subscription by its ID and the ID of its customer: amount, interval, status, times remaining, and the next payment date.

Mollie: List All Chargebacks

mollie_list_all_chargebacks

List every chargeback across all payments, newest first, with the reason code and the amount deducted from the settlement. Rows land at data._embedded.chargebacks[]. This is the account wide view; use List Payment Chargebacks for one payment.

Mollie: List All Payment Methods

mollie_list_all_methods

List every payment method Mollie offers, whether or not the organization is eligible for it. Use it to plan which methods to request; use List Payment Methods for what is actually usable today. Not paginated. Rows land at data._embedded.methods[].

Mollie: List Balances

mollie_list_balances

List the organization's balances, including the primary one, with their available and pending amounts and payout settings. Rows land at data._embedded.balances[]. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.

Mollie: List Customer Payments

mollie_list_customer_payments

List every payment linked to one customer, newest first. Rows land at data._embedded.payments[], the same shape as List Payments.

Mollie: List Customer Subscriptions

mollie_list_subscriptions

List the subscriptions of one customer with their status, interval, amount, and next payment date. Rows land at data._embedded.subscriptions[]. This is the source node behind the subscription picker, so it is scoped to a customer.

Mollie: List Customers

mollie_list_customers

List customers, newest first. Rows land at data._embedded.customers[] and the next page URL at data._links.next.href. This is the source node behind every customer picker in this connector.

Mollie: List Invoices

mollie_list_invoices

List the invoices Mollie has issued to the organization for its own fees, newest first, with net, VAT, and gross amounts and the fee lines. Rows land at data._embedded.invoices[]. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.

Mollie: List Mandates

mollie_list_mandates

List the mandates of one customer with their status (valid, pending, invalid) and method. Rows land at data._embedded.mandates[]. This is the source node behind the mandate picker, so it is scoped to a customer. The documented scopes filter is reachable through extra query.

Mollie: List Payment Chargebacks

mollie_list_payment_chargebacks

List the chargebacks raised against one payment. Rows land at data._embedded.chargebacks[]. This is the source node behind the chargeback picker, so it is scoped to a payment.

Mollie: List Payment Links

mollie_list_payment_links

List payment links, newest first, with their amounts, archived flag, and shareable URLs. Rows land at data._embedded.payment_links[]; note the embedded key is underscored, unlike the other list endpoints.

Mollie: List Payment Methods

mollie_list_methods

List the payment methods enabled on the website profile, with their logos and minimum and maximum amounts. This is the Gate 1 auth probe: it needs no parameters and every credential tier can call it. In test mode Mollie also returns pending methods, and a profile that has requested nothing yet gets the most popular methods back. This endpoint is not paginated. Rows land at data._embedded.methods[].

Mollie: List Payment Refunds

mollie_list_refunds

List the refunds created for one payment, newest first. Rows land at data._embedded.refunds[]. This is the source node behind the refund picker, which is why it is scoped to a payment rather than the whole account.

Mollie: List Payments

mollie_list_payments

List the payments created with the current website profile, newest first. Cursor paginated: rows land at data._embedded.payments[] and the next page URL at data._links.next.href. This is the source node behind every payment picker in this connector.

Mollie: List Profiles

mollie_list_profiles

List the organization's website profiles with their name, website, review status, and business category. Rows land at data._embedded.profiles[]. This is the source node behind the profile picker, and like the profile parameter itself it needs an ORGANIZATION LEVEL credential: a profile API key is already bound to one profile.

Mollie: List Settlement Payments

mollie_list_settlement_payments

List the payments included in one settlement, in the same shape as List Payments, which is how a payout is reconciled against orders. Capture based methods such as Klarna appear as captures instead, so they are not listed here. Needs an ORGANIZATION LEVEL credential.

Mollie: List Settlements

mollie_list_settlements

List the payouts Mollie has made to the bank account, newest first, with their reference, status, amount, and the invoice they belong to. Rows land at data._embedded.settlements[]. Needs an ORGANIZATION LEVEL credential (an access token), not a profile API key.

Action nodes 15

Mollie: Cancel Payment

mollie_cancel_payment

DESTRUCTIVE and IRREVERSIBLE: cancel an open payment. The payment moves to canceled and can never be paid; there is no uncancel, so a new payment has to be created instead. Only works while the payment reports isCancelable true, which depends on the method and usually lasts until the next business day.

Mollie: Cancel Payment Refund

mollie_cancel_refund

DESTRUCTIVE and IRREVERSIBLE: stop a refund before it is executed. Mollie only allows this while the refund status is queued or pending, and a canceled refund cannot be reopened, so refunding again means creating a new refund. Returns no content on success.

Mollie: Cancel Subscription

mollie_cancel_subscription

DESTRUCTIVE and IRREVERSIBLE: cancel a subscription. Status becomes canceled and no further payments are scheduled; Mollie documents no way to reactivate one, so restarting billing means creating a new subscription. The customer's mandates are left alone.

Mollie: Create Customer

mollie_create_customer

Create a customer record, the object mandates and subscriptions hang off. Nothing is charged and no email is sent; the customer also becomes visible in the Mollie dashboard. The new ID arrives at data.id.

Mollie: Create Customer Payment

mollie_create_customer_payment

Create a payment already linked to a customer, which is the Create Payment endpoint with the customer filled in. NO MONEY MOVES at creation: the shopper still completes the checkout at data._links.checkout.href. Linking the customer is what lets a returning shopper reuse a stored card and what a recurring sequence needs.

Mollie: Create Mandate

mollie_create_mandate

Record an existing authorization to charge a customer later. No money moves and no shopper is contacted. Only SEPA Direct Debit and PayPal mandates can be created directly this way; a card mandate is created by having the shopper make a first payment. The mandate ID arrives at data.id and is what a subscription bills against.

Mollie: Create Payment

mollie_create_payment

Create a payment and get back a checkout URL at data._links.checkout.href to send the shopper to. NO MONEY MOVES here: the payment starts with status open and is only charged when the shopper completes the checkout, which is why this is a reversible write while refunds and cancellations are not. Set a webhook URL to receive the status change.

Mollie: Create Payment Link

mollie_create_payment_link

Create a shareable payment link. NO MONEY MOVES: a payment only appears when someone opens the link and pays. The shareable URL comes back at data._links.paymentLink.href. Leave the amount blank to let the payer enter one, optionally with a minimum. Links do not expire unless an expiry is set, and a link can be archived later to stop accepting payments.

Mollie: Create Payment Refund

mollie_create_refund

DESTRUCTIVE: this MOVES REAL MONEY back to the shopper and there is no un refund. The amount may be lower than the original payment for a partial refund. Mollie executes refunds after a delay, and Cancel Payment Refund is the only way back, and only while the refund is still queued or pending. Use the idempotency key so a retry cannot pay twice.

Mollie: Create Subscription

mollie_create_subscription

DESTRUCTIVE: schedules REAL RECURRING CHARGES against a mandate the customer has already authorized, so no further approval stands between this call and money moving, and cancelling later does not refund what was collected. The customer needs a valid mandate first. Set a start date to control when billing begins, and times to end the subscription after a fixed number of charges. The description must be unique among that customer's active subscriptions.

Mollie: Delete Customer

mollie_delete_customer

DESTRUCTIVE and IRREVERSIBLE: delete a customer. Mollie states that ALL mandates and ALL subscriptions of that customer are canceled with it, so recurring revenue stops and the authorizations cannot be restored. Past payments stay in the account's history.

Mollie: Revoke Mandate

mollie_revoke_mandate

DESTRUCTIVE and IRREVERSIBLE: revoke a mandate. The account or card can no longer be charged with it, and Mollie states that ALL connected subscriptions are canceled as well. A revoked mandate cannot be restored; the customer has to authorize a new one.

Mollie: Update Customer

mollie_update_customer

Update a customer's name, email, locale, or metadata. Only the fields you fill are sent, so blank fields are left untouched rather than cleared.

Mollie: Update Payment

mollie_update_payment

Update details of an existing payment: description, redirect and webhook URLs, metadata, method, locale, or due date. Only the fields you fill are sent, and Mollie states that updating a payment does not trigger a webhook call.

Mollie: Update Subscription

mollie_update_subscription

Change an active subscription's amount, interval, description, start date, number of times, webhook, or mandate. Future charges follow the new values and the change can be edited again; a canceled subscription cannot be updated. Fill BOTH amount fields when changing the amount, because Mollie expects the currency with the value.

Using the integration

On the automation canvas

Mollie nodes chain with every other node on the canvas. A support form can run Mollie: Get Payment, branch on how much is still refundable, and open an approval task in Mattering Productivity before anything moves. A scheduled sweep can run Mollie: List Settlements and Mollie: List Settlement Payments and write a payout and its payments into a Mattering database for reconciliation. A signup flow can run Mollie: Create Customer and hand the new ID at data.id to the rest of the run. The payment ID from Mollie: List Payments and the customer ID from Mollie: List Customers are the two values almost every other node wants, which is why both listers also back the pickers on the fields that need them.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and Matter can drive the same surface. The 30 read nodes are the comfortable place to start: an agent can answer where a payment stands with Mollie: Get Payment, find a customer's recurring plans with Mollie: List Customer Subscriptions, or explain a deduction with Mollie: Get Payment Chargeback. Keep the seven destructive nodes behind a condition or an approval task rather than a bare instruction, and fill the idempotency key on writes so a retried agent turn cannot create the same refund or subscription twice. Mollie also ships an official MCP server of its own, hosted at https://mcp.mollie.com/mcp, authenticated with an advanced access token that has to carry the profile.read scope, and documented with Claude Desktop and Cursor as clients. It covers Balances, Captures, Customers, Invoices, Mandates, Methods, Payments, Payment Links, Settlements, Subscriptions, Terminals, Webhooks, and Webhook Events, which includes captures, terminals, and webhook management that this integration deliberately leaves out, so it is worth knowing about. What differs is the credential and the surroundings. Mollie's server asks for an organization level advanced access token for everything it does, including a plain payment read, while 34 of these 45 nodes run on an ordinary profile API key. And these nodes come with destructive flags, an optional idempotency key, and a canvas, so a refund can wait on an approval task and a settlement sweep can run on a schedule with no agent in the loop at all.

Taking a payment, and what actually charges anyone

Mollie: Create Payment returns a checkout URL at data._links.checkout.href and charges nobody: the payment starts open and only completes when the shopper pays, which is why it is a reversible write. Mollie: Create Customer Payment is the same call with the customer filled in, which is what lets a returning shopper reuse a stored card and what a recurring sequence needs. Mollie: Create Payment Link is the no checkout option, a shareable URL at data._links.paymentLink.href that a workflow or an agent can send; leave the amount blank and the payer enters one. Mollie: Update Payment edits description, URLs, metadata, method, locale, or due date on a payment that has not completed, and only the fields you fill are sent.

Refunds, and the one window to cancel one

Mollie: Create Payment Refund moves real money back to the shopper and there is no un refund, which is why it is flagged destructive. The amount can be lower than the original for a partial refund. Mollie executes refunds after a delay, and that delay is the only escape hatch: Mollie: Cancel Payment Refund works while the refund status is queued or pending and not after, and Mollie documents no way to reopen a canceled refund, so refunding again means creating a new one. Mollie: Get Payment Refund is what tells you which state you are in, and Mollie: List Payment Refunds shows everything already issued against a payment, which is the check that stops a workflow refunding the same order twice.

Recurring billing, mandate first

Recurring revenue in Mollie is a chain of three objects. Mollie: Create Customer makes the record, Mollie: Create Mandate records an authorization the customer has already given, which is why it is a reversible write that contacts nobody, and Mollie: Create Subscription bills against that mandate on a schedule. Only SEPA Direct Debit and PayPal mandates can be created directly; a card mandate comes from the shopper making a first payment. Mollie: List Mandates and Mollie: Get Mandate show whether an authorization is still valid, and the single get is the one to reach for when you need the details object, since Mollie's example list response returns it empty on the rows. Mollie: Update Subscription changes an active plan, and Mollie: Cancel Subscription is terminal, with no documented way to reactivate.

Reporting that needs the organization level token

Eleven nodes answer the finance questions and all eleven need an advanced access token rather than a profile API key. Mollie: List Settlements and Mollie: Get Settlement cover the payouts to your bank account with their revenue and cost breakdown per method, and Mollie: List Settlement Payments returns the payments inside one payout so a deposit can be matched to orders. Mollie: List Balances and Mollie: Get Balance give the position right now, available and pending; the lister takes no balance ID at all, since it returns every balance on the organization, and Mollie documents a separate primary balance endpoint for when the main one is all you want. Mollie: Get Balance Report summarizes a window and accepts the alias primary in place of a balance ID, with the from date inclusive, the until date exclusive, and both read in Central European Time, so a full month runs from the 1st to the 1st. Mollie: List Invoices and Mollie: Get Invoice read Mollie's own fee invoices, with a PDF link on the single get.

What stays off the canvas

Several Mollie surfaces are deliberately absent. The Orders API is not here because Mollie's own documentation no longer recommends it and points to Payments instead. The platform operator surfaces, clients, business accounts, balance transfers, routing, and capabilities, need partner or OAuth app credentials and describe a marketplace product rather than the merchant product this integration serves; the organization, profile, and onboarding reads that Mollie documents alongside them are here, since an advanced access token is all they ask for. Payouts, captures, and release authorization all move or release money and belong in a considered second pass rather than an unattended first one. Terminals and pairing codes are point of sale hardware, sessions need browser context the canvas does not have, and profile writes reshape a merchant's checkout configuration, which belongs in the dashboard. Webhook subscription management is also out: receiving events is the trigger layer's job, and the pattern for that is in the troubleshooting section below.

Troubleshooting

Test Connection fails with 401 Unauthorized Request
Mollie returns that title when the bearer token is missing or does not authenticate, so the failure is about the credential itself rather than the endpoint. Check for leading or trailing whitespace from the copy, confirm you pasted the key and not its label from the dashboard, and confirm the key has not been revoked since you saved it. Because Mollie shows a key once at creation, a half copied key cannot be compared against the original: create a new key, update the credential in Connectors, and revoke the old one. The keys live in the Mollie Web App under Developers, then API access tokens.
The settlement, balance, or invoice nodes fail while everything else works
That is the credential tier, not a broken node. Mollie gates eleven of the 45 nodes on an advanced access token, the organization level credential an Admin creates in the Mollie Web App, and a profile API key beginning test_ or live_ will not authenticate them however valid it is elsewhere. The affected nodes are Mollie: List Settlements, Mollie: Get Settlement, Mollie: List Settlement Payments, Mollie: List Balances, Mollie: Get Balance, Mollie: Get Balance Report, Mollie: List Invoices, Mollie: Get Invoice, Mollie: Get Current Organization, Mollie: List Profiles, and Mollie: Get Onboarding Status, and each says so in its own description. Store the access token as a second Mollie credential in Connectors and point those workflows at it.
A downstream step reads nothing from a list node
Mollie answers in HAL, so list rows are not at the top of the response: they sit under data._embedded plus a key named for the resource, such as data._embedded.payments[], data._embedded.customers[], or data._embedded.settlements[]. Single resources are flat instead, so a get node's fields read as data.id and data.amount.value with no envelope. Two keys catch people out: payment links are underscored at data._embedded.payment_links[], and Mollie's example mandate list response returns rows whose details object is empty, so read a mandate with Mollie: Get Mandate when you need the bank, card, or PayPal specifics.
A list node only returns the first 50 rows
That is Mollie's default page size, and the pagination is cursor based rather than numbered. Raise the limit up to the documented maximum of 250 rows per call, and for anything larger follow the cursor: the next page URL arrives at data._links.next.href and is null when the list is exhausted, and the from parameter takes the ID to start the next page at. Lists come back newest first unless a sort is available and set. The payment methods endpoints are the exception Mollie calls out itself: they are not paginated at all.
Cancel Payment Refund says the refund can no longer be canceled
Mollie only allows a refund to be canceled while its status is queued or pending. Once it moves to processing or refunded the money is on its way and the window is closed, and Mollie documents no way to reopen a canceled refund either, so a change of mind after that point means creating a new payment rather than undoing anything. Run Mollie: Get Payment Refund to read the status before attempting a cancel, and if a workflow needs a genuine grace period, hold the request in an approval task before Mollie: Create Payment Refund rather than trying to catch it afterwards.
A subscription charged sooner than expected
A Mollie subscription bills against a mandate the customer authorized earlier, so unlike a hosted checkout there is no shopper approval between the create call and a real charge. Mollie's reference pages do not state what the first charge date is when the start date is omitted, which is precisely why Mollie: Create Subscription is flagged destructive and its description tells you to set one. Always set an explicit start date, set times if the plan should end by itself, and keep the node behind an approval step. Cancelling afterwards stops future charges, and Mollie documents no refund of payments already collected, so treat those as a separate refund decision. The description must also be unique among that customer's active subscriptions or the create is rejected.
Recurring revenue stopped after a customer or mandate was removed
Both of those calls cascade, and Mollie documents it. Deleting a customer cancels all of that customer's mandates and all of their subscriptions with it, and revoking a mandate cancels every subscription connected to that mandate. Mollie documents no restore for either, so plan on the customer authorizing a new mandate and the subscriptions being created again rather than on recovering the originals. Past payments stay in the account's history either way. Both nodes are flagged destructive for this reason, so keep Mollie: Delete Customer and Mollie: Revoke Mandate out of unattended paths, or gate them behind an approval task that first runs Mollie: List Mandates and Mollie: List Customer Subscriptions so the person approving can see what will be canceled.
A cancel or delete node returns an empty data object
That is the vendor's response, not a lost result. Mollie declares no content for a successful cancel refund, delete customer, or revoke mandate, so those nodes report the 204 status with an empty data object and success is the status itself. Cancel payment and cancel subscription do return the updated object, so their output carries the new status. When a workflow needs proof of the outcome after a bodiless call, follow it with the matching read: Mollie: Get Payment Refund, Mollie: Get Customer, or Mollie: Get Mandate.
Nothing in Mattering reacts when a payment is paid
This integration is the outbound API surface and ships no Mollie trigger nodes, so nothing polls for status changes on its own. Let Mollie call Mattering instead. Mollie: Create Payment and Mollie: Update Payment both take a webhook URL, so point it at an inbound webhook trigger on a Mattering automation, and Mollie's status change will run that workflow, which can then call Mollie: Get Payment to read the authoritative state rather than trusting the payload. One documented quirk while building the loop: updating a payment does not itself trigger a webhook call, so do not expect an update to echo back.
Get Payment Method returns 404 or 403 for a method you expected
Mollie separates those two answers deliberately, and both are informative. A 404 means the method is not available on the profile at all, and a 403 means it is available but not yet enabled, which makes this the right check before offering a method in a checkout. Mollie: List Payment Methods returns what the profile can actually use today, and Mollie: List All Payment Methods returns Mollie's wider catalog including methods the organization is not eligible for, which is why the method pickers in this integration source the enabled lister rather than the full one.

Mollie is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products