Merchants managed
120,000+
AR
Acme Retail Pvt Ltd
Merchant ID: MID·48213 · Active
Verified
Profile
Risk
Pricing
Documents
Business typeRetail — Apparel
MCC code5651
Settlement cycleT+1, daily
Risk tierLow risk

Why Merchant Management Matters

Every function of an acquiring business — onboarding, payment acceptance, settlement, reconciliation, risk, reporting — ultimately reads from and writes to the same underlying object: the merchant record. When that record is fragmented across systems, every function built on top of it inherits the fragmentation. When it is centralized, every function gets more accurate the moment merchant management improves.

That is why merchant management is not a peripheral admin tool in a well-run acquiring business — it is the operational core. It is where a merchant's identity, hierarchy, risk profile, payment channels, pricing, and contract terms live as one connected record.

Acquirers that treat merchant management as infrastructure, rather than as a database bolted onto other systems, are the ones able to onboard faster, price more precisely, and scale a merchant portfolio without operational headcount growing in lockstep with merchant count.

Onboarding
System A
Risk data
Spreadsheet
Pricing sheet
Email thread
AR
Acme Retail Pvt Ltd
Single merchant record
OnboardingComplete
Risk profileLow risk
Pricing planTier 2
Devices linked3 terminals
ComplianceUp to date

Fragmented data vs. unified merchant record

Challenges of Traditional Merchant Management

Most acquirers still manage merchant data across disconnected tools — a pattern that introduces errors, slows onboarding, and prevents teams from working from one shared view of the merchant.

01

Manual onboarding.

Merchant data entered by hand introduces errors and delays before a merchant ever processes a transaction.

02

Disconnected systems.

Onboarding, pricing, payment configuration, and settlement often live in separate tools, none of which share a single source of truth.

03

Inconsistent merchant data.

When the same merchant exists in multiple systems, discrepancies between them become a recurring operational burden.

04

Fragmented operations.

Support, risk, and commercial teams each work from a different partial view of the merchant relationship.

05

Scaling difficulty.

Manual processes that work for hundreds of merchants break down at thousands, forcing operational headcount to grow with the portfolio instead of the platform absorbing that growth.

Centralize the Complete Merchant Lifecycle

DigiPay.Guru's Merchant Management Platform is the single system of record for every merchant an acquirer manages, from the first onboarding application through years of ongoing operation. Profile, hierarchy, payment configuration, pricing, and contract all live on the same merchant record, so a change made in one place is immediately reflected everywhere else that record is used.

1
Onboard
2
Configure
3
Activate
4
Monitor
5
Grow

One merchant record, from onboarding to ongoing operations

Manual vs. Centralized Merchant Management

DimensionManual / Disconnected ManagementCentralized with DigiPay.Guru
Merchant dataDuplicated across systems, prone to driftOne merchant record, single source of truth
OnboardingManual entry, error-proneDigital application feeding directly into the merchant record
Hierarchy & multi-locationTracked in spreadsheets or separate toolsModeled natively — hierarchy, stores, outlets, branches
Pricing & feesConfigured manually per merchant, hard to auditConfigurable pricing, MDR, and fee rules tied to the merchant record
ContractsStored separately from operational dataLinked directly to commercial configuration
ReportingAssembled manually across systemsLive analytics from the same underlying record
Scaling to more merchantsRequires proportional operational headcountPlatform absorbs growth through configuration, not headcount

Manage Every Merchant Relationship

Each merchant is represented by a complete, structured profile — not a row in a spreadsheet, but a record that carries everything operations, risk, and commercial teams need to manage that relationship.

Merchant Profiles

A complete record of business identity, contacts, and processing history for every merchant.

Business Information

Legal entity, ownership, and registration details captured once and reused across every workflow.

Merchant Categories (MCC)

Standardized merchant category classification driving risk policy and network reporting.

Risk Profiles

A live risk profile built from verification outcomes and ongoing transaction behavior.

Merchant Status Management

Application, active, under review, suspended, or closed — status transitions logged and auditable.

Merchant Lifecycle

A single view of where every merchant sits in their relationship with your business.

Manage Merchant Organizations

Merchants are rarely a single flat entity. DigiPay.Guru models the real structure of a merchant organization — parent companies, subsidiaries, and every physical location beneath them.

Merchant Hierarchy

Parent and child merchant relationships modeled and managed natively.

Corporate Structures

Multi-entity organizations represented accurately, not flattened into a single record.

Store Management

Every store under a merchant managed individually while rolling up to one consolidated view.

Outlet Management

Outlet-level configuration for payment methods, terminals, and reporting.

Branch Management

Branch-level operational control for merchants organized around a branch network.

Merchant Groups

Apply policy, pricing, or reporting across a defined group of merchants at once.

Acme Retail Group
Corporate structure
Store hierarchy
42 outlets
Outlet management
Franchise + owned
Branch groups
Regional pricing
Mumbai12 outlets
Delhi18 outlets
Bangalore8 outlets
Pune4 outlets

Merchant hierarchy, modeled the way your merchants are actually organized

Configure Merchant Services

Payment acceptance configuration lives on the same merchant record as everything else, so enabling a new channel for a merchant is a configuration change, not a separate provisioning process.

Payment Channels

Configure which acceptance channels are available to each merchant.

Learn more

POS Assignment

Assign and track POS terminals against the merchant and outlet they serve.

Learn more

SoftPOS Enablement

Turn on SoftPOS acceptance for eligible merchants without a hardware rollout.

Learn more

QR Configuration

Configure static or dynamic QR acceptance per merchant or outlet.

Learn more

Payment Gateway Configuration

Enable online acceptance and connect it to the merchant's existing acquiring relationship.

Learn more

Settlement Profiles

Define settlement cycle, destination account, and deduction rules per merchant.

Learn more

Pricing & Commercial Management

Commercial terms are configuration, not a spreadsheet maintained outside the platform. Pricing changes apply directly to settlement calculations, and contract terms stay connected to the fee structures they govern.

Merchant Pricing

Set pricing per merchant, merchant group, or segment.

MDR Configuration

Configure merchant discount rate structures by payment method and transaction type.

Fee Management

Define and apply fees consistently across the merchant portfolio.

Commission Structures

Configure commission arrangements for partners, ISOs, or referral relationships.

Contract Management

Keep commercial terms linked directly to the merchant record they govern.

Merchant Operations Dashboard

Operations, risk, and commercial teams work from the same live view of the merchant portfolio, rather than reconciling separate reports after the fact.

Merchant Activity

Live visibility into onboarding, transaction, and status activity across the portfolio.

Operational KPIs

Track onboarding time, activation rate, and other operational metrics that matter to your team.

Performance Monitoring

Monitor merchant and portfolio performance against volume and risk expectations.

Merchant Analytics

Segment and analyze the portfolio by geography, category, channel, or risk tier.

Portfolio Management

Manage the full merchant portfolio from one dashboard instead of assembling views across systems.

Merchant Operations Dashboard
Merchant activity
8,412
Compliance KPIs
98.4%
Real-time monitoring
Live
Merchant analytics
+12.6%
Merchant portfolio growth
Portfolio management
1,204 active merchants
86 pending review
312 new this quarter
14 flagged for risk
Top merchants by volume
Acme Retail LtdNorthline Bank Merchants▲ 8.2%
Metro Wallet ServicesUrban Grocery Chain▲ 5.1%

Why DigiPay.Guru Merchant Management

Merchant management is treated as core platform infrastructure at DigiPay.Guru, not an administrative layer added on top of processing. Every other capability — onboarding, payment acceptance, settlement, reconciliation, and reporting — reads from the same merchant record, so improvements to merchant management compound across the entire platform rather than staying isolated to one screen.

Frequently asked questions

Merchant management software is the platform an acquirer uses to administer every aspect of the merchant relationship — profiles, business hierarchy, payment channel configuration, pricing, contracts, and ongoing performance — in one centralized system rather than across disconnected tools.

Merchant lifecycle management is the tracking and control of a merchant's status and configuration from application through onboarding, active processing, and eventual closure, with every transition logged against the merchant record.

Yes. Store, outlet, and branch management let a merchant with multiple locations manage every site under one merchant profile, with location-level configuration rolling up to a consolidated view.

Yes. Merchant hierarchy and corporate structure tools let acquirers model parent organizations, subsidiaries, and merchant groups, applying policy at the appropriate level of the hierarchy.

Yes. Merchant pricing, MDR configuration, fee management, and commission structures are all configurable per merchant, merchant group, or segment.

Yes. Contract management is built into the merchant record, connecting commercial terms directly to the pricing and fee configuration applied to that merchant.

Yes. Merchants can view and, where permitted, update their own profile and business information through the self-service merchant portal.

Merchant configuration — pricing, fee schedules, and settlement profiles — feeds directly into the settlement engine, so settlement calculations always reflect the merchant's current commercial terms.

Yes. POS assignment, SoftPOS enablement, QR configuration, and payment gateway configuration are all managed from the same merchant management platform.

Yes. The platform is built to manage portfolios ranging from a handful of merchants to enterprise-scale portfolios spanning multiple hierarchies, geographies, and payment channels.

Ready to Simplify Merchant Management?

Talk to the DigiPay.Guru team about your current merchant portfolio and operational setup, or book a demo to see the merchant management platform in action.

Section Page CTA

Look through your eyes of insight to our insightful thoughts

DigiPay.Guru is born to simplify financial transactions. We love discussing the latest finTech solutions. We write regular blogs where we cover insightful topics with our insightful thoughts to cater you with imperative informations.