API discoveries

Comparison of Adyen Checkout API, Checkout Utility Service, Data Protection API, and Payment API

A practical comparison of the four Adyen API specifications captured on 2026-09-20, outlining their reported purposes, authentication, versioning, functional differences, and suggested next steps for evaluation based solely on the supplied records.

AltAPIs Editorial · AI-assisted · automatically published after software checks; not human-reviewed

Bitcoin Cryptocurrency Security. Topic illustration; not a screenshot or endorsement of the products discussed. File:Bitcoin Cryptocurrency Security.jpg by Edwin.images · CC BY-SA 4.0. Wikimedia thumbnail resize only; image remains under its original license.

Observation Context

All four API specifications were observed on 2026-09-20T17:39:44.601Z via the APIs.guru repository. The records show identical observedAt and firstSeenAt timestamps: Adyen Checkout Service (v70), Checkout Utility Service (v1), Data Protection Service (v1), and Payment Service (v68). No additional metadata such as stars, forks, or download counts is present in the supplied data, so any inference about adoption or popularity would be unsupported.

Reported Purposes from Descriptions

Checkout API description: "Adyen Checkout API provides a simple and flexible way to initiate and authorise online payments. You can use the same integration for payments made with cards (including 3D Secure), mobile wallets, and local payment methods (for example, iDEAL and Sofort)." Checkout Utility Service description: "A web service containing utility functions available for merchants integrating with Checkout APIs." Data Protection API description: "Adyen Data Protection API provides a way for you to process Subject Erasure Requests as mandated in GDPR. Use our API to submit a request to delete shopper's data, including payment details and other related information (for example, delivery address or shopper email)." Payment API description: "A set of API endpoints that allow you to initiate, settle, and modify payments on the Adyen payments platform. You can use the API to accept card payments (including One-Click and 3D Secure), bank transfers, ewallets, and many other payment methods."

Authentication Mechanisms

Each service requires an API key passed in the X-API-Key header. The Checkout API example shows: "curl -H \"Content-Type: application/json\" \ -H \"X-API-Key: YOUR_API_KEY\" ...". The Checkout Utility Service uses the same pattern with an API key from the Customer Area. The Data Protection API likewise instructs to set the key to X-API-Key. The Payment API adds an alternative: basic authentication using username and password, exemplified by "curl -U \"ws@Company.YOUR_COMPANY_ACCOUNT:\"YOUR_BASIC_AUTHENTICATION_PASSWORD\" -H \"Content-Type: application/json\" ...". All services note that a new API key is needed for live endpoints.

Versioning Approach

All four APIs version endpoints via a URL suffix "vXX" where XX is the version number. Checkout API uses v70 (example: https://checkout-test.adyen.com/v70/payments). Checkout Utility Service uses v1 (example: https://checkout-test.adyen.com/v1/originKeys). Data Protection API uses v1 (example: https://ca-test.adyen.com/ca/services/DataProtectionService/v1/requestSubjectErasure). Payment API uses v68 (example: https://pal-test.adyen.com/pal/servlet/Payment/v68/authorise). Going live requires replacing the test subdomain with a live prefixed URL unique to the merchant account.

Functional Differences Inferred from Descriptions

Checkout API centers on payment initiation and authorization for cards, mobile wallets, and local methods such as iDEAL and Sofort. Checkout Utility Service provides auxiliary functions (e.g., retrieving origin keys) that support Checkout integration but do not process payments themselves. Data Protection API is scoped to GDPR compliance, specifically enabling submission of shopper data erasure requests and deletion of associated information. Payment API covers the broader payment lifecycle: initiation, settlement, modification, and supports additional methods like bank transfers and e‑wallets, as well as One‑Click and 3D Secure flows. These distinctions imply Checkout API is suited for front‑end payment forms, Utility for integration helpers, Data Protection for compliance workflows, and Payment API for back‑end settlement and reconciliation tasks.

Limitations of the Sample and Suggested Next Steps

The supplied records contain only high‑level description, authentication, and versioning fields; they do not include the full OpenAPI paths, request/response schemas, error definitions, rate limits, or security schemes. Consequently, we cannot evaluate endpoint coverage, data model compatibility, idempotency guarantees, or webhook capabilities from this sample alone. To proceed, one should retrieve the complete specifications from the same URLs to enumerate all available operations, examine concrete payloads, and compare specifics such as supported payment methods, version‑specific behavior, and any required headers beyond X‑API-Key.