CAMS Finserv

What is CAMS Finserv?

CAMS Finserv acts as a trust bridge in India's digital credit ecosystem. Under RBI's Account Aggregator framework, it allows financial platforms to request structured data directly from the user's accounts after explicit digital consent. It replaces traditional PDF bank statement scraping, which is prone to fraud and high rejection rates. By retrieving cryptographically signed JSON data straight from banks, CAMS Finserv dramatically reduces underwriting risk and operational cycles.

To scale operations efficiently, growth teams use this tool to optimize workflows, decrease technical debt, and build automated reporting systems. By integrating this platform directly into your product analytics pipeline, you can capture detailed user footprints, monitor server metrics, and ensure high deliverability/uptime rates.

Key Features

Pricing & Plans

Pricing is indicative and may vary based on team size, contract length, and regional taxation.

CAMS Finserv charges purely on successful API data pulls. Pricing scales down with volume: low-volume startups pay ₹8 to ₹10 per statement retrieve, while high-volume digital lenders pay closer to ₹2 per transaction. Standard GST of 18% applies under SAC 998314. Consent setup is free; API failures due to bank timeouts are generally not billed.

Who Should Use CAMS Finserv

• Recommended for: Fintech lending apps looking to automate credit assessment and bank statement verification.
• Recommended for: Wealth management and Robo-advisory platforms wanting to track user net worth across assets.
• Limitations: Requires user consent via mobile OTP; users with mismatched bank phone numbers will fail onboarding.
• Limitations: Data formats can vary slightly between FIPs, requiring robust parsing libraries on the receiver end.

Detailed Technical Capabilities & Operational Architecture

CAMS Finserv operates as an RBI-regulated Account Aggregator (AA) gateway implementing the ReBIT financial data sharing specification. The platform manages consent artifact creation, OTP-based user authentication, and decoupled data fetch requests between Financial Information Users (FIUs) and Financial Information Providers (FIPs). Financial telemetry data—including bank statements, mutual fund folios, and GST returns—is encrypted end-to-end using asymmetric key pairs generated at the FIP layer, ensuring secure transit without payload decryption at the AA intermediary level.

Product Growth Playbook & Integration Use Case

### Integration Playbook: Account Aggregator Consent Flow Ensure the CAMS AA widget is triggered after displaying a trust screen outlining the data retrieved. On callback success, parse the encrypted JSON package and store it in your database: ```javascript // AA Success Webhook Receiver Handler app.post('/api/aa/consent-callback', async (req, res) => { const { consentId, status, dataKey } = req.body; if (status === 'CONSENT_GRANTED') { const encryptedData = await fetchAAData(consentId); const decryptedJSON = decryptAAData(encryptedData, dataKey); await processCreditUnderwriting(decryptedJSON); res.status(200).send({ success: true }); } else { res.status(400).send({ error: 'Consent denied or timed out' }); } }); ``` To prevent user drop-off, load the AA redirect page in an inline iframe or secure overlay rather than redirecting the main page.

First 5 Things to Set Up

1. 1

   Apply for FIU registration and register on the CAMS Finserv developer portal.

2. 2

   Generate API credentials and set up secure webhook listeners.

3. 3

   Integrate the AA redirect consent widget into your onboarding flow.

4. 4

   Test data retrieval against the sandbox bank simulation accounts.

5. 5

   Deploy to production and complete compliance certification with ReBIT guidelines.