What Is Merchant Management Software?
Merchant management software is the operational platform used by banks, payment acquirers, PSPs, and PayFacs to onboard, configure, manage, and monitor merchants throughout the acquiring lifecycle.
It centralizes everything an acquiring business needs to manage a merchant relationship: the merchant's legal entity and business information, KYB/KYC records and compliance status, merchant hierarchy from acquirer level down to outlet and terminal, MCC classification, MDR and fee rules, settlement preferences, risk classification, terminal assignments, and ongoing operational workflows.
Unlike CRM systems that track relationship activity, or payment gateways that process transactions, merchant management software is the system of record for merchant configuration. Every downstream acquiring function — authorization, routing, settlement, reconciliation, and reporting — reads from the merchant record it manages.
Core capabilities
- Merchant onboarding and KYB/KYC management
- Merchant profiles and business information
- Merchant hierarchy (acquirer → PayFac → sub-merchant → outlet → terminal)
- Outlet and terminal management
- MCC classification and risk profiles
- MDR, pricing, and fee configuration
- Settlement preferences and bank account management
- Merchant portal and self-service access
- Reporting, analytics, and portfolio monitoring
- REST API and webhook integrations
Why Banks, Acquirers, PSPs & PayFacs Need Merchant Management Software
Every function of an acquiring business — onboarding, payment acceptance, settlement, reconciliation, risk, reporting — 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 merchant data is centralized, every acquiring function gets more accurate the moment the merchant record improves. Authorization engines consume correct MCC and risk tier data. Settlement engines apply the right MDR and fee rules. Reconciliation matches transactions to verified merchant and outlet records.
Acquirers that treat merchant management as platform infrastructure — rather than a database bolted on to other systems — are able to onboard faster, price more precisely, maintain compliance at scale, and grow a merchant portfolio without operational headcount growing in lockstep with merchant count.
Fragmented merchant data vs. unified merchant record
Merchant Management Software Features
A complete merchant management platform covers every dimension of the merchant relationship — from initial onboarding through ongoing operational lifecycle management. The capability map below shows what each module manages and how it relates to the broader acquiring function.
| Capability | What It Manages | Related Acquiring Function |
|---|---|---|
| Merchant Onboarding | Applications, approvals, activation, lifecycle status | Merchant acquisition / KYB |
| Merchant Profiles | Business information, legal entity, contacts, documents | Merchant master data |
| Merchant Hierarchy | Acquirer → PayFac → sub-merchant → outlet → terminal | Portfolio structure |
| Outlet Management | Locations, branches, operating status and relationships | Multi-location merchants |
| Terminal Management | POS, mPOS, SoftPOS, QR and device assignments | Payment acceptance |
| KYC/KYB | Documents, verification status, expiry and compliance records | Compliance |
| Pricing & MDR | MDR, fees, commissions, pricing tiers and overrides | Revenue / pricing |
| Risk Management | Risk classification, controls, limits and monitoring inputs | Risk / fraud |
| Settlement | Bank accounts, settlement preferences and configurations | Settlement |
| Merchant Portal | Merchant self-service, reporting and operational actions | Merchant operations |
| Reporting & Analytics | Portfolio, outlet, terminal and performance reporting | Operations / management |
| APIs & Integrations | REST APIs, webhooks, events and external integrations | Technology / ecosystem |
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 a shared view of the merchant portfolio.
Manual onboarding.
Merchant data entered by hand introduces errors and delays before a merchant ever processes a transaction.
Disconnected systems.
Onboarding, pricing, payment configuration, and settlement often live in separate tools, none of which share a single source of truth.
Inconsistent merchant data.
When the same merchant exists in multiple systems, discrepancies between them become a recurring operational burden.
Fragmented operations.
Support, risk, and commercial teams each work from a different partial view of the merchant relationship.
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 channel configuration, pricing, and contract all live on the same merchant record, so a change made in one place is immediately reflected everywhere else it is used.
One merchant record — from onboarding and KYB/KYC through active operations
Manual vs. Centralized Merchant Management
| Dimension | Manual / Disconnected | Centralized Merchant Management |
|---|---|---|
| Merchant data | Duplicated across systems, prone to drift | One merchant record, single source of truth |
| Onboarding | Manual entry, error-prone | Digital application feeding directly into the merchant record |
| Hierarchy & multi-location | Tracked in spreadsheets or separate tools | Modeled natively — hierarchy, stores, outlets, branches |
| Pricing & fees | Configured manually per merchant, hard to audit | Configurable pricing, MDR, and fee rules tied to the merchant record |
| Contracts | Stored separately from operational data | Linked directly to commercial configuration |
| Reporting | Assembled manually across systems | Live analytics from the same underlying record |
| Scaling to more merchants | Requires proportional operational headcount | Platform absorbs growth through configuration, not headcount |
Merchant Hierarchy Management
Merchant hierarchy management models the operational structure of an acquiring portfolio — from acquirer level down through PayFac, sub-merchant, outlet, and terminal. Policy, pricing, compliance rules, and reporting can be configured and inherited at any level of the hierarchy, which is particularly critical for PayFacs managing sub-merchants and for acquirers managing large, multi-location merchant networks.
Merchant hierarchy modeled from acquirer to terminal
Merchant & Outlet Management
Each merchant is represented by a complete, structured profile — carrying everything operations, risk, compliance, and commercial teams need to manage that relationship accurately across its full lifecycle.
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 code (MCC) classification driving risk policy and network reporting.
Risk Profiles
A live risk profile built from KYB/KYC verification outcomes and ongoing transaction behavior.
Merchant Status Management
Application, active, under review, suspended, or closed — status transitions logged and auditable across the lifecycle.
Merchant Lifecycle
A single view of where every merchant sits in their operational relationship with your acquiring platform.
Terminal Management
Payment acceptance configuration lives on the same merchant record as everything else, so enabling a new channel — POS, SoftPOS, QR, or gateway — is a configuration change rather than a separate provisioning process. Terminal assignments link devices to the correct merchant and outlet, and device status is tracked across the estate.
KYC/KYB & Compliance Management
KYB (Know Your Business) and KYC (Know Your Customer) records are maintained as first-class attributes of the merchant profile. Document types, verification status, expiry dates, and compliance workflow state are tracked per merchant and updated automatically when connected to third-party verification providers.
Compliance teams can configure review triggers, document expiry alerts, and risk classification rules that operate continuously across the portfolio — not just at onboarding. Every compliance action is logged against the merchant record for audit purposes.
KYB/KYC record — what is managed
Pricing & Fee Management
Commercial terms are configuration, not a spreadsheet maintained outside the platform. MDR rules, pricing tiers, fee schedules, and commission arrangements are stored on the merchant record and consumed directly by the settlement engine — so pricing changes apply immediately to settlement calculations without manual intervention.
Merchant Pricing
Set pricing per merchant, merchant group, or portfolio segment — with tier-based structures supported.
MDR Configuration
Configure merchant discount rate (MDR) structures by payment method, card type, and transaction type.
Fee Management
Define and apply fees consistently across the merchant portfolio with configurable rules per merchant or segment.
Commission Structures
Configure commission arrangements for ISOs, agents, partners, or referral relationships.
Contract Management
Keep commercial terms linked directly to the merchant record and the fee structures they govern.
How Merchant Management Software Fits Into a Merchant Acquiring Platform
Merchant management software sits at the operational core of a merchant acquiring architecture. Merchant configuration — hierarchy, MCC, pricing and MDR rules, settlement preferences, terminal assignments, and risk classification — is produced by the merchant management platform and consumed by every downstream acquiring service.
Merchant management is the configuration source for the entire acquiring stack
Merchant Management Software Integrations
Merchant management software integrates with the broader acquiring, compliance, and operational technology stack via REST APIs, webhooks, event-driven feeds, and batch import/export. The merchant record and its configuration are available to every system that needs them.
Supported integration methods
Merchant Operations Dashboard
Operations, risk, and commercial teams work from the same live view of the merchant portfolio — rather than assembling separate reports after the fact. Portfolio-level reporting, outlet-level monitoring, and merchant analytics are all driven from the same merchant record.
Who Uses Merchant Management Software?
Merchant management software serves multiple buyer teams within an acquiring organization. Each team works from the same merchant record but has distinct operational priorities.
Merchant Operations Teams
- Merchant lifecycle management — application through closure
- Outlet and terminal provisioning workflows
- Merchant status transitions and audit trails
- Portfolio-level operational visibility
Compliance & Risk Teams
- KYB/KYC document management and expiry tracking
- Risk classification and merchant limit configuration
- Compliance workflow and audit trail management
- Ongoing monitoring and review triggers
Finance & Pricing Teams
- MDR, fees, and commission configuration
- Revenue sharing and pricing tier management
- Settlement preference and bank account setup
- Contract terms linked to fee structures
Technology & Integration Teams
- REST API and webhook-based integrations
- Provisioning and system interoperability
- SSO and identity management
- Event-driven merchant data flows
Merchant Management Software Use Cases
Merchant management software is used across different acquiring business models — from commercial banks running direct merchant portfolios to PayFacs managing sub-merchant hierarchies and marketplaces managing seller settlement relationships.
Banks managing direct merchant portfolios
Commercial banks and regional financial institutions use merchant management software to administer their direct merchant acquiring portfolios — managing KYB, pricing, settlement, and risk classification from a single operational platform.
Payment acquirers managing large merchant networks
Acquirers managing thousands of merchants across multiple outlet types rely on merchant management to maintain accurate portfolio data, automate lifecycle workflows, and provide operations teams with a unified view.
PSPs managing merchants across payment methods
Payment service providers use merchant management to configure acceptance channels, manage merchant data, and ensure consistent pricing and settlement across POS, QR, and gateway payment methods.
PayFacs managing sub-merchant hierarchies
Payment facilitators (PayFacs) use hierarchical merchant management to onboard and manage sub-merchants under their acquiring license — configuring pricing, settlement splits, and compliance workflows at each level.
Fintechs launching acquiring services
Fintechs entering merchant acquiring use merchant management software as the operational core — connecting onboarding, payment acceptance, settlement, and reporting into a single merchant record from day one.
Marketplaces managing sellers and settlement
Marketplace platforms use merchant management to register sellers, configure settlement preferences, manage payout relationships, and maintain compliance records across their seller base.
How Merchant Management Compares
Merchant Management vs CRM
A CRM manages customer and relationship activity. Merchant management manages the operational and configuration lifecycle of payment merchants — the two are complementary, and merchant management is commonly integrated with an existing CRM rather than replacing it.
Merchant Management vs Payment Gateway
Merchant management manages who the merchant is, how they're structured, priced and classified. A payment gateway facilitates payment acceptance and transaction integration, consuming that configuration rather than duplicating it.
Merchant Management vs Merchant Onboarding Platform
Onboarding focuses on application, KYB/KYC and approval. Merchant management extends into ongoing merchant, outlet, terminal, pricing and operational lifecycle management after onboarding is complete
Security & Compliance
Merchant management software handles sensitive business data, KYB/KYC documents, financial configurations, and compliance records. The DigiPay.Guru platform is designed to support the security and data governance requirements of banks, regulated acquirers, PSPs, and PayFacs.
Role-Based Access Control
Configurable access permissions ensure each team sees and acts on only the merchant data relevant to their function.
Audit Trails
Every change to a merchant record, compliance status, or configuration is logged with user, timestamp, and action for regulatory and operational audit purposes.
Data Encryption
Sensitive merchant and document data is encrypted at rest and in transit, in line with the security requirements of financial services deployments.
Compliance Workflow Controls
Document expiry, review triggers, and compliance workflow gates prevent merchants from proceeding through the acquiring lifecycle without completing required compliance steps.
Why DigiPay.Guru
DigiPay.Guru treats merchant management as core acquiring platform infrastructure. Merchant profiles, hierarchy, KYB/KYC, pricing, settlement, terminal management, and risk classification all live on the same merchant record — so every acquiring function from authorization through settlement reads from a consistent, current source.
Banks, acquirers, PSPs, and PayFacs use DigiPay.Guru to manage merchant portfolios across merchant onboarding, lifecycle management, outlet and terminal provisioning, compliance, and operational reporting — without the operational overhead of disconnected systems.
Merchant Acquiring Platform
The full acquiring stack — onboarding, management, payment acceptance, settlement, and reporting — on one platform.
Learn moreMerchant Onboarding
Digital application, KYB/KYC automation, and configurable approval workflows connecting directly to the merchant record.
Learn moreSettlement Engine
Settlement calculations driven by MDR, fee schedules, and preferences configured in merchant management.
Learn moreMerchant Portal
Self-service access for merchants, driven by the same merchant record managed by the acquirer.
Learn moreFrequently asked questions
Discuss Your Merchant Management Architecture
See how DigiPay.Guru can support merchant onboarding, hierarchy, outlets, terminals, pricing, compliance and settlement configuration within your acquiring platform.
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.
Let's Talk! Have Questions? We’re Here to Help....
Fill all your details in the form and one of our business consultant will get in touch you within 24 hours.
2019
Founded in
120+
In-house Tech experts
15+
Country served
100k+
Customers Achieved by our clients
10+
Paytech leader partnerships
8+
Fintech Platforms Introduced