Belgium Payments (Mollie — Bancontact) MCP server

Create a payment link in EUR for Belgium via Mollie. Buyer pays with Bancontact (the rail Belgian buyers actually use), cards, 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.

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

Create a recurring subscription in EUR for Belgium via Mollie (Bancontact / SEPA Direct Debit, 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.

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.

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.

Cancel a Belgium 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.)

Check a Belgium 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.