Adyen
Adyen does not send webhook events for company-level reports by default. You must contact Adyen Support to enable webhook events for company-level reports. Without this, Athia is never notified that a new report is ready and data stops advancing. Nothing else in the setup surfaces this.
Adyen needs real homework in the provider's console: most of what Athia ingests arrives as scheduled report files, so those reports must exist first. Do that and Adyen becomes the best settlement and cost source you can connect.
What you get
Settlement detail and aggregate settlement, payment accounting, received payment details, interchange and scheme fee detail, dispute transaction detail, and 3D Secure authentication outcomes.
Strongest for settlement and fee detail. Adyen breaks out what was settled and what it cost at a level most providers do not expose, making it the reference source for cost per approved order.
Weakest for subscription context, which is thin here — that picture comes from elsewhere.
Before you start
1. Enable and schedule the reports. Select the merchant account from the top-left dropdown → Reports in the left nav → search for and configure each report → click Generate → select Automated (generate on schedule) → choose .CSV as the File type. Configure all of these:
- 3D Secure Authentication
- 3DS Authentication
- Aggregate settlement details
- Dispute transaction details
- Interchange and Scheme Fee
- Payment Accounting
- Received payment details
- Settlement details
Automate these reports at the company account level as well as per merchant account — per-merchant-account scheduling alone does not produce the company-level reports.
After the first merchant account, star (bookmark) the reports so the rest go faster.
2. Create the Report service user. Switch to company-level view, create the credential, and select Report service user as the Credential type. Copy the Username from General settings, then generate the Password under Server settings → Basic Auth. Associate the credential with the company account and every merchant account you want in Athia; a credential scoped to one account silently leaves the others out.
3. Create the Web Service API credential. In the Adyen Customer Area at company level, go to Developers → API credentials and create a web service credential, then generate and copy its API key.
4. Give the Web Service API credential its roles. Creating it is not enough. Under Permissions → Roles, grant Management API - Accounts read and Management API - Webhooks read and write. Under Accounts, associate it with the company account and all associated merchant accounts.
The Report service user credential is read-only: Athia reads the report files your schedules already produce and does not enable or modify reports on your behalf — you schedule them in the Adyen console. The Web Service API credential is write-capable on webhooks (
Management API - Webhooks read and write); that scope is used to read your account configuration and maintain the webhook that tells Athia a new report is ready.
Credentials Athia asks for
| Field | Required | What it is / where to find it |
|---|---|---|
| Name | Yes | Your label for this connection — identify the company account or region |
| Schedule | No | How often Athia checks for new data and report files |
| Web Service Api Key | Yes | The API key you created for Athia |
| Report Service Api Key | Yes | The credential for the company-level Report service user |
Setting up the connection
- In Settings → Connections, choose + Add Connection and select Adyen.
- On Configure Connector, enter a Name and pick a Schedule.
- On Enter Credentials, paste the Web Service Api Key and the Report Service Api Key.
- Choose Verify Connection.
The connection then shows as ACTIVE and the first sync starts.
For additional MIDs, reuse the same credentials — no further Adyen changes are needed if reports are already configured for those MIDs.
Register the Athia webhook in Adyen
Copy the Athia Webhook Destination URL from the connection wizard, then in Adyen:
- Go to Developers → Webhooks → Create new webhook → Standard notification → Add.
- Open Edit Server configuration and paste the Athia Webhook Destination URL.
- Under Merchant accounts, select the MIDs — they must match the MIDs you configured reports for.
- Under Additional Settings, enable 3D Secure (include 3D Secure result and version), Acquirer (add acquirer result and reference) and Card (include Card BIN and detailed Card BIN information).
- Test the webhook, save it, then enable it.
Company-level report events still require the Adyen Support request at the top of this page.
Sync cadence
Your Schedule controls how often Athia looks for new report files, not how fast Adyen produces them. Settlement data advances only when Adyen closes a batch.
Limits and things to know
- Report-dependent. If a report is not enabled in Adyen — or is set to manual — that data never reaches Athia, and verification can succeed while a domain stays empty.
- Amounts are decimal — never divide by 100, unlike Stripe.
- Card data is minimized. For what each ingested field holds, see Athia Data Dictionary.
- Historical reach is bounded by how many reports Adyen returns, so very old periods may be unreachable and must be regenerated in Adyen first — in the Customer Area, go to Reports → select report → custom date range. Confirm the achievable lookback before promising a backfill window.
Troubleshooting
| What you see | Likely cause | What to do |
|---|---|---|
| One merchant account is missing | Report service user not associated with it | Associate the credential with every account |
| Settlement data arrives, fee data does not | Interchange and Scheme Fee report not enabled | Enable it and wait for the next generation |
| Verification succeeds but no new data ever arrives | Adyen is not sending webhook events for company-level reports | Contact Adyen Support to enable them, then confirm the webhook is enabled and its MIDs match your report MIDs |
Related
- Athia Connectors — the full connector catalog.
- Integrating Athia — integration paths, including file drops and warehouse-to-warehouse.
- Athia Data Dictionary — field-level definitions.
Updated 1 day ago