OVERALL CONTROL / 0.6-customer-control
Grades and scoring
Data access
25% of the overall score before applicability adjustment.
Scored answers and evidence
Read interface 2.5/10
Report outputs only
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
The assessed read route delivers generated merchant report files, not an arbitrary transaction query interface.
Get reports automatically ↗
Step 2: Set up REPORT_AVAILABLE notifications; Step 5: Download reports · Checked 2026-10-16
Bulk delivery 8.8/10
Batched or iterable API requests
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Automated authenticated file downloads provide batched report retrieval, qualified by report type and period.
Get reports automatically ↗
Step 5: Download reports · Checked 2026-10-16
Query expressiveness 7.5/10
Fixed object or report retrieval
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Retrieve a generated report from its notified URL; arbitrary external predicates are not established.
Get reports automatically ↗
Step 2: Set up REPORT_AVAILABLE notifications; Step 5: Download reports · Checked 2026-10-16
Access cost barrier -
-
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
The lowest eligible paid plan and route-specific fixed API charges have not been established.
API credentials ↗
API credentials; Requirements; Configure API permissions · Checked 2026-10-16
Third-party accessibility
20% of the overall score before applicability adjustment.
Scored answers and evidence
Third-party eligibility -
-
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
API credentials ↗
API credentials; Requirements; Configure API permissions · Checked 2026-10-16
Downstream permission -
-
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
API credentials ↗
API credentials; Requirements; Configure API permissions · Checked 2026-10-16
External action
15% of the overall score before applicability adjustment.
Scored answers and evidence
Write interface 2.5/10
Named operations in a limited domain
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
A captured-payment refund operation and Idempotency-Key are documented; broad create/update is not inferred.
Refund a captured payment ↗
Refund a captured payment; Request Parameters; Header Parameters · Checked 2026-10-16
Custom application path 10.0/10
Customer applications using fixed APIs without provider selection
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Customers configure their own role-scoped integration credentials; chosen-third-party distribution remains unresolved.
API credentials ↗
API credentials; Multiple API credentials · Checked 2026-10-16
Continuity
15% of the overall score before applicability adjustment.
Scored answers and evidence
Refresh mechanism 5.0/10
Scheduled feeds or recurring extracts
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Recurring report generation and report-ready notifications support repeated extraction.
Get reports automatically ↗
Step 1: Set up automatic report generation; Step 2: Set up REPORT_AVAILABLE notifications · Checked 2026-10-16
Limit visibility -
-
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Numeric request quotas and recovery instructions have not been established.
API credentials ↗
API credentials; Requirements; Configure API permissions · Checked 2026-10-16
CDC and deletion capture 2.5/10
Full snapshots permit customer reconciliation; native deltas unverified
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Repeat a selected report scope for reconciliation; this does not establish complete tombstone or update coverage.
Get reports automatically ↗
Step 1: Set up automatic report generation; Step 5: Download reports · Checked 2026-10-16
Replay and gap recovery 2.5/10
Rebuild from a fresh snapshot; no historical replay established
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
The Customer Area can regenerate the supported merchant/type/date selection, including reports whose generated file has expired. This rebuilds selected reporting output, not deleted payloads or a retained event checkpoint.
Generate and download reports manually ↗
Manually generate and download a report; report-retention introduction · Checked 2026-10-16
Get reports automatically ↗
Step 5: Download reports · Checked 2026-10-16
Data exit
20% of the overall score before applicability adjustment.
Scored answers and evidence
Export custody 7.5/10
Customer-held structured files or API records
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Merchant report files can be downloaded and retained externally; selected PGP encryption is supported.
Get reports automatically ↗
Step 4 (Optional): Encrypt report files; Step 5: Download reports · Checked 2026-10-16
Post-cancellation access Disclosure
-
Disclosure only; does not reduce planned-exit credit.
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
A customer cancellation retrieval window and any exit charges have not been established.
API credentials ↗
API credentials; Requirements; Configure API permissions · Checked 2026-10-16
Planned migration fidelity 5.0/10
Selected report fields in structured files; broader scope unverified
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Selected report fields leave as structured files; broader transaction/configuration completeness is unverified.
Get reports automatically ↗
Step 1: Set up automatic report generation; Step 5: Download reports · Checked 2026-10-16
Business logic and customization
5% of the overall score before applicability adjustment.
Scored answers and evidence
Logic authoring 2.5/10
External integration code; native business logic portability not established
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
External report ingestion and reconciliation are supported; native workflow portability is unestablished.
Get reports automatically ↗
Step 5: Download reports · Checked 2026-10-16
Rights to custom logic -
-
Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API.
Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
API credentials ↗
API credentials; Requirements; Configure API permissions · Checked 2026-10-16
Scores are out of 10. * Incomplete evidence discounts verified capabilities (unknown answers stay unknown). Planned migration drives data exit. Scoring method ↗
CUSTOMER CHOICE
Third-party accessibility
A Merchant admin or user with Manage API credentials creates a Report Service credential and assigns Merchant Report Download. Account toggles restrict its merchant scope; a report credential does not by itself authorize Checkout payment mutations.
Confirm who can connect, who owns the credentials and which uses are permitted. Customer consent and provider approval can be separate requirements; the selected plan and contract still matter.
READ / INTEGRATE
API and export routes
Configure selected report types and receive a REPORT_AVAILABLE notification with the download URL. An authenticated HTTP GET retrieves the file using the report-service API key or Basic authentication; available fields and periods depend on the selected report.
| Access route | Authentication | Credential owner | Provider approval | Access requirement | Last checked |
|---|---|---|---|---|---|
| Adyen customer API | API key | Customer | Not confirmed | Customer-supplied credentials | 2026-10-16 |
Availability depends on your product, plan and agreement. See the documentation below for the requirements of each route.
ECONOMIC ACCESS
Cost, authentication and limits
The lowest eligible customer plan and any fixed API, partner or setup charges remain unestablished. Payment-processing charges do not by themselves establish an API-access surcharge.
Check API entitlement, credential ownership and rate limits for the route you intend to use. Include review fees, customer-plan upgrades and ongoing access charges in the total.
ACT FROM OUTSIDE
External action
The Checkout refund operation submits all or part of a captured payment for return to the shopper. The result is asynchronous through REFUND events, and unreferenced refunds require separate provider approval; this is not an update to an exported report.
Validate the supported operation, acting identity and permission scope (read access does not imply write permission). Ambiguous retries and revoked credentials also affect whether an external workflow can run safely.
KEEP ACCESS USEFUL
Continuity
REPORT_AVAILABLE provides a trigger for recurring report retrieval. Retain file identity, merchant scope and generation period, then reconcile delivered records; the reviewed report route does not establish complete update/deletion events or a durable replay window. Supported report/date selections can be regenerated in the Customer Area; generated-file retention is separate from change-event replay.
CDC, deletions and recovery
| Question | Answer / applicable route | Evidence |
|---|---|---|
| Can ongoing extraction identify updates and deleted records on the declared route? | Full snapshots permit customer reconciliation; native deltas unverifiedAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Repeat a selected report scope for reconciliation; this does not establish complete tombstone or update coverage. | Get reports automatically ↗Step 1: Set up automatic report generation; Step 5: Download reportsChecked 2026-10-16 |
| How can extraction recover after missed events or an interrupted consumer? | Rebuild from a fresh snapshot; no historical replay establishedAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. The Customer Area can regenerate the supported merchant/type/date selection, including reports whose generated file has expired. This rebuilds selected reporting output, not deleted payloads or a retained event checkpoint. | Generate and download reports manually ↗Manually generate and download a report; report-retention introductionChecked 2026-10-16 Get reports automatically ↗Step 5: Download reportsChecked 2026-10-16 |
Useful ongoing access includes corrections and deletions, not only the first export. A failed request, changed filter or lost resource permission should not be interpreted as a deleted record.
LEAVE WITH YOUR DATA
Data exit and portability
Customers can hold structured report files, optionally encrypted with their own PGP public key. File custody does not establish a native account restore or complete payment vault, merchant configuration and historical-state export.
Test the output against the destination’s required fields and history. Check stable identifiers, relationships, attachments and extraction time; a sample file proves only the coverage of that sample.
BUILD / INSPECT / REUSE
Business logic and customization
External code can ingest reports and implement customer reconciliation (with refund actions separately authorized). Native Adyen workflow ownership and independent execution of provider risk or settlement logic remain unresolved.
Custom API access, ownership of workflows and the right to export their definitions are separate questions. A custom-app capability alone does not establish that business rules can move to another system.
AGREEMENTS / API DOCS / PROGRAM REQUIREMENTS
Documented conditions
Answers below come from public provider materials. Every answer retains its source check date, scope (a partner agreement does not describe every customer route). Customer contracts and live behavior still need verification.
| Question | Answer / applicable route | Evidence |
|---|---|---|
| What structured read interface is documented? | Report outputs onlyAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. The assessed read route delivers generated merchant report files, not an arbitrary transaction query interface. | Get reports automatically ↗Step 2: Set up REPORT_AVAILABLE notifications; Step 5: Download reportsChecked 2026-10-16 |
| How can customers retrieve data in bulk? | Batched or iterable API requestsAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Automated authenticated file downloads provide batched report retrieval, qualified by report type and period. | Get reports automatically ↗Step 5: Download reportsChecked 2026-10-16 |
| What queries can a customer issue outside the provider UI? | Fixed object or report retrievalAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Retrieve a generated report from its notified URL; arbitrary external predicates are not established. | Get reports automatically ↗Step 2: Set up REPORT_AVAILABLE notifications; Step 5: Download reportsChecked 2026-10-16 |
| Who decides whether a chosen third party may connect? | -Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved. | API credentials ↗API credentials; Requirements; Configure API permissionsChecked 2026-10-16 |
| What extra commercial condition applies to the routes supplying the assessed read capability, relative to the lowest paid plan? | -Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. The lowest eligible paid plan and route-specific fixed API charges have not been established. | API credentials ↗API credentials; Requirements; Configure API permissionsChecked 2026-10-16 |
| What permission is needed for the documented downstream use? | -Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation. | API credentials ↗API credentials; Requirements; Configure API permissionsChecked 2026-10-16 |
| Which external write operations are documented? | Named operations in a limited domainAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. A captured-payment refund operation and Idempotency-Key are documented; broad create/update is not inferred. | Refund a captured payment ↗Refund a captured payment; Request Parameters; Header ParametersChecked 2026-10-16 |
| How can customers connect an application they build or choose? | Customer applications using fixed APIs without provider selectionAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Customers configure their own role-scoped integration credentials; chosen-third-party distribution remains unresolved. | API credentials ↗API credentials; Multiple API credentialsChecked 2026-10-16 |
| What mechanism supports repeatable extraction of changes? | Scheduled feeds or recurring extractsAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Recurring report generation and report-ready notifications support repeated extraction. | Get reports automatically ↗Step 1: Set up automatic report generation; Step 2: Set up REPORT_AVAILABLE notificationsChecked 2026-10-16 |
| How are integration limits disclosed? | -Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Numeric request quotas and recovery instructions have not been established. | API credentials ↗API credentials; Requirements; Configure API permissionsChecked 2026-10-16 |
| Where can a usable data copy be delivered? | Customer-held structured files or API recordsAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Merchant report files can be downloaded and retained externally; selected PGP encryption is supported. | Get reports automatically ↗Step 4 (Optional): Encrypt report files; Step 5: Download reportsChecked 2026-10-16 |
| What retrieval rights are documented at cancellation? | -Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. A customer cancellation retrieval window and any exit charges have not been established. | API credentials ↗API credentials; Requirements; Configure API permissionsChecked 2026-10-16 |
| How can customers define their own business logic? | External integration code; native business logic portability not establishedAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. External report ingestion and reconciliation are supported; native workflow portability is unestablished. | Get reports automatically ↗Step 5: Download reportsChecked 2026-10-16 |
| What rights or portability are documented for custom workflow artifacts? | -Adyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Ownership, reusable export and independent execution of native workflow definitions remain unresolved. | API credentials ↗API credentials; Requirements; Configure API permissionsChecked 2026-10-16 |
| What usable data or native definitions can leave before cancellation? | Selected report fields in structured files; broader scope unverifiedAdyen merchant automated report-file download plus a separately authorized Checkout captured-payment refund operation; these are distinct credentials and do not establish a transaction-query API. Selected report fields leave as structured files; broader transaction/configuration completeness is unverified. | Get reports automatically ↗Step 1: Set up automatic report generation; Step 5: Download reportsChecked 2026-10-16 |
SOURCES / SCOPE / HISTORY
Sources and open questions
This review is based on the documentation below. Live account behavior and customer-specific agreements haven’t been tested.
Still to confirm
- Customer credential issuance does not establish a chosen third party’s eligibility; provider distribution approval remains unresolved.
- The lowest eligible paid plan and route-specific fixed API charges have not been established.
- Applicable third-party processing, redistribution and AI-use permissions have not been established by the reviewed technical documentation.
- Numeric request quotas and recovery instructions have not been established.
- A customer cancellation retrieval window and any exit charges have not been established.
- Ownership, reusable export and independent execution of native workflow definitions remain unresolved.
Documentation
Assessment checked 2026-10-16. Each answer retains its source and applicable route; the check date does not establish live account behavior.