METRO QR TICKETING

Payment and settlement infrastructure layer for metro QR ticketing

Expand your platform’s offerings and categories without expanding your operational complexity.

Get Early Access

THE PROBLEM

ONDC gets you distribution. Building the infrastructure delays the revenue opportunity.

Integration complexity

18–20 raw ONDC APIs to implement
A different MRC means a new API spec, validation or QR logic
A separate integration for every new MRC

Integration complexity

18–20 raw ONDC APIs to implement
A different MRC means a new API spec, validation or QR logic
A separate integration for every new MRC

Delayed settlement

A different settlement cycle for each MRC
Operational configuration with each MRC

Delayed settlement

A different settlement cycle for each MRC
Operational configuration with each MRC

Recon and dispute issues

Manual mismatch handling causes reconciliation errors
No shared format for refunds and mismatches
Chargeback resolution only through the MRC relationship manager

Recon and dispute issues

Manual mismatch handling causes reconciliation errors
No shared format for refunds and mismatches
Chargeback resolution only through the MRC relationship manager

WHY NOW

The window to own this category is open

1.15 crore

Daily metro commuters, and growing

~45%

Payments per month per active commuter

27%

QR adoption via digital channels in Delhi alone

40%

Cash commuters — an addressable revenue opportunity

WHAT SETU DOES

Setu is the layer between multiple MRCs and your platform

Automatic MRC onboarding

When a new metro joins ONDC, it's live on your integration with zero code change.

Automatic MRC onboarding

When a new metro joins ONDC, it's live on your integration with zero code change.

Spec-change absorption

Upstream absorption of MRC API changes, validation updates and new QR logic.

Spec-change absorption

Upstream absorption of MRC API changes, validation updates and new QR logic.

Built-in observability

Operational health, business outcomes and settlement metrics, out of the box.

Built-in observability

Operational health, business outcomes and settlement metrics, out of the box.

HOW IT WORKS

Four steps, and you never touch the plumbing

01 — Request

Your app sends a booking request to Setu.

01 — Request

Your app sends a booking request to Setu.

02 — Orchestrate

Setu talks to ONDC and the metro network — catalog, quote, confirmation.

02 — Orchestrate

Setu talks to ONDC and the metro network — catalog, quote, confirmation.

03 — Ticket

Ticket and QR are generated and returned to your app instantly.

03 — Ticket

Ticket and QR are generated and returned to your app instantly.

04 — Settle

Settlement, reconciliation and disputes run in the background — you never touch them.

04 — Settle

Settlement, reconciliation and disputes run in the background — you never touch them.

One integration. Every metro, live.

Delhi (DMRC)

Bangalore (BMRCL)

Chennai (CMRL)

Kochi (KMRL)

Nagpur (NMRCL)

Pune (PMRDA)

Mumbai (all lines)

INFRASTRUCTURE FOR THE NEXT BILLION

QR ticketing versus the NCMC card

Parameter

QR Ticketing

NCMC Card

Delhi Metro adoption

27.71% of journeys

1.98% of journeys

Hardware required

Any smartphone with a UPI app

Physical NFC card + terminal sync

Onboarding cost

Zero

₹50–100 card deposit

Top-up experience

Instant, via UPI

Online reload, needs a terminal tap to sync

Lost card recovery

N/A — the ticket is digital

Unloaded balance lost (offline transaction)

User behaviour fit

Matches the existing UPI habit (83% of digital payments)

Requires new card-carrying behaviour

Bangalore status

Live and growing

BMRCL suspended issuance, Apr 2025

Build the payments layer under India’s next transit boom

One integration. Every metro on the network — today, and as new cities go live.

Get Early Access