Free setup on ROLLER Integration Packs until 31 August 2026. Use code ROLLER826. Check out ROLLER Integration Packs
← All connectors
Adyen Partner Connector

Connect Adyen Without Constraints

IntelliPaaS seamlessly connects Adyen with your core business systems, enabling no-code integration for payments, settlement reconciliation and terminal estate management across cloud, on-prem and hybrid environments.

Adyen ships its MCP server as a local package rather than a hosted endpoint, and it is explicitly alpha — still on a 0.x release line, with coverage limited to the Checkout and Management APIs while more are added. Authentication is by API key, and scoping is done through Adyen's webservice user roles, sixteen of them, covering everything from payment methods and terminals to webhooks and API credentials. Adyen's own recommendation is to create a dedicated webservice user with a fresh key and grant only the roles the enabled tools need, and the server supports loading a subset of tools explicitly. Test is the default environment; live requires your live URL prefix, which is region and merchant specific. Because the tool set includes cancels and refunds, IntelliPaaS runs Adyen operations behind approval steps and environment guards by default.

Adyen integration capabilities

  • Create and read checkout sessions and retrieve available payment methods.
  • Create, read and expire payment links.
  • Issue cancels and refunds against existing payments.
  • Read merchant accounts, users, API credentials and allowed origins.
  • Manage the terminal estate — list, reassign, schedule actions and patch settings.
  • List, read and test webhooks across company and merchant accounts.

These capabilities let payments be initiated, tracked and reconciled from the systems that own the order, rather than from the payments dashboard. IntelliPaaS handles field mapping, currency handling and data type transformation automatically.

Common integration scenarios

  • Create a checkout session or payment link directly from an order in Shopify, BigCommerce or Adobe Commerce.
  • Reconcile Adyen settlements against invoices in NetSuite, Xero or QuickBooks.
  • Issue a refund in Adyen when a return is approved in the commerce or support system.
  • Keep terminal assignments and settings in step with store and location records.
  • Monitor webhook configuration across merchant accounts and alert on drift.

These scenarios address the most common friction in payment operations — settlements reconciled by hand, refunds raised in two systems, terminal estates managed one device at a time — by automating the flows between Adyen and the platforms around it.

Deployment & security

Flexible deployment is essential for organisations operating in regulated industries or jurisdictions with strict data residency requirements. IntelliPaaS supports private cloud and on-premise deployments with full regional data sovereignty, and Adyen's live URL prefix keeps traffic on your own region-specific endpoint. All deployment modes receive the same feature set, connector library and support tier, with no capability trade-offs based on deployment choice.

Deployment mode
Data residency
Features
Best for
Cloud (SaaS)
Shared cloud
Full
SMB / mid-market, speed
Private Cloud
Customer VPC
Full
Regulated industries
On-Premise
Customer infra
Full
Data sovereignty, finance, healthcare
No capability trade-offs based on deployment choice.
GDPR-readyEncryption in transit and at restFull regional data residency

Why IntelliPaaS

  • No-code to pro-code flexibility for all integration needs.
  • End-to-end security with dedicated webservice users, role-scoped API keys and tool allowlisting.
  • Approval steps and environment guards on money-moving operations such as cancels and refunds.
  • Enterprise-grade observability with monitoring, alerting and audit logging.

Frequently connected apps

FAQ

Frequently asked questions

What authentication does the connector use?

An Adyen API key, scoped through webservice user roles — sixteen of them across payments, terminals, webhooks and credentials. Adyen recommends a dedicated webservice user with a fresh key, granted only the roles the enabled tools actually need.

How mature is the Adyen MCP server?

It is alpha, still on a 0.x release line, and coverage is currently the Checkout and Management APIs with more being added. Because the tools include cancels and refunds, IntelliPaaS runs them behind approval steps and environment guards.

Does it work against live payments?

Yes. Test is the default environment; live requires your live URL prefix, which is region and merchant specific. We recommend proving flows in test with an explicit tool allowlist before enabling live.

Can I deploy on-premise or in a private cloud?

Yes. Cloud (SaaS), private cloud in your own VPC, and fully on-premise or air-gapped deployments are all supported, with full feature parity across every mode.

Is my data secure?

Data is encrypted in transit and at rest, and IntelliPaaS is GDPR-ready. Role-scoped keys and tool allowlisting limit what any agent can reach, and on-prem modes keep payment orchestration inside your own infrastructure boundary.

Ready to connect Adyen to your stack?

Our team will map your exact integration scenario, usually in a 30-minute session.