Load Visa Direct Connect data to DuckDB

Visa Direct Connect provides APIs for streamlined access to multiple payment endpoints, enabling payouts to accounts, wallets, and cards. Everything needed to build a working Visa Direct Connect → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Visa Direct Connect to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Visa Direct Connect to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Visa Direct Connect API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Visa Direct Connect API at a glance

These values come from the Visa Direct Connect API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Visa Direct Connect API?

All requests require Mutual TLS (mTLS) client certificate authentication and an API key header formatted as 'Authorization: API-Key {key}'.

1. Get your credentials

1. Log in to your account on the Visa Developer Platform. 2. Navigate to your Project Dashboard for the relevant Visa Direct Connect project. 3. Select the target environment (e.g., Sandbox, Certification, or Production) from the left-hand navigation menu. 4. Open the Credentials tab. 5. Locate the X-Pay Token section to retrieve your API Key and Shared Secret, or follow the provided instructions to configure Two-Way SSL (Mutual Authentication) if required by your specific API implementation.

2. Add them to .dlt/secrets.toml

Copy
[sources.visa_direct_connect_source]
visa_api_key = "your_api_key_here"
visa_shared_secret = "your_shared_secret_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Visa Direct Connect data can I load into DuckDB?

These are the Visa Direct Connect endpoints dlt can load into DuckDB:

---

How do I load only new Visa Direct Connect records?

The Visa Direct Connect API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "query_payout", "endpoint": {
    "path": "visapayouts/v3/payouts",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Visa Direct Connect pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading Send Payout and Query Payout from the Visa Direct Connect API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def visa_direct_connect_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.visa.com/vdp",
            "auth": {"type": "api_key", "api_key": api_key},
        },
        "resources": [
            {"name": "query_payout", "endpoint": {"path": "visapayouts/v3/payouts"}},
            {"name": "get_account_balance", "endpoint": {"path": "visapayouts/v3/accountBalance"}}
        ],
    }
    yield from rest_api_resources(config)


def load_visa_direct_connect_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="visa_direct_connect_pipeline",
        destination="duckdb",
        dataset_name="visa_direct_connect_data",
    )
    load_info = pipeline.run(visa_direct_connect_source())
    print(load_info)


if __name__ == "__main__":
    load_visa_direct_connect_to_duckdb()

Run it with python visa_direct_connect_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Visa Direct Connect data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("visa_direct_connect_pipeline").dataset()
df = data.query_payout.df()
print(df.head())

SQL:

Copy
SELECT * FROM visa_direct_connect_data.query_payout LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Visa Direct Connect to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Visa Direct Connect loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Visa Direct Connect data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack