Escaping the PA Trap: How Tech Platforms Can Legally Route Vendor Payments
The "Current Account" Mistake
You have built a revolutionary marketplace. Customers log in, buy a service from a third-party vendor listed on your app, and pay at checkout. The funds flow seamlessly into your startup's standard current account. Every Friday, your finance team deducts a 10% platform commission and wires the remaining 90% to the respective vendors.
It sounds like standard business operations. However, in the eyes of the Reserve Bank of India (RBI), this seemingly innocent operational flow makes your startup an illegal, unlicensed Payment Aggregator (PA). Ignorance of this rule is currently one of the leading causes for sudden bank account freezes and regulatory shutdown notices for early-stage tech platforms.
The RBI Crackdown: Prohibition on Fund Pooling
The Reserve Bank of India, through its stringent Guidelines on Regulation of Payment Aggregators and Payment Gateways, has clearly defined who can and cannot handle third-party funds. The core regulatory concern is protecting customer money from being misused, delayed, or lost by an intermediary platform before it reaches the intended merchant.
If your platform touches the funds intended for a vendor, even for a millisecond within your own corporate current account, you are in direct violation of RBI guidelines and the Payment and Settlement Systems Act, 2007 (PSS Act).
The Regulatory Safe Harbor: Escrow and Nodal Accounts
How do platforms like Swiggy, Urban Company, or local service marketplaces operate legally without becoming full-fledged PAs themselves? They rely on Regulatory Safe Harbors established in partnership with licensed entities.
Instead of receiving funds into a standard corporate account, compliant platforms utilize Nodal or Escrow Accounts. These are specialized bank accounts managed by a licensed Payment Aggregator (like Razorpay, Cashfree, or Stripe) or a sponsor bank.
The Commercial Takeaway: Split Payment APIs
The solution to this legal hurdle is a technological one. By integrating Split Payment APIs (often marketed as "Marketplace Settlements" or "Route" products by major payment gateways), founders can achieve absolute legal compliance while simultaneously automating their revenue collection.
- Automated Commissions: When the ₹1,000 transaction hits the Escrow Account, the API automatically splits the funds at the source. It sends ₹900 to the vendor and routes your ₹100 platform fee into your actual corporate current account.
- Reduced Tax Friction: Since the ₹900 never hits your books, you do not have to artificially inflate your revenue and later account for it as an expense or "cost of goods sold." Your accounting cleanly reflects only your ₹100 commission.
- Vendor Trust: Vendors are assured that their payments are held by an RBI-regulated entity, significantly lowering the trust barrier for onboarding new merchants to your platform.
Conclusion: Structural Engineering Before Coding
In 2026, building a fintech-enabled platform or a multi-vendor marketplace requires more than just flawless code; it requires architectural legal engineering. Hardcoding a payment flow that routes through your standard corporate account is a recipe for regulatory disaster.
Founders must consult with specialized legal counsel to structure their payment flows, draft appropriate Merchant Agreements, and select the right licensed Payment Aggregator before writing the first line of code. Escaping the PA trap is entirely possible, provided you respect the boundaries of fund pooling.
