HyperBolt UPI Switch
An NPCI-grade UPI switch, rebuilt for the AI-attack era — at a tenth of legacy TCO.
A horizontally scalable, graph-aware UPI core that connects directly to the NPCI 2.x switch, federates with IMPS, AEPS, BBPS and RuPay, and embeds inline fraud decisioning at every hop — without the latency tax of bolted-on risk engines.
Core Capabilities
Numbers that speak for themselves
Hyperbolt currently manages structured and unstructured data, including billions of records.
<0ms
<0ms
p99 switch latency
0k +
0k +
TPS per cluster
0.0%
0.0%
rail availability
0weeks
0weeks
NPCI sandbox to prod
HyperBolt
The Indian UPI switch market — at a glance
A snapshot of India’s UPI switch ecosystem, highlighting key players, transaction scale, performance metrics, and infrastructure growth trends.
HyperBolt
Graph-aware, risk-native
<50ms p99 · 30k TPS · NPCI 2.x · inline fraud
Legacy Switch A
Card-era middleware retrofitted to UPI
120–250ms · external risk hop
Legacy Switch B
On-prem appliance, batch reconciliation
T+1 settlement insight
PSP-built Switch
Tightly coupled to one aggregator
Vendor lock-in, no multi-bank
Open-source DIY
Self-built UPI plugin
12–18 mo build, zero RBI assurance
What the switch does
A full UPI core — not a thin router with a fraud add-on.
Every capability a modern Indian payments operator needs to run UPI, IMPS, AEPS, BBPS and RuPay at scale — packaged into one VPC-resident binary with one operating model.
NPCI 2.x conformant core
Native ReqPay / RespPay / ReqAuth / RespAuth handling, credit-and-collect, mandates, AutoPay, conversational UPI, and UPI Lite — certified against the latest NPCI specs.
- • Full ISO 20022 + NPCI XML message conformance
- • Mandate engine for recurring debits and e-Mandate UMRN
- • UPI Lite offline wallet and credit-line-on-UPI
- • Real-time settlement file generation for sponsor banks
Sub-50ms decision path
End-to-end p99 latency under 50ms including risk score, mandate validation, beneficiary checks, and policy evaluation — measured at the switch, not the API gateway.
- • Lock-free in-memory routing tables
- • Zero-copy protobuf pipeline, no JVM tax
- • Per-PSP circuit breakers with graceful degrade
- • Hot-path observability with 1µs span resolution
Multi-rail interop
One switch, every rail. UPI, IMPS, AEPS, NEFT, RTGS, BBPS, RuPay, Bharat QR — addressed through a unified beneficiary and account-resolution graph.
- • VPA, IFSC+AC, Aadhaar, mobile, RuPay PAN resolution
- • Federated routing across sponsor and remitter banks
- • Cross-rail fallback (UPI ↔ IMPS) within SLA
- • BBPS biller catalog + RuPay tokenisation built in
Risk fabric, in-line
HyperBolt’s graph-native fraud engine runs as a co-located scorer inside the switch — no external HTTP hop, no async drift, no false-positive tax on growth.
- • 6-hop fund-flow traversal at switch speed
- • Device + behavioural + handle graph fused at /decide
- • Adversarial red-team feed for AI-scripted attacks
- • Reason codes attached to every decline — RBI/FIU ready
Policy DSL owned by risk
Risk and compliance ship rule changes through a typed DSL with shadow replay against last-30-day traffic — no release-train coupling to engineering.
- • Typed, versioned, peer-reviewed rule packages
- • Shadow mode + champion-challenger A/B
- • Per-merchant / per-MCC / per-corridor scoping
- • One-click rollback with deterministic replay
Stateful by design
First-class transaction state machines persisted to a horizontally shared log — reconciliation, recall, and dispute orchestration are core features, not afterthoughts.
- • Exactly-once semantics across PSP retries
- • T+0 reconciliation with NPCI raw settlement files
- • Built-in chargeback, recall, refund workflows
- • Replay any transaction byte-for-byte for audit
RBI + DPDP-aligned
VPC-resident deployment in your data centre or our Mumbai/Hyderabad zones. HSM-backed key custody, data localisation, and audit-grade access controls by default.
- • Thales / nCipher HSM integration for PIN-block, MAC
- • TLS 1.3 mTLS to NPCI and all PSPs
- • Field-level encryption for PII at rest
- • DPDP consent lineage attached to every record
Drop-in core integration
Reference connectors for Finacle, FLEXCUBE, BaNCS, TCS BaNCS, Infosys EdgeVerve and Oracle FSS. No core-banking change request to go live.
- • Pre-built CBS adapters with idempotency
- • Sponsor-bank settlement file pipelines
- • Standard webhooks for ledger, fraud, ops
- • Sandbox + Postman + OpenAPI from day one
Self-healing operations
An operations plane that detects PSP brownouts, NPCI sandbox flaps, and beneficiary-bank decline storms — and routes around them before your support queue fills.
- • Per-corridor health scoring with auto-route
- • Synthetic probes against NPCI + member banks
- • Anomaly alerts shipped to PagerDuty / Slack
- • Runbooks executed by the switch, not your NOC
How it's built
A five-layer switch with the risk graph embedded — not bolted on.
Most India switches are a routing engine plus an external fraud service joined by an HTTP hop. HyperBolt fuses them at the binary level so the risk graph is queried in the same hot path that signs the NPCI response.
Layer 1
Edge & Protocol Layer
NPCI XML, ISO 20022, REST/gRPC, mTLS termination, per-PSP traffic shaping.
Layer 2
Routing & State Core
Lock-free routing, exactly-once state machine, transaction log, settlement engine.
Layer 3
Graph Risk Plane
Co-located fraud scorer over entity, device, handle and fund-flow graphs.
Layer 4
Policy & Mandate Engine
Typed DSL, mandate lifecycle, AutoPay, UPI Lite, credit-line-on-UPI.
Layer 5
Integration Plane
CBS adapters, sponsor-bank pipelines, webhooks, observability and ops runbooks.
GRAPH ENGINE
47 edge types. One traversal. Every UPI request scored against the live money graph.
ENTITIES
VPA • device • SIM • account • merchant • MCC • BC outlet • biller • BIN • BIC
EDGES
transacts-with • shares-device • co-signs • funds • refunds • disputes • settles-through
SIGNALS
velocity • novelty • drift • concentration • ring-density • liveness • handle-rotation
Decision pipeline
Six hops. One process. Always under 50ms.
Every UPI message traverses the same deterministic, replayable pipeline — so every decline is explainable and every approval is reconciliable.
Step 1
Ingest
NPCI ReqPay arrives. mTLS verified, payload parsed in <1ms.
Step 2
Resolve
VPA/account/handle resolved against federated beneficiary graph.
Step 3
Materialize
Live features computed: velocity, novelty, ring density, device drift.
Step 4
Score
Graph model + policy DSL evaluate the transaction in-process.
Step 5
Act
Approve · step-up · cool-down · decline — reason codes attached.
Step 6
Settle
State machine persists, settlement file emitted, webhooks fired.
How a UPI switch works
From QR scan to settlement — the six-hop journey of a UPI transaction.
A UPI switch sits between PSP apps, the NPCI central switch, and the bank's core banking system. Depending on whether you serve the merchant side or the customer side, you operate an Acquiring Switch, an Issuing Switch — or both.
01
Customer initiates
Payer scans a QR, taps an Intent link, or enters a VPA in the PSP app. The PSP signs the request and pushes it to its acquiring switch.
02
Acquiring switch validates
MCC, merchant KYC, velocity, geo and device signals are checked. The collect/pay request is composed into an NPCI XML ReqPay and forwarded to the central NPCI switch.
03
NPCI routes to issuer
NPCI resolves the beneficiary VPA / account / handle and dispatches the request to the issuer bank's UPI switch over the NPCI 2.x mesh.
04
Issuing switch authorises
Issuer switch validates UPI PIN against HSM, runs limit and risk checks against the core banking ledger, posts the debit, and returns RespPay to NPCI.
05
Beneficiary credited
NPCI fans the response to the acquiring switch. Beneficiary's bank posts the credit (real-time or via T+0 sponsor settlement) and sends a customer notification.
06
Settlement & reconcile
NPCI publishes raw settlement files. Both acquiring and issuing switches reconcile T+0 against their internal state machines and emit accounting events to the CBS.
ACQUIRING SIDE
UPI Acquiring Switch
The acquirer represents the merchant on the rail. It onboards merchants, generates QR / Intent collect requests, forwards them to NPCI, settles funds into merchant Nostro accounts, and runs the chargeback / dispute workflow. Operated by PA-PG players, sponsor banks, and large merchant aggregators.
ISSUING SIDE
UPI Issuing Switch
The issuer represents the customer. It registers VPAs, holds UPI PIN custody in an HSM, authorises debits against the core banking ledger, runs mandates / AutoPay / UPI Lite, and applies inline issuing-side fraud control. Operated by every bank with UPI live customers.
Merchant onboarding & lifecycle
End-to-end merchant identity, KYC/KYB, MCC tagging, sub-merchant hierarchy and risk-based limit assignment.
- Aadhaar / PAN / GST / Udyam KYB
- Sub-merchant & aggregator support
- MCC-aware velocity & cap policies
- Automated MDR / MSF configuration
QR & intent generation
Static, dynamic, and Bharat QR generation with EMVCo conformance, plus UPI Intent / Deep-link orchestration for in-app collect.
- Per-terminal dynamic QR with TTL
- EMVCo + NPCI Bharat QR conformance
- UPI Intent SDK for Android/iOS
- Tokenised payee for tip / split flows
Collect-request engine
Composes ReqPay collect/intent messages to NPCI, manages timeouts, retries, deemed-approvals and reversals at switch speed.
- Collect, Pay, Mandate, AutoPay flows
- Per-PSP circuit breakers
- Idempotent retry with exactly-once
- Deemed-approval timeout handling
Settlement & payout
T+0 sponsor-bank settlement, daily NPCI raw-file reconciliation, and per-merchant payout schedules with TDS / GST splits.
- Sponsor-bank Nostro reconciliation
- Per-merchant configurable payout windows
- TDS, GST and MDR split engine
- Auto-generated 26AS / GSTR feeds
Acquiring risk & chargeback
Inline graph-risk on the collect path plus a full UDIR chargeback workflow for disputes, refunds and good-faith reversals.
- Inline merchant-risk decline
- NPCI UDIR dispute orchestration
- Refund, partial-refund, reversal flows
- Reason-coded decline analytics
Merchant notifications & APIs
Webhook, REST and gRPC surfaces for merchants and ISVs, plus settlement / dispute notification fan-out.
- OpenAPI + Postman collection
- At-least-once webhook delivery
- WhatsApp / SMS / email notifications
- Merchant dashboard & reports
SHARED SWITCH PLATFORM
Run acquiring, issuing, or both — on one binary.
The acquiring and issuing modules are facets of the same NPCI-conformant core. Operators license the modules they need without running two switches in parallel.
Protocol & message core
NPCI 2.x XML, ISO 20022, mTLS, signature & checksum validation.
Routing & state machine
Exactly-once transaction lifecycle, replay, recall, reversal.
Settlement ledger
Shadow ledger reconciled with NPCI raw files; T+0 close.
Reconciliation & dispute
UDIR + RGCS workflows, refund, chargeback, good-faith reversal.
Ops, observability, HA
Per-corridor health, hot-standby, multi-AZ, NPCI sandbox parity.
Who it's for
One switch. Three operator profiles. Measurable economics for each.
Banks, fintechs and payment infrastructure operators all need UPI to be fast, safe, and cheap — but they're measured on different ledgers. HyperBolt UPI Switch ships the same core with operator-specific operating models.
SCHEDULED COMMERCIAL, PSU & SMALL-FINANCE BANKS
For banks: own your UPI economics instead of renting them from a third-party switch.
Most Indian banks today route UPI through a third-party switch they neither control nor observe in real time. HyperBolt UPI Switch lets the bank operate as its own PSP — decisions, settlement, and fraud control inside the bank's perimeter — while remaining fully NPCI-conformant.
60–80%
lower per-txn UPI infra cost vs. third-party PSP
<50ms
p99 inline switch latency including fraud
T+0
settlement reconciliation against NPCI files
6 weeks
NPCI sandbox to production cutover
WHERE THE PAIN SHOWS UP → HOW THE SWITCH ANSWERS
Own the rail
Operate as a direct PSP with the bank's own VPA handle, settlement account, and risk policy — no shared-tenant compromise.
Regulator-grade evidence
Every decision and settlement entry is replayable byte-for-byte for RBI inspection and FIU-IND filings.
Branch + app + BC parity
One switch serves the mobile-banking app, internet banking, and the BC AEPS network with the same decisioning brain.
TCO that doesn't scale with GMV
Infra cost scales with concurrency, not transaction count — your margin per UPI improves as you grow.
WHERE THE PAIN SHOWS UP → HOW THE SWITCH ANSWERS
FINTECHS, NEOBANKS, PPI ISSUERS & LENDING PLATFORMS
For fintechs: launch UPI products without inheriting a sponsor-bank backlog.
Fintechs ship product weekly; sponsor banks ship middleware quarterly. HyperBolt UPI Switch sits inside the sponsor bank's perimeter but exposes a developer-friendly API and policy DSL to the fintech — so new merchant flows, mandates, and credit-line-on-UPI features go live in days, not quarters.
<2 weeks
API integration to first production transaction
10×
feature velocity vs. sponsor-bank middleware queue
−60%
synthetic-onboarding success rate on UPI flows
0
per-txn risk fees on verified clean traffic
Developer-grade integration
OpenAPI, Postman, sandbox, and webhook contracts from day one — your engineers integrate in days, not sprints.
Product velocity unlocked
AutoPay, mandates, UPI Lite, credit-line-on-UPI, conversational UPI — all live the moment NPCI certifies them.
Cohort-tuned risk
Shadow-replay rule changes against your own cohort traffic before promoting to production.
Sponsor-bank transparency
Read-only evidence portal for the sponsor's compliance team — kills the email loop that delays launches.
PSPS, AGGREGATORS, SWITCHES & PAYMENT INFRASTRUCTURE
For payment infrastructure: rail-grade scale with the risk graph built in.
Aggregators and PSPs operate at the convergence point of the ecosystem. HyperBolt UPI Switch ships as a rail-grade core engineered for switch-class TPS, with privacy-preserving federation that lets member banks share fraud intelligence without ever moving raw PII.
30k+
TPS per cluster with <50ms p99
100%
of decisions independently replayable
Federated
intel without cross-member PII movement
Member ↑
trust as a rail-level differentiator
WHERE THE PAIN SHOWS UP → HOW THE SWITCH ANSWERS
Switch-class throughput
Engineered for 30k+ TPS per cluster with predictable tail latency under burst and brownout.
Federated intelligence
Members exchange encrypted graph signals; raw PII never leaves their VPC, intelligence still propagates network-wide.
Member-facing risk feeds
Push enriched signals back to issuers and acquirers as a network value-add — strengthens membership stickiness.
Rail-level attestation
Quarterly fraud-posture reports your regulator and member banks both rely on.
Customer proof
From risk review to competitive advantage — measured in weeks, not years.
Three live deployments. Three different operator profiles. One common outcome: fraud losses down, regulator confidence up, and engineering teams back in control of their payment stack.
FILTER BY SEGMENT
Payment Infrastructure
Multi-bank UPI switch operator, 15M+ monthly transactions
Cross-member mule networks were laundering through the switch, degrading trust scores with NPCI and attracting regulatory scrutiny. Legacy risk was a batch nightly job; real-time intel lived in Excel and WhatsApp.
HyperBolt UPI Switch replaced the legacy core with a graph-native switch. Member-facing fraud feeds gave every connected bank shared intelligence without exposing PII. Privacy-preserving federation let the network spot cross-member rings without breaking data-localisation rules.
38%
fewer cross-member fraud complaints
100%
replayable transaction lineage
Sub-50ms
inline risk at switch speed
NPCI-grade
throughput with no latency tax
“Moving from batch Excel to a real-time shared graph changed the economics of the entire network. Members now trust the switch because they can see the reasoning behind every block — and the regulator sees it too.”
CTO — Multi-bank UPI switch operator, 15M+ monthly transactions
Why HyperBolt UPI Switch
The first UPI switch engineered for India's rails — and for attackers who use AI.
Most India fintech-tech is a card-era switch with a UPI adapter and an external risk engine. HyperBolt is UPI-native, graph-aware, and economically aligned with the operator — not the vendor.
Built for switch-class load
Lock-free, zero-copy core in Rust/Go — not a JVM stack inheriting GC pauses on the hot path.
Risk graph in the binary
The fraud scorer is a library call away from the routing core — not an HTTP hop that doubles your tail latency.
Explainable by default
Every approval, decline, mandate change and refund ships with reason codes and a deterministic replay record.
India-resident, RBI-aligned
VPC deployment, HSM-backed key custody, DPDP consent lineage, full data localisation — no exfil paths.
Operator economics, not vendor margin
Flat infra pricing + outcome-linked risk share — you keep the upside as you grow.
NPCI roadmap, on day zero
Mandates, AutoPay, UPI Lite, credit-on-UPI and conversational UPI ship the moment NPCI certifies — not next quarter.
Your data deserves a faster lane.
Join 2,400+ data teams who moved from slow dashboards to real-time intelligence — in under 20 minutes.