How a Sydney-based Neo-Bank Secured its Indian Footprint despite Strict RBI Regulations
India's FinTech ecosystem is one of the most dynamic in the world, driven by the Unified Payments Interface (UPI) and a massive unbanked population. For "PayNexus Global" (anonymized), a successful Australian neo-bank specializing in SME lending, the Indian market represented a $50 billion opportunity. However, entering the Indian financial sector is not for the faint of heart. The Reserve Bank of India (RBI) maintains a high bar for Foreign Direct Investment (FDI) in financial services.
This case study explores how CorpArray guided PayNexus through a complex 18-month journey, from initial market entry strategy to securing a partnership-led operational model and managing the subsequent FDI compliance (Form FC-GPR) and SBO (Significant Beneficial Ownership) reporting.
PayNexus initially planned to apply for a full Non-Banking Financial Company (NBFC) license. However, they soon realized the regulatory reality was far more complex than anticipated.
The RBI had become extremely selective in granting new NBFC licenses to foreign-owned entities, particularly those involving digital lending. The requirement for a minimum Net Owned Fund (NOF) of ₹20 Crore was the easy part; the hard part was proving 'fit and proper' status for the Australian parent company and its ultimate beneficial owners.
The RBI's directive on "Storage of Payment System Data" requires all payment data to be stored exclusively in India. For a cloud-native Sydney firm using AWS regions in Australia and Singapore, this meant a complete re-architecture of their data stack.
While PayNexus was Australian, some of its early-stage venture capital investors had links to jurisdictions that share a land border with India. This triggered 'Press Note 3' scrutiny, requiring government approval rather than the 'automatic route' for FDI.
CorpArray's strategy focused on speed-to-market while building a long-term regulatory asset. We advised PayNexus against a direct NBFC application in year one.
We structured the Indian entity as a Technology Service Provider (TSP) and LSP. This allowed PayNexus to partner with an existing Indian bank and a local NBFC. PayNexus provided the 'underwriting algorithm' and the 'customer interface' while the local partner held the balance sheet. This removed the immediate need for an NBFC license and reduced the capital requirement.
To avoid Press Note 3 delays, we helped PayNexus restructure their 'Capital Table' for the Indian subsidiary, ensuring that only the Australian parent company (a clean, regulated entity) was the shareholder. We managed the FC-GPR filing through the FIRMS portal, ensuring that the valuation (based on DCF) was accepted by the AD Bank without queries.
We worked with PayNexus’s CTO to implement a 'Data Residency' framework. All Indian customer PII (Personally Identifiable Information) was migrated to AWS Mumbai, with a strict 'no-outward-flow' policy for transactional data, satisfying the RBI's audit requirements.
By Day 180, PayNexus India was live as an LSP. However, to truly own the customer, they still wanted their own license. CorpArray identified an 'Acquisition Opportunity'—a small, dormant NBFC with a clean track record. We managed the 'Change in Management' application with the RBI, which is often faster than a fresh license application. We handled the due diligence, the public notice requirements, and the final 'Prior Approval' from the RBI’s Department of Non-Banking Regulation (DNBR).
In India, compliance is not a checkbox; it's a conversation. CorpArray's ability to represent our Australian values to the RBI while respecting Indian regulatory concerns was the key to our success. — CEO, PayNexus Global.