Nexus Bank Acquiring Console Live
PROCESSING
12,481
Merchants Live
4,381
TPS now
₹4.3Cr
Today's Volume
TOP MERCHANTS BY VOLUME
Puma India
MID:40221900 Visa
₹18,000NO APPR
Nexmart
MID:40281190 Mastercard
₹8,400BE DECL
Zara India
TID:TID:1120 RuPay
₹2,400NO APPR
RetailCo Store 71
₹28,500REVIEW
Adidas India
MID: MID 40607995 BL
₹5,280NO APPR
Approval Rate
99.2%
Chargeback%
0.42%
Avg Merchant
₹18.4L
Merchants QC
9,310
White-labelled as Nexus Bank
Merchants see your brand. Not ours.

POS Terminal Management

Everything You Need to Run Your Entire Terminal Fleet

From warehouse to merchant outlet — DigiPay.Guru's POS Acquiring Platform manages every terminal across your network with real-time visibility, remote provisioning, and zero field visits.

8 wks

From contract to live production

100%

White-label — your brand throughout

99.999%

Switch & platform uptime SLA

50M+

Transactions processed monthly

Banks have the merchant relationships.

Banks have the regulatory standing.

Banks have the settlement rails.

What most banks do not have is the acquiring infrastructure to use any of it.

The payment acquiring market is one of the fastest-growing revenue streams in banking. Every card tap at a POS terminal, every QR payment at a market stall, every contactless transaction at a fuel station — a bank that acquires generates MDR income, interchange revenue, and deeper merchant relationships that compound over time.

But building acquiring infrastructure from scratch is a two-to-three year project. An ISO 8583 switch. A POS terminal management system. A merchant hierarchy engine. A settlement and reconciliation platform. Fraud and risk controls. Scheme certifications. It requires specialised teams that most banks do not have — and time that no bank can afford to spend while fintechs take market share.

DigiPay.Guru solves this. Not with a roadmap. With a platform that is already built, already certified, already deployed — and available under your bank's brand in eight weeks.

The Real Problems

Seven Things That Are Costing Your Bank Right Now.

These are not hypothetical risks. They are the operational realities of every bank that has tried to run merchant acquiring without purpose-built infrastructure.

01

You are losing merchants to fintechs that can onboard them in hours.

A merchant who approaches your bank for a POS terminal today waits days for KYC, weeks for hardware delivery, and another week for activation. The fintech across the street onboards them digitally in under 24 hours. You lose the relationship before the terminal even ships.

MARKET REALITY
3-6 weeks

Average bank merchant onboarding time vs. 24 hours for digital-first acquirers. Every week of delay is a week the merchant considers alternatives.

02

Your MDR revenue is leaking because no one can see where it goes.

When MDR rates are managed in spreadsheets and applied manually during settlement, errors accumulate invisibly. Wrong rates applied to the wrong card types. Interchange miscalculation that you only discover at audit. The margin you thought you were earning is not the margin you are actually keeping.

ESTIMATED LEAKAGE
2-8 bps

Typical MDR revenue leakage from manual fee management and interchange miscalculation. On 100 Cr monthly volume, that is 7-8 lakhs disappearing every month.

03

Your reconciliation team is closing books manually — at midnight.

Settlement files from the switch. Clearing reports from the scheme. Bank credits from NPCI. Three sources, reconciled by a team of people running VLOOKUP formulas at 11 PM. One missed row, one transposition error, one file that uploaded with the wrong date — and your CFO has an unreconciled balance that takes two days to trace.

OPS COST
8-14 hrs/day

Average time spent on manual settlement reconciliation by banks without automated systems. That is a full-time team doing work that software should do.

04

You find out about terminal failures the same way your merchants do — after the fact.

A POS terminal that goes offline at 9 AM is not reported to your operations team until the merchant calls your helpline at noon. Three hours of lost transaction volume. A frustrated merchant. A support ticket that takes another hour to resolve. Multiply this across a fleet of thousands, and the cost — in revenue, in relationship damage, in ops effort — is significant.

AVG DETECTION LAG
2-4 hours

Time between a terminal going offline and your operations team being notified, at banks without real-time device monitoring. Every hour offline is lost transaction volume for your merchant.

05

Your fraud controls are reactive. They catch fraud after the chargeback lands.

Without real-time pre-authorization fraud scoring, velocity checks, and blacklist enforcement, your first signal of a fraud event is the chargeback notice from the scheme — days or weeks after the transaction occurred. By then, the damage is done. The funds may be unrecoverable. And if your chargeback rate approaches scheme limits, the consequences escalate beyond individual losses.

SCHEME THRESHOLD
1.0%

Visa chargeback monitoring programme threshold. Banks above this face programme fees, mandatory remediation plans, and ultimately risk of losing acquiring privileges.

06

Your ISO 20022 migration has been "planned" for three years.

Visa, Mastercard, and SWIFT are actively migrating to ISO 20022. Your current switch runs on ISO 8583 — and building a translation layer, or migrating the switch itself, is a multi-year internal project that competes with every other priority in your technology roadmap. The deadline, however, does not move.

MIGRATION WINDOW
Closing

Visa and Mastercard ISO 20022 migration timelines are fixed. Banks that do not have an ISO 20022-capable switch in place face connectivity disruptions and compliance findings.

07

You cannot offer PayFac or sub-merchant programmes because your platform was not built for it.

The most profitable acquiring models today are not direct merchant relationships — they are PayFac structures where your bank acts as the principal acquirer for a network of sub-merchants managed by a PayFac. Your current acquiring infrastructure has a flat merchant model. There is no hierarchy. No fee cascading. No sub-merchant isolation. You cannot participate in the market fastest-growing segment.

MARKET OPPORTUNITY
$42B

Global PayFac market size by 2028. Banks that cannot offer PayFac infrastructure will watch this revenue flow to those that can — while still bearing the regulatory responsibility as the underlying acquirer.

The Answer

One Platform. Every Problem Solved.

DigiPay.Guru is not a product. It is a complete acquiring infrastructure — every component a bank needs to run a full-scale merchant acquiring programme. Integrated, certified, and white-labelled under your brand. You own the merchant relationship. We operate the infrastructure.

ISO 8583 & ISO 20022 Acquiring Switch

A certified payment switch that processes every card transaction in under 80ms, with intelligent routing, automatic fallback, and a built-in ISO 8583 to ISO 20022 translation layer — so your migration timeline is flexible.

Learn more

Merchant Hierarchy & Management System

Model any acquiring structure — direct merchants, ISOs, PayFacs, and sub-merchants — in a configurable hierarchy with fee cascading, KYC management, and outlet-level controls.

Learn more

POS Terminal Management Platform

Remote provisioning, OTA key injection, firmware updates, and real-time health monitoring for every POS, SoftPOS, and mPOS terminal in your fleet — from a single console.

Learn more

Automated Settlement & Reconciliation

MDR calculation, interchange management, commission splits, T+0/T+1 settlement cycles, and three-way automated reconciliation — the entire financial close, without a single spreadsheet.

Learn more

Real-Time Fraud & Risk Management

Pre-authorization fraud scoring, velocity checks, configurable rule engine, and blacklist management — catching threats before they authorize, not after the chargeback arrives.

Learn more

mPOS & SoftPOS Acceptance

Extend your acquiring reach to micro-merchants and field agents with white-label mPOS apps and SoftPOS — NFC, QR, and card acceptance on any Android device, no hardware required.

Learn more

What Banks Actually Gain

Four Outcomes. Not Four Features.

Features are what the platform does. Outcomes are what your bank gets. These are the four things that change when a bank deploys DigiPay.Guru.

Time to Market

You Stop Losing Merchants Before You Have Even Started.

Eight weeks from contract signature to live transactions. Not a prototype. Production.

Building acquiring infrastructure in-house takes 18-36 months and a team of specialists your bank may not have — payment protocol engineers, HSM key management specialists, scheme certification experts, and reconciliation system architects. By the time you finish, the market has moved.

DigiPay.Guru is pre-built, pre-certified, and pre-integrated with Visa, Mastercard, NPCI, and major bank hosts. Your implementation is a configuration project, not a development project. You go live in eight weeks — and you start generating MDR revenue from week nine.

Week 1-2: Requirements, merchant data migration, branding configuration
Week 3-5: Host connectivity, terminal provisioning, UAT
Week 6-8: Parallel run, scheme sign-off, go-live
Week 9 onwards: Live merchant transactions, MDR income begins
implementation-timeline · weeks8 WEEKS
Week 1-2Requirements & configIN PROG
Week 3Host connectivity setupNEXT
Week 4-5UAT & terminal provisioningQUEUED
Week 6Scheme certificationSCHED
Week 7-8Parallel run & go-liveQUEUED
Build cost
$0 (pre-built)
Cert timeline
Included
First MDR income
Week 9
vs. 18-36 months to build in-house

Revenue Precision

Every Basis Point of MDR. Captured. Accounted For.

The MDR engine applies the correct rate to every transaction — by scheme, card type, MCC, and channel — automatically.

A bank running merchant acquiring on a manual or semi-automated MDR system is almost certainly undercharging some merchants and over-crediting others — and has no reliable way to know which. The DigiPay.Guru MDR engine maintains a complete fee matrix per merchant and applies it to every transaction at settlement time.

The result is a bank that knows exactly what it earns on every transaction, can model the impact of fee changes before making them, and can produce MDR income statements for any time period in seconds.

Per merchant MDR matrix by scheme, card type, channel, and MCC
Interchange plus and blended MDR models both supported
MDR income reporting by merchant, portfolio, and date range
Fee simulation: model revenue impact before changing any rate
MDR Income · Today · portfolio-wideLIVE
Gross Vol₹4.31 Cr
MDR Charged₹3,41,0001.40% blended
Interchange₹1,95,360Paid out
Scheme Fees₹21,550Paid out
Bank Net₹1,24,9700.49% spread
₹1.24L acquirer margin today · Zero manual calculation

Risk & Compliance

Your Chargeback Rate Stays Well Below the Scheme Threshold. Always.

Fraud is stopped before it authorizes. Chargebacks are tracked before they escalate. Your scheme standing is never at risk.

A bank's acquiring licence is its most valuable payment asset — and it is also the asset most at risk when fraud and chargeback management fails. Visa and Mastercard both run chargeback monitoring programmes that escalate through warnings, programme fees, and ultimately termination of acquiring privileges.

DigiPay.Guru's risk stack operates pre-authorization — every transaction is scored, velocity-checked, and blacklist-matched before the authorization is forwarded to the host. Fraud is declined before it reaches the scheme.

Pre-authorization fraud scoring — fraud never reaches the scheme
Real-time chargeback rate per merchant — alert before threshold breach
Automatic merchant risk grading and reserve holdback
PCI-DSS Level 1 certified infrastructure — audit findings become history
Risk Dashboard · PROTECTEDPROTECTED
CB Rate
0.42%SAFE
Scheme Limit
1.0% (Visa)
Risk Level
0.38% comfortable
Fraud blocked
47 today
Fraud loss
$0 today
High-risk merch
3 on reviewWATCH
PCI Status
Level 1 certified
Last audit
0 findings
Portfolio protected · CB well below threshold · PCI clear

Scale & PayFac

Your Bank Becomes the Principal Acquirer for an Entire Ecosystem.

The most profitable acquiring structure is not one-to-one. It is one bank to many PayFacs to thousands of sub-merchants.

DigiPay.Guru's merchant hierarchy engine supports unlimited depth — Bank to ISO to PayFac to Sub-Merchant to Outlet to Terminal — with fee rules, compliance requirements, and settlement preferences configured independently at each level and cascading automatically to those below. Your bank earns acquiring revenue from thousands of merchants it has never directly interacted with, while the PayFac handles the merchant level relationship.

Unlimited hierarchy depth — Bank, ISO, PayFac, Sub-Merchant, Outlet, Terminal
Automated multi-party settlement — every entity paid correctly in the same batch
PayFac self-service portal — sub-merchants onboard without bank involvement
Bank retains regulatory oversight and scheme standing throughout
hierarchy.view · acquiring_structureLIVE
Nexus Bank LtdPrincipal
RetailCo PayFacPayFac
Puma India · Zara · AdidasSub-Merch
44 locations activeOutlets
112 onlineTerminals
Bank MDR net
0.49% · ₹1.24L/day
PayFac cut
0.12% · auto-split
Sub merch vol
₹4.31 Cr today
1 bank · 1 PayFac · 3 sub-merchants · 44 outlets · 112 terminals

Proof Points

The Numbers Banks Ask About First.

8

Weeks to live production — guaranteed.

Not a pilot. Not a proof of concept. A fully operational merchant acquiring system under your bank's brand, processing real transactions with real merchants, in eight weeks from contract signature. We have done it before. We will do it for you.

0

Scheme certification projects for your team.

Visa, Mastercard, and NPCI certifications are already complete. You do not inherit a certification backlog. You do not need a team of scheme-certified engineers. You plug in to a platform that is already approved. Your IT team handles configuration, not protocol engineering.

100%

White-label. Your brand on everything.

The merchant portal, the mobile app, the terminal screens, the e-receipts, the settlement reports, the support documentation — all carry your bank's brand and identity. Your merchants never see DigiPay.Guru. They see you. That is how it should be.

The Honest Comparison

Build vs. Buy. The Numbers Are Clear.

CapabilityBuilding In-HouseDigiPay.Guru
Time to first live transaction✗ 18-36 months✓ 8 weeks
Visa & Mastercard certification✗ 6-12 months per scheme✓ Pre-certified. Included.
ISO 20022 readiness✗ Multi-year migration project✓ Built-in translation layer
PayFac / sub-merchant hierarchy✗ Rebuild from scratch✓ Unlimited depth, out of the box
Automated reconciliation✗ Manual or bespoke build✓ Three-way auto-reconciliation
Real-time fraud scoring✗ Rules only, if built at all✓ ML scoring + rules + blacklists
White-label under bank brand✓ Yes (if a priority)✓ Yes. Fully.
Upfront infrastructure cost✗ ₹20-80 Cr estimate✓ Subscription — no capex

Explore the Stack

Every Component Your Bank Needs.

CORE INFRASTRUCTURE

Acquiring Switch Platform

ISO 8583 + ISO 20022. <80ms authorization. 10,000+ TPS. Host connectivity to Visa, Mastercard, RuPay, and your own bank hosts.

Learn more
FINANCIAL ENGINE

Merchant Settlement System

MDR calculation, interchange management, T+0/T+1 settlement cycles, automated three-way reconciliation, and audit-ready financial reports.

Learn more
RISK LAYER

Merchant Risk Management

Pre-authorization fraud scoring, velocity checks, configurable rule engine, and blacklist management. Sub-50ms. 99.6% accuracy.

Learn more

Frequently asked questions

Fully white-label. Every customer-facing surface — the merchant portal, merchant mobile app, POS terminal screens, e-receipts, SMS notifications, settlement reports, and support documentation — carries your bank's name, logo, and branding. DigiPay.Guru does not appear anywhere in the merchant's experience. The platform is deployed under your bank's domain, published to app stores under your bank's developer account, and referenced in all communications as your bank's product. Your merchants have a relationship with your bank. Not with us.

Your bank holds the scheme membership. DigiPay.Guru is the technology infrastructure provider — the platform that processes transactions on behalf of your bank under your bank's scheme credentials. This means your bank retains full regulatory standing as the acquirer, full control over merchant relationships and risk policies, and full ownership of the acquiring revenue. DigiPay.Guru provides the technology. Your bank holds the licence.

The eight-week timeline is achievable because the platform is pre-built and pre-certified. Week 1–2 covers requirements gathering, branding configuration, merchant data migration planning, and host connectivity mapping. Weeks 3–5 cover host connectivity setup, terminal provisioning for your initial POS fleet, and user acceptance testing. Week 6 handles scheme sign-off and compliance review. Weeks 7–8 run a parallel operation alongside your existing system, followed by the cut-over to full production. The implementation team from DigiPay.Guru is embedded with your team throughout. The eight weeks assumes your bank's IT and compliance teams are available to review and approve at each milestone.

Yes. The merchant hierarchy engine supports PayFac structures natively. Your bank acts as the principal acquirer. PayFacs are registered as Level 2 entities under your bank's hierarchy. Each PayFac can onboard their own sub-merchants through a self-service portal, and all sub-merchant transactions flow through your bank's acquiring infrastructure. MDR revenue flows up the hierarchy: sub-merchant pays MDR to the PayFac, PayFac pays a share to the bank. Commission splits are calculated and distributed automatically in the same settlement run. Your bank retains full visibility and control over every sub-merchant in the PayFac's network — including risk monitoring, KYC status, and chargeback rates.

DigiPay.Guru operates on a subscription model with no large upfront capital expenditure. Pricing is structured as a platform fee (based on transaction volume tiers) plus a one-time implementation fee for the eight-week deployment. There are no per-module licence fees — the full platform stack is included. Volume-based pricing means your cost scales with your revenue, not ahead of it. Detailed pricing is shared during the demo call after we understand your expected transaction volumes and merchant portfolio size.

Your transaction data, merchant data, and settlement records are stored in data centres within the geography specified in your contract — Indian banks can specify India-only data residency, which is fully supported. DigiPay.Guru staff do not have access to your merchant data or transaction records without explicit written authorisation from your bank. All data is encrypted at rest and in transit. The platform is PCI-DSS Level 1 certified, and the data handling practices are auditable by your internal audit team or by an approved third-party auditor at any time.
One more thing.

The Banks That Win Merchant Acquiring Won't Wait Two Years to Build.

The window to capture merchant acquiring market share is open right now. Fintechs are moving. Other banks are moving. The question is whether your bank is moving with them — or watching from the sidelines.

Request a Demo
Section Page CTA

Read our insightful blogs!

Stay updated with the latest trends and innovations in finTech with our insightful blogs.