4.12 Core banking and payout integration
Sponsor bank
Section titled “Sponsor bank”The lender’s sponsor bank is the bank that:
- Holds the lender’s collection account, disbursement account, escrow accounts.
- Submits the lender’s NACH presentation files to NPCI.
- Provides virtual accounts for borrower-level repayment routing.
- Provides payout APIs for disbursement (IMPS / NEFT / RTGS / UPI).
- Provides statement / MIS files daily.
Choosing the sponsor bank is one of the most consequential operational decisions for a new NBFC.
Bank options
Section titled “Bank options”The Indian banks with strongest API banking / fintech infrastructure for NBFC partnerships:
| Bank | API maturity | Typical fintech relationship |
|---|---|---|
| HDFC Bank | Mature API stack; large fintech partnerships | Premium, deep |
| ICICI Bank | Mature; iLens / API banking | Premium, deep |
| Axis Bank | Mature; active fintech division | Premium, deep |
| Yes Bank | API-first historically; fintech-friendly | Active |
| IDFC FIRST | Strong fintech focus; modern stack | Active |
| Kotak Mahindra | Decent API; selective fintech partnerships | Selective |
| RBL Bank | Active in fintech | Active |
| DCB / Equitas / AU Small Finance / Fincare / Bandhan / Federal | Varying maturity; some strong on specific rails | Mixed |
| Public-sector banks | Generally less API-mature; partnerships exist but slower | Slower |
What to negotiate with sponsor bank
Section titled “What to negotiate with sponsor bank”- NACH presentation — daily file submission + ack.
- Virtual account — sub-account per borrower for repayment.
- API banking — payout rails, statement pull.
- Pricing — per-transaction; volume-tiered.
- SLAs — file submission cutoff, payout-confirmation latency, statement availability.
- Integration support — bank’s IT team availability.
Payout aggregators
Section titled “Payout aggregators”Independent of sponsor bank, payout aggregators add a layer of redundancy and modern APIs:
| Vendor | URL |
|---|---|
| RazorpayX Payouts | razorpay.com/x |
| Cashfree Payouts | cashfree.com |
| Setu Bridge | setu.co |
| M2P Payouts | m2pfintech.com |
| Decentro | decentro.tech |
| Karza Disburse | karza.in |
These wrap multiple banks’ APIs behind a single API; useful for failover and broader coverage.
Virtual accounts
Section titled “Virtual accounts”- Per-borrower virtual account under master collection account.
- Borrower transfers to their virtual account.
- Auto-allocated to their loan.
- Eliminates manual reconciliation guesswork.
Reconciliation
Section titled “Reconciliation”- Daily MIS from sponsor bank: NACH ack file, statement, virtual-account credits.
- Internal recon engine: matches expected to actual.
- Exception queue for mismatches.
- GL reflection: matched entries flow to ledger.
API patterns
Section titled “API patterns”- REST / JSON for modern banks and aggregators.
- SFTP + file-based for legacy public-sector banks (NACH files, statement files).
- Webhooks for asynchronous notifications (NACH ack, virtual-account credit, payout status).
Pricing proxy
Section titled “Pricing proxy”- NACH presentation: per debit attempt
₹2 – ₹15. - Payout (IMPS / NEFT / RTGS):
₹2 – ₹10per transaction. - Virtual account allocation: usually small fee per active VA.
- API banking: bank-specific, often a setup fee + usage.
Compliance
Section titled “Compliance”- RBI Payment System Data Storage — payment data within India.
- NPCI rules for NACH / UPI rails.
- Outsourcing MD — bank relationship governed under your outsourcing framework as well.
- Digital Lending Guidelines — direct flow lender → borrower.
Build vs buy
Section titled “Build vs buy”- Sponsor bank relationship: Buy (negotiate hard).
- Payout aggregator: Buy (RazorpayX / Cashfree).
- NACH presentation file: Build (format stable; data is yours).
- Reconciliation engine: Build (your data, your rules).
- Virtual-account allocation logic: Build (your loan-mapping rules).