Can AI agents automate Adyen?

Adyen is automatable today through its documented HTTPS APIs. Checkout API v72 at https://checkout-test.adyen.com/v72 initiates and authorises online payments, including sessions, payment methods, payment links, captures, refunds, and stored-payment tokens. Management API v3 at https://management-test.adyen.com/v3 configures company and merchant accounts, stores, terminals, webhooks, users, and API credentials. The API Explorer also lists payouts, classic Payments, in-person/terminal operations, Adyen for Platforms, issuing, and transfers. Each request authenticates with an API key in the x-API-key header or HTTP Basic credentials generated in Customer Area. Live Checkout URLs require a company-specific prefix from the live Customer Area. Official server libraries exist for Java, PHP, .NET, Node.js, Go, Python, and Ruby. Adyen publishes OpenAPI specifications and HMAC-signed HTTPS webhooks (JSON, HTTP POST, or SOAP delivery). Scheduled reports download as CSV over authenticated GET. The first-party MCP server is documented as alpha: npx -y @adyen/mcp with an API key, covering Checkout API and Management API tools only. Live MCP also needs the live URL prefix. Production use requires an Adyen merchant account, role-scoped API credentials, and PCI-aware handling of money-moving operations. Zapier, Make, Power Automate, and n8n catalogs were not opened. A general-purpose Adyen CLI was not established. Computer-use viability is unassessed. API scores 8 and is the best path because MCP remains alpha and limited to two API families.

Best path today: api · Overall automatability: 8/10