PhonePe Python API Docs | dltHub

Build a PhonePe-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The DQR Init API allows businesses to generate unique QR codes for each payment request, facilitating both online and in-store transactions. It is part of PhonePe's dynamic QR code solution, enabling secure and efficient payments. This API is documented on PhonePe's developer portal. The REST API base URL is https://mercury-t2.phonepe.com and All requests require an X-VERIFY signature header generated with a secret salt key..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading PhonePe data in under 10 minutes.


What data can I load from PhonePe?

Here are some of the endpoints you can load from PhonePe:

ResourceEndpointMethodData selectorDescription
qr_init/v3/qr/initPOSTInitialise a dynamic QR code.
transaction_status/v3/transaction/{merchantId}/{transactionId}/statusGETRetrieve status of a specific transaction.
placeholder_one/v3/placeholder/oneGETPlaceholder endpoint – no source info.
placeholder_two/v3/placeholder/twoGETPlaceholder endpoint – no source info.
placeholder_three/v3/placeholder/threeGETPlaceholder endpoint – no source info.

How do I authenticate with the PhonePe API?

Generate X-VERIFY by hashing SHA256(base64(payload) + request_path + salt_key) and append '###' plus the salt index; include it in the X-VERIFY header of each request.

1. Get your credentials

  1. Log in to the PhonePe merchant/partner portal.
  2. Go to 'Integrations' → 'Dynamic QR' settings.
  3. Locate the 'Salt Key' and 'Salt Index' fields.
  4. Copy these values; the Salt Key is the secret used for X-VERIFY, and the Salt Index is appended after the ### delimiter.
  5. Store the values securely and use them in the DLT secrets.toml configuration.

2. Add them to .dlt/secrets.toml

[sources.phonepe_dqr_init_api_source] salt_key = "your_salt_key_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the PhonePe API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

python phonepe_dqr_init_api_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline phonepe_dqr_init_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset phonepe_dqr_init_api_data The duckdb destination used duckdb:/phonepe_dqr_init_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

dlt pipeline phonepe_dqr_init_api_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads qr_init and transaction_status from the PhonePe API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def phonepe_dqr_init_api_source(salt_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://mercury-t2.phonepe.com", "auth": { "type": "api_key", "salt_key": salt_key, }, }, "resources": [ {"name": "qr_init", "endpoint": {"path": "v3/qr/init"}}, {"name": "transaction_status", "endpoint": {"path": "v3/transaction/{merchantId}/{transactionId}/status"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="phonepe_dqr_init_api_pipeline", destination="duckdb", dataset_name="phonepe_dqr_init_api_data", ) load_info = pipeline.run(phonepe_dqr_init_api_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("phonepe_dqr_init_api_pipeline").dataset() sessions_df = data.qr_init.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM phonepe_dqr_init_api_data.qr_init LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("phonepe_dqr_init_api_pipeline").dataset() data.qr_init.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load PhonePe data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install

Was this page helpful?

Community Hub

Need more dlt context for PhonePe?

Request dlt skills, commands, AGENT.md files, and AI-native context.