Settlement at Scale
The Numbers Behind Every Settled Transaction
DigiPay.Guru's Settlement System is built for volume, accuracy, and compliance — from a single merchant to a network of thousands.
Why It Exists
Three Things That Are True About Payment Settlement
A wrong settlement is worse than no settlement.
Every rupee that lands in the wrong account — or doesn't land at all — becomes a dispute, a support ticket, or a regulatory finding. Settlement systems that get it almost right are the most expensive systems you can operate. Precision isn't a feature. It's the entire product.
Manual reconciliation is a liability masquerading as a process.
When your reconciliation team exports CSVs and cross-references bank files at midnight, you are one human error away from a financial discrepancy that takes weeks to resolve. Automation doesn't just save time — it eliminates an entire category of risk that manual processes permanently carry.
Complexity is not an excuse for opacity.
MDR, interchange, processing fees, ISO commissions, sub-merchant splits — settlement is genuinely complex. But complexity should be contained inside the engine, not exposed to your merchants and your ops team. The output should always be simple: who gets paid what, and when.
Settlement Engine
The Engine Behind Every Cleared Rupee
The Settlement Engine is the core of the system — a rule-based, event-driven processor that takes a raw transaction and produces a verified, audited net payout for every party in the acquiring chain.
How it Works
From Transaction to Bank Credit. Automatically.
Every cleared transaction triggers a settlement pipeline. The engine reads the merchant's fee profile, applies MDR, deducts interchange, calculates commissions, and computes the net payout — in milliseconds.
Batches run on configurable cycles: T+0 for instant settlement, T+1 for next-day, or custom windows. Every batch produces an immutable audit record. Nothing is manual. Nothing is approximated.
Configure once. Settle forever. The engine reads merchant-level rules from the Merchant Management System and applies them automatically to every transaction in every batch — no manual intervention required at run time.
In a PayFac, ISO, or hierarchical acquiring model, a single transaction produces obligations for multiple parties. The engine splits and routes each party's share automatically — acquirer, ISO, sub merchant, and gateway — in a single settlement run.
Processing Fees
Every Fee. Calculated Correctly. Every Time.
Merchants pay the fee they agreed to. Not one paisa more, not one paisa less.
Processing fees in payment acquiring are rarely simple. A merchant's fee profile might include a flat per-transaction charge, a percentage of the transaction value, a minimum floor, a maximum cap — applied differently for domestic vs. international cards, and different again for credit vs. debit.
The Fee Management module maintains a structured fee matrix per merchant and applies it to every transaction at the moment of settlement — not as an approximation, but as a calculation verified against the fee rule in force at that exact date and time.
Commissions & Revenue Splits
Every Partner Gets Their Share. Automatically.
The acquiring chain isn't two parties. It's five. Everyone gets paid correctly, every cycle.
In a modern acquiring ecosystem, revenue doesn't flow from one entity to another — it flows through a network of relationships: acquirer banks, ISOs, payment facilitators, sub-agents, and technology partners all have a stake in each transaction.
The Commission Engine models this network as a configurable revenue sharing tree. Each node in the hierarchy has its own commission rule — a percentage of gross revenue, a percentage of MDR collected, or a flat per-transaction fee — and the engine computes, aggregates, and distributes every party's share in the same settlement run that pays the merchant. No disputes about who gets what.
MDR — Merchant Discount Rate
MDR Isn't Just a Number. It's a Revenue Architecture.
The MDR you charge a merchant determines your margin. The MDR engine makes sure every basis point is applied correctly.
Merchant Discount Rate (MDR) is the percentage of each transaction that a merchant pays for the privilege of accepting cards. It sounds simple — but in practice, MDR is a layered structure. The acquirer sets a headline MDR for the merchant. From that MDR, the acquirer must fund the interchange going to the issuing bank, the scheme assessment fees paid to Visa or Mastercard, and their own processing costs. What remains is the acquirer's spread — and that margin lives or dies on the accuracy of MDR application at scale.
DigiPay.Guru's MDR engine manages this entire stack. It applies the correct MDR per transaction based on card scheme, card type, transaction channel, and amount band — and tracks the disaggregation of that MDR into interchange, scheme fees, and acquirer margin automatically.
Interchange Management
Interchange Is Not a Cost. It's a Variable.
Interchange rates shift with card type, merchant category, and scheme rules. The system tracks every one of them.
Interchange is the largest single cost in a payment acquiring operation. It is paid by the acquirer to the card issuer for every card transaction, and it varies by card scheme, card product type, merchant category code, transaction type, and country. Visa and Mastercard publish interchange tables with dozens of rate categories — and the rate applied to a specific transaction depends on how accurately the acquirer qualifies it.
Misqualification — submitting a transaction with incorrect data that triggers a higher interchange tier — is one of the most common and expensive mistakes in acquiring operations. DigiPay.Guru's Interchange Management module maintains current interchange tables, applies the correct tier to every transaction, and flags qualification failures before they hit your settlement. It also models interchange-plus pricing, allowing you to pass through the exact interchange cost to merchants with transparency, and retain your markup separately.
Automated Reconciliation
Reconciliation That Closes Itself.
Every transaction that enters the system must exit it — matched, verified, and accounted for. Automatically.
Reconciliation is the process of confirming that what the payment network says happened matches what your system recorded — and that the money that was supposed to move actually did. In large acquiring operations, this means matching millions of transaction records across multiple sources: your switch, the card scheme, the issuing bank, and your own settlement files.
Manual reconciliation at this scale is not just slow — it's structurally unreliable. DigiPay.Guru's Reconciliation Engine automates this entire process. It ingests transaction data from every source, matches records using a configurable ruleset, flags exceptions automatically, and produces a daily reconciliation report that closes the books — verified to the last paisa.
Full Settlement Coverage
Nothing Falls Through. Nothing Is Estimated.
Six capabilities that together make DigiPay.Guru's settlement system the most complete in the acquiring stack.
Real-Time Settlement Visibility
Every batch, every transaction, every payout — visible in real time on a single dashboard. Merchants see their settlement status. Ops sees exceptions. Finance sees the ledger. Nothing is hidden.
Configurable Settlement Cycles
T+0 same-day settlement for premium merchants. T+1 next-day for standard. T+2 or weekly for risk-controlled accounts. Each merchant's cycle is configured independently — no platform-wide restrictions.
Chargeback & Dispute Management
Chargebacks automatically deducted from the next settlement cycle. Full chargeback lifecycle tracking — retrieval request, chargeback notice, representment, pre-arbitration, and final resolution — with notification at each stage.
Financial Reporting & GL Export
Daily settlement reports, MDR income statements, interchange cost analysis, and commission ledgers — all exportable in CSV, PDF, or via API. Built for finance teams who need audit-ready outputs, not raw database dumps.
Reserve & Holdback Management
Configure rolling or fixed reserves for high-risk merchants. Reserve funds are tracked separately in the settlement ledger and released automatically at the end of the reserve period — no manual release required.
Core Banking & ERP Integration
Settlement data flows directly into your core banking system or ERP via REST API or SFTP batch file — in any standard format. No CSV downloads. The books reconcile themselves.
Platform Ecosystem
Settlement Is the Final Step
of a Larger System
The Settlement System connects directly to every upstream product — transactions, merchants, fees, and terminals all feed into a single, closed-loop financial operation.
Merchant Acquiring Platform
Transactions authorized by the Acquiring Platform flow directly into the Settlement Engine. Every cleared authorization creates a settlement obligation — automatically queued for the next batch.
Learn moreMerchant Management System
Fee rules, MDR rates, commission structures, and merchant bank accounts are all configured in the MMS. The Settlement Engine reads these at runtime — no manual entry per batch.
Learn morePOS Acquiring Platform
Every POS terminal transaction enters the settlement pipeline. Terminal-level transaction data provides the granularity needed for per-outlet reconciliation and MCC-based fee application.
Learn moreOne More Thing.
Settlement Should Be Invisible to Everyone Except the Merchant's Bank.
When settlement works the way it should, nobody talks about it. Merchants see cleared funds. Finance sees matched books. Compliance sees clean audit trails. That's what we built.
See the Settlement Engine Live
Frequently asked questions
Read our insightful blogs!
Stay updated with the latest trends and innovations in finTech with our insightful blogs.



