Adyen Connector

With Weld, you can seamlessly replicate Adyen's payment data to any destination or warehouse for easy analytics and reporting.

Start for free View documentation

4.8 on G2

Weld · Data Sources

AdyenYour warehouseLive

payments_accounting_report48 columnsSynced

settlement_detail_report33 columnsSynced

company4 columnsSynced

account_configuration_report3 columnsSyncing

aggregate_settlement_details_report3 columnsQueued

Lands in

Agent context over MCP

How it works

Set up in minutes.
No code, no maintenance.

Adyen

Data source

Authenticating...

Ready to connect

Overview

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.

Agent context

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

28 tables

Joins between these tables aren't mapped yet.

Open the schema explorer Open the full schema explorer

Weld MCP server

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

Set up the MCP server

Claude CodeOpus 5

ConnectedWeld MCPAgent contextAdyentables28fields160

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.

●weld·search_available_references

⎿raw.adyen.payments_accounting_report

+ 27 more Adyen tables

●weld·get_reference_schema

⎿payments_accounting_report · 48 columns

file_name, row_checksum

●weld·run_query

⎿select count(*) from {{raw.adyen.payments_accounting_report}}

submitted

●weld·get_query_status

⎿DONE

●weld·get_query_result

⎿rows returned

✓Answered from Adyen data in your warehouse

>Ask about your Adyen dataMCP

Destinations

Load Adyen into any warehouse.
Set up in minutes, no code.

Resources

Everything you need.
To get started.

Documentation

Adyen setup guide

Step-by-step instructions to configure and start syncing.

MCP server

Connect your agents

Set up Claude, Cursor, ChatGPT or Codex against your Weld workspace.

Weld Connect API

Build custom connectors

Use the Weld Connect API to build and publish your own connector.

FAQ

Common questions

Answers to frequently asked questions about Weld connectors.

Weld Connect API

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.

Explore Weld Connect API reference

POST/elt_syncs

# Create a Adyen ELT sync
curl -X POST https://connect.weld.app/elt_syncs \
  -H "x-api-key: $API_KEY" \
  -d '{
    "connection_id": "conn_abc123",
    "integration_id": "adyen",
    "destination_schema_name": "adyen_data",
    "sync_interval": "0 * * * *"
  }'
▌