Netherlands Payments (Mollie — iDEAL)

Official7 tools

by junter1989k-ai · JavaScript

Netherlands payments for AI agents — iDEAL via Mollie. Never holds funds.

app.wishpool/netherlands-payments-mcp — Netherlands Payments MCP

This MCP server provides Netherlands payments for AI agents using iDEAL via Mollie. It is designed so the service does not hold funds. When credentials are needed, they are sent as HTTP headers on each request and are not stored. The server exposes 7 tools.

🛠️ Key Features

Netherlands payments for AI agents
iDEAL via Mollie
Never holds funds
Credentials passed via HTTP headers; not stored

🚀 Use Cases

Enable AI agents to accept payments in the Netherlands
Use in any MCP-capable agent (e.g., Claude Desktop, Cursor, Windsurf)

⚡ Developer Benefits

No installation required
Simple MCP client configuration using an HTTP server URL
Threat model documentation referenced for trust details

⚠️ Limitations

Documentation excerpt does not specify which specific operations are covered by the 7 tools.

Topics

ai-agentsmcpmcp-servermolliepaymentsai-agentclaudenetherlandswishpool

Captured live from the server via tools/list.

create_payment_link

Create a payment link in EUR for the Netherlands via Mollie. Buyer pays with iDEAL (the rail Dutch buyers actually use), cards, Bancontact, and other methods enabled on the Mollie account. Returns a hosted checkout URL the buyer opens to pay — payment completes automatically, no confirm step. Bring your own credentials via HTTP header (x-mollie-api-key; free test credentials from my.mollie.com never move real money). Money always flows buyer→Mollie→merchant; this service never touches funds.

Parameters4

amount_eur	number	required	Amount in EUR (decimals allowed), e.g. 10. Minimum 1.
description	string	required	What this payment is for (shown to the buyer, ≤200 chars)
customer_email	string	optional	Optional buyer email.
success_url	string	optional	Optional https URL to send the buyer to after payment.

Raw schema

{
  "type": "object",
  "properties": {
    "amount_eur": {
      "type": "number",
      "minimum": 1,
      "maximum": 1000000,
      "description": "Amount in EUR (decimals allowed), e.g. 10. Minimum 1."
    },
    "description": {
      "type": "string",
      "description": "What this payment is for (shown to the buyer, ≤200 chars)"
    },
    "customer_email": {
      "type": "string",
      "description": "Optional buyer email."
    },
    "success_url": {
      "type": "string",
      "description": "Optional https URL to send the buyer to after payment."
    }
  },
  "required": [
    "amount_eur",
    "description"
  ]
}

query_payment_status

Check whether a the Netherlands payment (created by create_payment_link) has been paid. Queries Mollie directly — pull-based, no webhook needed. paid=true when status is PAID.

Parameters1

payment_id

string

required

The payment_id (tr_...) returned by create_payment_link

Raw schema

{
  "type": "object",
  "properties": {
    "payment_id": {
      "type": "string",
      "description": "The payment_id (tr_...) returned by create_payment_link"
    }
  },
  "required": [
    "payment_id"
  ]
}

refund_payment

Refund a paid payment (created by create_payment_link). Full refund by default; pass amount for a partial refund where supported. Refunds respect the same owner policy guardrails (x-agentpay-max-amount) as payments — the amount is checked before anything is sent to the gateway.

Parameters2

payment_id	string	required	The payment_id of the paid payment (same id used by query_payment_status)
amount	number	optional	Optional partial-refund amount in the local currency major unit. Omit for a full refund.

Raw schema

{
  "type": "object",
  "properties": {
    "payment_id": {
      "type": "string",
      "description": "The payment_id of the paid payment (same id used by query_payment_status)"
    },
    "amount": {
      "type": "number",
      "description": "Optional partial-refund amount in the local currency major unit. Omit for a full refund."
    }
  },
  "required": [
    "payment_id"
  ]
}

create_subscription_link

Create a recurring subscription in EUR for the Netherlands via Mollie (SEPA Direct Debit set up via iDEAL, cards, PayPal — whatever recurring methods are enabled on the Mollie account). Mollie recurring is a two-step, honest flow (there is no single call that returns a ready subscription, because the buyer must authorize a mandate first): this tool creates a Mollie customer and a FIRST payment (sequenceType=first) and returns a hosted checkout URL. The buyer opens it once and pays — that first payment IS the first billing period AND authorizes the mandate. Then call activate_subscription with the returned customer_id and payment_id to start the recurring plan for the remaining periods. amount_eur is charged PER billing period. Requires x-mollie-api-key. Respects the same owner policy guardrails (x-agentpay-max-amount / x-agentpay-approval-above) as payments — the per-period amount is checked before anything is created. Money always flows buyer→Mollie→merchant; this service never touches funds.

Parameters8

amount_eur	number	required	Amount charged PER billing period, in EUR (decimals allowed), e.g. 9.99. Minimum 1.
description	string	required	What the subscription is for (shown to the buyer; also used as the Mollie subscription description, ≤200 chars).
period	string	optional	Billing period. Default "monthly".
interval	integer	optional	Charge every N periods (period=monthly, interval=3 = every 3 months). Default 1. (Yearly is billed as 12-month intervals; interval multiplies that.)
total_count	integer	optional	Total number of billing periods to charge, INCLUDING the first payment (e.g. 12 monthly = one year). Omit for an open-ended subscription that renews until cancelled.
customer_name	string	optional	Optional buyer name (stored on the Mollie customer).
customer_email	string	optional	Optional buyer email (Mollie sends receipts there).
success_url	string	optional	Optional https URL to send the buyer to after they authorize/pay the first payment.

Raw schema

{
  "type": "object",
  "properties": {
    "amount_eur": {
      "type": "number",
      "minimum": 1,
      "maximum": 1000000,
      "description": "Amount charged PER billing period, in EUR (decimals allowed), e.g. 9.99. Minimum 1."
    },
    "description": {
      "type": "string",
      "description": "What the subscription is for (shown to the buyer; also used as the Mollie subscription description, ≤200 chars)."
    },
    "period": {
      "type": "string",
      "enum": [
        "monthly",
        "yearly",
        "weekly",
        "daily"
      ],
      "description": "Billing period. Default \"monthly\"."
    },
    "interval": {
      "type": "integer",
      "minimum": 1,
      "description": "Charge every N periods (period=monthly, interval=3 = every 3 months). Default 1. (Yearly is billed as 12-month intervals; interval multiplies that.)"
    },
    "total_count": {
      "type": "integer",
      "minimum": 1,
      "maximum": 1000,
      "description": "Total number of billing periods to charge, INCLUDING the first payment (e.g. 12 monthly = one year). Omit for an open-ended subscription that renews until cancelled."
    },
    "customer_name": {
      "type": "string",
      "description": "Optional buyer name (stored on the Mollie customer)."
    },
    "customer_email": {
      "type": "string",
      "description": "Optional buyer email (Mollie sends receipts there)."
    },
    "success_url": {
      "type": "string",
      "description": "Optional https URL to send the buyer to after they authorize/pay the first payment."
    }
  },
  "required": [
    "amount_eur",
    "description"
  ]
}

activate_subscription

Second step of the Mollie subscription flow. After the buyer has opened the create_subscription_link URL and paid the first payment (which authorizes the mandate), call this with the customer_id and payment_id that create_subscription_link returned. If the mandate is now valid it creates the recurring subscription (for the periods after the first payment) and returns subscription_id (sub_...). If the buyer has NOT finished authorizing yet, it does NOT error — it returns activated=false with a readable mandate_status so you can keep polling (call query_subscription, wait ~20s, then call activate_subscription again). Idempotent: if the subscription already exists it returns the existing one. The plan parameters (amount / period / interval / total_count) were stored on the first payment, so you do not re-supply them here.

Parameters2

customer_id	string	required	The customer_id (cst_...) returned by create_subscription_link.
payment_id	string	required	The payment_id (tr_...) returned by create_subscription_link (it carries the stored plan parameters).

Raw schema

{
  "type": "object",
  "properties": {
    "customer_id": {
      "type": "string",
      "description": "The customer_id (cst_...) returned by create_subscription_link."
    },
    "payment_id": {
      "type": "string",
      "description": "The payment_id (tr_...) returned by create_subscription_link (it carries the stored plan parameters)."
    }
  },
  "required": [
    "customer_id",
    "payment_id"
  ]
}

query_subscription

Check a the Netherlands subscription. Pass customer_id alone for an overview: status AWAITING_AUTHORIZATION (buyer has not authorized the mandate yet — keep polling / call activate_subscription), MANDATE_VALID (buyer authorized; call activate_subscription now to start the recurring plan), or ACTIVE (a subscription is running; subscription_id is returned). Pass customer_id AND subscription_id (sub_...) to check one subscription directly: ACTIVE | PENDING | CANCELED | SUSPENDED | COMPLETED, with next_charge_date. Pull-based — no webhook needed.

Parameters2

customer_id	string	required	The customer_id (cst_...) returned by create_subscription_link.
subscription_id	string	optional	Optional subscription_id (sub_...) from activate_subscription to check one subscription directly. Omit for a mandate + subscription overview.

Raw schema

{
  "type": "object",
  "properties": {
    "customer_id": {
      "type": "string",
      "description": "The customer_id (cst_...) returned by create_subscription_link."
    },
    "subscription_id": {
      "type": "string",
      "description": "Optional subscription_id (sub_...) from activate_subscription to check one subscription directly. Omit for a mandate + subscription overview."
    }
  },
  "required": [
    "customer_id"
  ]
}

cancel_subscription

Cancel a the Netherlands subscription so it stops charging. Pass the customer_id (cst_...) and the subscription_id (sub_...) from activate_subscription / query_subscription. Mollie cancellation is immediate — no further billing periods are charged. (If the buyer never authorized the mandate, there is nothing to cancel; just let the first payment expire.)

Parameters2

customer_id	string	required	The customer_id (cst_...) the subscription belongs to.
subscription_id	string	required	The subscription_id (sub_...) to cancel — get it from activate_subscription or query_subscription.

Raw schema

{
  "type": "object",
  "properties": {
    "customer_id": {
      "type": "string",
      "description": "The customer_id (cst_...) the subscription belongs to."
    },
    "subscription_id": {
      "type": "string",
      "description": "The subscription_id (sub_...) to cancel — get it from activate_subscription or query_subscription."
    }
  },
  "required": [
    "customer_id",
    "subscription_id"
  ]
}

README.md3 KBView on GitHub

Netherlands Payments MCP — let AI agents accept payments in Netherlands

Use it in 60 seconds

Paste this into your MCP client config (Claude Desktop, Cursor, Windsurf, or any MCP-capable agent):

json

{
  "mcpServers": {
    "netherlands-payments": {
      "type": "http",
      "url": "https://mcp-nl.wishpool.app/mcp"
    }
  }
}

Nothing to install. Credentials, when you need them, travel as HTTP headers on each request and are never stored — see the threat model.

Or run it yourself

Would you rather not send production credentials to a server you do not control? Deploy this identical code to your own account and point your agent at your own URL:

bash

git clone https://github.com/junter1989k-ai/netherlands-payments-mcp && cd netherlands-payments-mcp && npx vercel --prod

MIT-licensed. Self-hosting removes us from the picture entirely, at no cost and with no loss of function.

Live · MCP endpoint: https://mcp-nl.wishpool.app/mcp · Listed on the official MCP Registry as app.wishpool/netherlands-payments-mcp · Part of a 20-country family — hub: mcp.wishpool.app

A remote MCP server that lets any AI agent (Claude, ChatGPT, Cursor…) accept payments in Netherlands: iDEAL (the rail Dutch buyers actually use), cards, Bancontact, and other methods enabled on the Mollie account — via Mollie's hosted checkout.

⚖️ Stateless translation layer: funds always flow buyer → Mollie → merchant directly. Never holds funds or stores credentials — no database at all.

Quick start

MCP endpoint: https://mcp-nl.wishpool.app/mcp (Streamable HTTP, stateless JSON-RPC)

Header	Value
`x-mollie-api-key`	your Mollie API key (test_ = test mode from my.mollie.com, live_ = production)

Tools

Tool	What it does
`create_payment_link`	Create a EUR hosted-checkout link.
`query_payment_status`	Pull-based status check; `paid=true` when PAID.

Develop

bash

node test/serve.js      # local server (http://localhost:3228/mcp)
node test/e2e.js        # protocol + validation suite (probes real Mollie auth errors)

Zero runtime dependencies; Node ≥ 18. MIT license.

Install

Tools (7)

create_payment_linkquery_payment_statusrefund_paymentcreate_subscription_linkactivate_subscriptionquery_subscriptioncancel_subscription

Remote endpoint

Streamable HTTP

Hosted server - connect over the network, no local install.

url

https://mcp-nl.wishpool.app/mcp

Add to VS Code Add to Cursor

claude_desktop_config.json

json

{
  "mcpServers": {
    "netherlands-payments-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp-nl.wishpool.app/mcp"
      ]
    }
  }
}

Desktop config is stdio-only; this bridges via mcp-remote. Native remote: Settings > Connectors.

app.wishpool/netherlands-payments-mcp — Netherlands Payments MCP

🛠️ Key Features

🚀 Use Cases

⚡ Developer Benefits

⚠️ Limitations

Topics

create_payment_link

query_payment_status

refund_payment

create_subscription_link

activate_subscription

query_subscription

cancel_subscription

Netherlands Payments MCP — let AI agents accept payments in Netherlands

Use it in 60 seconds

Or run it yourself

Quick start

Tools

Develop

Install

Remote endpoint

Related servers