Adyen API
- Checkout API v72
- Payments API v68
- Payouts API v68
- Recurring API v68
- Management API v3
- Transfers API v4
Vendor coverage
Adyen API changes & breaking changes
Adyen splits its platform into per-service contracts (Checkout, Payments, Payouts, Recurring, Management, Transfers), each versioned on its own. Detektu diffs every published revision, because an unnoticed contract change in a payment flow is revenue at risk.
Last checked Oct 20, 2026, 4:00 PMLast change detected Oct 20, 2026, 3:54 PM
Detected changes
Latest Adyen API changes
Every entry is a change Detektu detected in Adyen's published contracts, with exact before/after evidence on its page.
No breaking changes on record yet.
Coverage
What Detektu monitors
Official products and contracts checked for changes.
Change model
How Adyen ships changes
The release patterns that shape your integration risk.
Adyen publishes an OpenAPI contract per service and revs major versions deliberately (Checkout is at v72), but within a version the contracts still move. New payment methods extend enums, request validation tightens, response objects grow. Payment integrations exercise a narrow, business-critical slice of that surface.
Detektu reports each change with the exact service, operation, and property coordinate, so a tightened request schema on a call your checkout makes escalates, while additions to services you don't use stay informational.
From change to finding
Findings you'd see
Illustrative examples. Every real finding carries exact before/after evidence, severity, and source provenance.
Request field constraint tightened on payment sessions
openapi:POST /sessions ::amount.valueNew payment method type in the checkout enum
openapi:POST /payments ::paymentMethod.typeMonitored for you
Do Adyen's changes affect your integration?
Choose the operations and fields your services use. Detektu matches Adyen findings to that declared usage so your team can review the relevant evidence. No agent or repository access required.