canonical: https://jentic.com/apis/mollie.com/mollie # Mollie Payments API Jentic publishes the only available OpenAPI specification for Mollie Payments API, keeping it validated and agent-ready. Mollie is a European payment service provider that supports iDEAL, credit cards, SOFORT, Bancontact, gift cards, SEPA Direct Debit, and many other regional methods popular across the Netherlands, Belgium, Germany, and France. The API exposes payment creation, listing, retrieval, cancellation, refunds, and customer management plus a methods endpoint for surfacing locally relevant payment options at checkout. It targets European e-commerce merchants who need iDEAL and Bancontact alongside cards in a single integration. ## For AI agents Process European payments including iDEAL, Bancontact, SOFORT, and credit cards, manage customers, and issue refunds through Mollie's payment platform. ## Scope Does not handle accounting, tax filing, or payroll - use for European payment processing, refunds, and customer payment record management only. ## Capabilities - Create iDEAL, Bancontact, SOFORT, and credit card payments through a single endpoint - List or retrieve historical payments by ID for reconciliation - Cancel pending payments before the customer completes them - Issue full or partial refunds against completed payments - Manage customer records and list available payment methods for a checkout ## Use cases ### European E-Commerce Checkout with iDEAL and Bancontact Accept payments from Dutch and Belgian customers using their preferred local methods through a single Mollie integration. Calling POST /payments with method='ideal' or 'bancontact' returns a hosted checkout URL that handles the bank redirect flow, removing the need to integrate iDEAL or Bancontact directly. Suitable for European merchants where local methods convert significantly better than card-only checkouts. Example prompt: Call POST /payments with amount, currency=EUR, method=ideal, and a redirectUrl, then poll GET /payments/{id} until status becomes paid. ### Refund Processing for Customer Service Issue full or partial refunds against completed Mollie payments using the refunds endpoint, then list refunds for audit and reconciliation. The refund flow handles bank-side return for iDEAL and Bancontact transactions automatically, which manual bank-transfer refunds do not. Useful for customer service teams operating at scale where refund speed directly affects support metrics. Example prompt: Call POST /payments/{paymentId}/refunds with the refund amount to issue a partial refund, then GET /payments/{paymentId}/refunds to confirm it was recorded. ### Dynamic Payment Method Selection at Checkout Call GET /methods to retrieve the payment methods that are active and locally relevant for the customer, so the checkout shows iDEAL to Dutch shoppers and Bancontact to Belgian shoppers without hardcoding logic. The methods endpoint accepts amount and locale filters, so pricing-sensitive methods like SEPA Direct Debit only appear when eligible. Practical for international merchants serving multiple European markets. Example prompt: Call GET /methods with the cart amount and customer locale to return the methods to render in the checkout UI. ### Agent-Driven Payment Reconciliation AI agents handling finance-ops queries call Mollie through Jentic to list payments, retrieve specific transaction details, and issue refunds without holding the bearer token in their context. Jentic's spec is the only structured definition for Mollie that the agent can use for schema-driven tool selection. Example prompt: Search Jentic for 'list recent mollie payments', load GET /payments, and execute with a date filter to feed the reconciliation worksheet. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /payments | Create a payment using iDEAL, Bancontact, card, or other methods | | GET | /payments | List historical payments | | GET | /payments/{id} | Retrieve a specific payment | | DELETE | /payments/{id} | Cancel a pending payment | | POST | /payments/{paymentId}/refunds | Issue a refund against a payment | | GET | /payments/{paymentId}/refunds | List refunds on a payment | | POST | /customers | Create a customer record | | GET | /methods | List payment methods available for a checkout | ## Key resources - **Payments** — Create, list, retrieve, and cancel payments across European methods - **Refunds** — Issue full or partial refunds and list refund history per payment - **Customers** — Create and retrieve customer records for recurring use - **Methods** — List payment methods available for a given amount and locale ## Why Jentic - **Setup:** Wiring the Mollie Payments API by hand means managing its bearer key, handling European payment method quirks, and coding the payment, refund, and customer calls yourself. Through Jentic you install once, import the Mollie Payments API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** Mollie puts the payment id in the URL path (/payments/{id}, /payments/{paymentId}/refunds), so a rule can pin your agent to one payment and the operations on it. You choose the operations it may call, so a destructive one like cancelling a payment is not included unless you add it. - **Credential handling:** Your Mollie key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an iDEAL payment' or 'refund a payment', and Jentic returns the matching Mollie operation with its schema for amount, method, and redirect URL so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Stripe API** — Global payment processing platform with broad card and wallet coverage - **Adyen Checkout API** — Enterprise European payment processor with strong local-method coverage and unified ledger - **Braintree API** — PayPal-owned payments platform with PayPal, Venmo, and card support ## FAQ ### Why is there no official OpenAPI spec for Mollie Payments API? Mollie does not publish an OpenAPI specification in a structured format suitable for agent tool calling. Jentic generates and maintains this spec so that AI agents and developers can call Mollie Payments API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Mollie Payments API use? Mollie uses HTTP Bearer authentication with API keys prefixed test_ or live_ depending on the environment. Send the key as Authorization: Bearer . Through Jentic, the API key is held encrypted in the credential vault and injected at request time so the secret never appears in agent context. ### Can I accept iDEAL payments with the Mollie Payments API? Yes. Call POST /payments with method='ideal', the amount in EUR, and a redirectUrl, and Mollie returns a checkout URL that handles the bank-selection and redirect flow. After the customer completes payment, GET /payments/{id} confirms the final status. ### What are the rate limits for the Mollie Payments API? Mollie applies per-account rate limits documented in their developer portal (https://docs.mollie.com). Practical throughput is sufficient for normal e-commerce traffic; bulk operations such as historical payment imports should use pagination on GET /payments rather than parallel requests. ### How do I issue a refund through Jentic? Run pip install jentic, search for 'issue a mollie refund', load POST /payments/{paymentId}/refunds, and execute with the original payment ID and the refund amount. Jentic returns the refund object so the agent can confirm the refund was created. ### Does Mollie support recurring payments? Mollie supports recurring payments via the customers and SEPA Direct Debit flow. Create a customer record, then create payments tied to that customer with the recurring sequenceType. The customer endpoint in this spec lets you manage the customer-side records that recurring payments depend on. ### Can I limit what my agent is allowed to do with the Mollie Payments API? Yes. Jentic One runs self-hosted, so your own rules decide which Mollie operations and credentials the agent may use. Because Mollie carries the payment id in the URL path (/payments/{id}, /payments/{paymentId}/refunds), a rule can pin the agent to a single payment and only the calls you permit against it. You choose the operations it can reach, so a destructive one like DELETE /payments/{id} to cancel a payment stays off unless you add it.