education
Is the Split Pay UPI Trend Legal? What the NPCI Guidelines Actually Say
Merchants are splitting large bills into sub-₹2,000 payments to avoid the 0.4% MDR. We break down the legal and compliance reality of this viral strategy.
With the “Split Pay” method going viral across Indian business communities, a critical question has emerged in merchant WhatsApp groups and startup forums: Is this legal, or is it tax evasion?
Avoiding the new 0.4% Merchant Discount Rate (MDR) by breaking large bills into multiple transactions under ₹2,000 is a brilliant optimization of working capital. More importantly, it is entirely compliant with existing banking and NPCI frameworks.
The Anatomy of the 0.4% Rule
To understand the legality, you must look at how the banking switch reads data.
The NPCI circular mandates a 0.4% fee on P2M (Person-to-Merchant) transactions when the individual transaction payload exceeds ₹2,000. The banking infrastructure evaluates the specific data packet transmitted from the payer to the payee.
If the value in that singular data packet is ₹1,999, the switch routes it through the 0% MDR tier. The system does not retroactively aggregate consecutive payments made from the same VPA to apply a fee. It evaluates each ping independently.
Invoice Structuring vs. Transaction Routing
Splitting a payment is not a new concept. In B2B commerce, clients regularly pay 50% advances and 50% on delivery. In retail, customers frequently split a restaurant bill across multiple cards or pay partially in cash and partially via UPI.
Settling a single master invoice via multiple partial payments is a standard commercial right. By using the Split Pay method, you are simply condensing this installment behavior into a rapid, consecutive timeframe at checkout to optimize your routing costs.
What Actually Violates Compliance
While Split Pay is compliant, merchants often resort to other workarounds that explicitly violate RBI and NPCI terms of service. You must avoid these traps:
- Surcharging the Customer: Adding a “2% Gateway Fee” or “0.4% UPI Charge” directly to the customer’s retail bill is strictly prohibited under consumer protection frameworks.
- Using P2P Savings Accounts: Processing heavy commercial volume through a personal savings account to hide from P2M fees violates KYC norms and will result in a frozen bank account.
- Shell Merchant Accounts: Creating dozens of fake micro-merchant accounts to stay under the ₹1 Lakh P2PM exemption limit constitutes financial fraud.
How to Keep Your Ledgers Clean
The only genuine compliance risk with Split Pay is internal accounting. In the event of a tax audit, you must be able to prove that the money entering your bank matches the invoices generated.
If you generate a GST invoice for ₹5,000, your accounting software must cleanly link the three separate UPI UTRs (₹1,999, ₹1,999, ₹1,002) to that specific invoice. Using an automated API platform like VyaparGateway ensures this mapping happens programmatically. The system associates the multiple incoming webhooks to a single order_id, keeping your ledgers perfectly balanced and audit-ready while you enjoy a 0% effective MDR.
Direct answers
Frequently asked questions
- Will my bank freeze my account for receiving too many ₹1,999 payments?
- No. If you are using a registered P2M (merchant) current account, high transaction velocity is expected. Only personal savings accounts (P2P) risk being flagged for heavy commercial use.
- Does splitting the payment affect my GST filing?
- No. GST is calculated based on the total invoice value, regardless of whether that invoice was settled via one transaction, three split UPI payments, or a mix of cash and digital.
- Is there a limit to how many times a customer can scan?
- Merchants have no limit, but consumers are restricted by their bank's daily UPI transaction limit (typically 10-20 transactions per 24 hours).
Build your payment flow
Explore the API and browser-only merchant tools.
Create UPI checkout orders, verify signed events, or test the free calculators and generators without exposing credentials.