Adyen Connector
With Weld, you can seamlessly replicate Adyen's payment data to any destination or warehouse for easy analytics and reporting.
AdyenYour warehouseLive
Agent context over MCPSet up in minutes.
No code, no maintenance.
Adyen
Data source
Adyen in your warehouse.
Ready for your agents.
With Weld, you can seamlessly replicate Adyen's payment data to any destination or warehouse for easy analytics and reporting. Weld's Adyen connector is fully managed: it extracts data from Adyen, loads it into your warehouse, and keeps it in sync. The data lands in a clean, documented schema with agent context attached, so analysts can query it with SQL or dbt, and agents can query it over the Weld MCP server without guessing at tables or joins.
Adyen data schema.
The map your agents read.
Every table, field and relationship Weld syncs from Adyen is served to agents as context over MCP, so they pick the right tables and join on the right keys.
- tables
- 28
- fields
- 160
Adyen models.
What the numbers mean.
Open-source SQL that turns the raw Adyen tables into the reports people ask about. Deploy them in Weld and your agent queries the definitions, not guesses.
- Authorisation rateAuthorisation rate by day and payment method: of the payments that reached an authorisation decision, the share that were authorised.grain: day (first decision, report time zone) x merchant account x payment method x payment currency
- Fees by payment methodWhat each payment method costs: settled volume, refunds, chargebacks and the transaction fees withheld, with interchange, scheme fees and markup broken out where Adyen has interchange level data.grain: day (creation date, report time zone) x merchant account x payment method x payment method variant x net (settlement) currency
- Payment lifecycleOne row per payment with every step of its life: when it was received, authorised or refused, captured, settled, refunded and charged back, and the amounts Adyen booked at each step. Built from the Payment accounting report.grain: merchant account x PSP reference (one payment)
- Settlement batchesAdyen's settlement batches, itemised: what was settled, what came back out as refunds and chargebacks, what Adyen and the card schemes withheld, and what was paid to your bank account. Recreates the batch view of the Settlement details report in the Customer Area.grain: merchant account x batch number x net (settlement) currency
Ask your agent.
It already knows Adyen.
Connect Claude, Cursor, ChatGPT or your own agent to Weld over MCP. It reads the Adyen context, finds the tables it needs and queries your warehouse.
- Agent contextAdyen tables, fields and joins
- QuerySQL against your warehouse
- OperateCheck, rerun and refresh syncs
How many payments_accounting_report rows do we have in our Adyen data?
Reading the Adyen context first, so the query uses the right tables and keys.
Load Adyen into any warehouse.
Set up in minutes, no code.
Everything you need.
To get started.
Adyen setup guide
Step-by-step instructions to configure and start syncing.
MCP serverConnect your agents
Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.
Weld Connect APIBuild custom connectors
Use the Weld Connect API to build and publish your own connector.
FAQCommon questions
Answers to frequently asked questions about Weld connectors.
Set it up in code.
One REST API.
Use the Weld Connect REST API to create Adyen connections, configure ELT syncs, and manage pipelines entirely through code. Built for embedding, automation, and CI/CD workflows.
▌Common questions.
About connectors.
Something not covered here? A data engineer can walk through your setup with you.
Talk to usPut your Adyen data to work.
Connect Adyen, pick a warehouse, and your agents can query it today. Free for 14 days, no credit card.
Source
