Linking Adyen as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Adyen connector syncs account holders, balance accounts, companies, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Connect your Adyen account to sync payments data.
Create an API credential in your Adyen Customer Area under Developers > API credentials, then paste its API key below. Which tables you can sync depends on what that credential can reach:
- Transactions, transfers, account holders and balance accounts need an Adyen for Platforms or Adyen Issuing integration. Add your balance platform ID too.
- Settlement detail reports need a merchant account and the Merchant Report Download role. Adyen only creates these files once you turn on the settlement details report in your Customer Area.
- Companies and merchant accounts come from the Management API and need an account read role.
Pick the environment that matches where you created the API key - a test key won't work against live.
You'll be asked for:
- Environment: choose between Live and Test.
- API key
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Adyen tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Environment | select | Yes |
API key | password | Yes |
Balance platform ID | text | No |
Merchant account | text | No |
Start date | text | No |
First settlement batch number | number | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
AccountHolders | Account holders in your balance platform, each representing a legal entity you onboarded. | Full refresh | — | — |
BalanceAccounts | Balance accounts holding funds for each account holder in your balance platform. | Full refresh | — | — |
Companies | Company accounts your API credential can access. | Full refresh | — | — |
MerchantAccounts | Merchant accounts your API credential can access, with their processing configuration. | Full refresh | — | — |
SettlementDetailReports | Transaction-level settlement lines from the settlement details report, one row per settled payment or fee. | Incremental, Full refresh | batch_number | — |
Transactions | Individual movements of funds booked against a balance account. | Incremental, Full refresh | creationDate | — |
Transfers | Transfer instructions such as payouts, top-ups and internal transfers. | Incremental, Full refresh | createdAt | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.