Adyen Managed Payouts fixtures

Adyen Managed Payouts integration cases without live payments.

Use 5 source-linked synthetic scenarios to test success, failure, delayed, dispute or mandate behavior around a provider adapter. The fixture contract is explicit about sandbox-only use.

Open the workflow Read API docs
Scope: Synthetic and sandbox-only. This page documents QA and integration workflows; it does not claim live account verification or production payment execution.

Use it in three steps

2. Export for CI

Paid API access can export the provider matrix as JSON or CSV under plan limits.

Explore export for ci →

Sources and freshness

Provider documentation

Open the documented source or runtime contract before relying on this workflow.

View source →Page evidence checked 2026-07-10

Questions teams ask

Do these fixtures charge a real Adyen Managed Payouts payment method?

No. They are synthetic or provider-sandbox examples for QA and contract testing. Never submit them to a live payment flow.

What is included in a provider fixture?

Depending on the provider, rows can include scenario, sandbox routing/account number or IBAN, token, expected status, webhook and source context.

Can I request a provider not listed here?

Yes. Use the Business intake to submit a bounded provider and scenario list; coverage is reviewed before any implementation or commercial promise.

Availability and source coverage are bounded by the current registry, fixture catalog and plan entitlements. If a target is not matched, IBANgen reports that state instead of inventing authoritative coverage.