For builders
Build wealth management into what you already have.
The operations the interface performs, available as REST endpoints with webhooks — so wealth runs inside your product rather than beside it.
The problem
What this looks like today.
- 01
Your customers are already in your app, and you have to send them somewhere else to invest.
- 02
Building the operational stack yourself is a two-year programme.
- 03
The vendors who could provide it have no API worth building on.
What matters here
Business rules, not adjectives.
The API covers the core book.
Clients, orders, holdings, transactions and revenue — not a read-only subset.
Webhooks push events rather than making you poll.
Your system learns that a position changed instead of asking every few minutes.
Credentials are per tenant and scoped.
Never a pooled key shared between clients.
A sandbox exists to build against.
Before anything you write touches a live book.
Documentation is public and never behind a form.
Developers evaluate by reading. Making them ask for access first loses the evaluation before it starts.
The modules this buyer lives in.
Set up
Get the firm, its people and its clients onto the system.
Transact
Move money and keep the book true.
Grow
Get paid, and see where the practice is going.
Coverage
What is supported, class by class.
| Product | Order capture | Routing | Corporate actions | Valuation basis | Reporting | Commission |
|---|---|---|---|---|---|---|
| Mutual Funds | Yes, with conditionsOnline and offline | Yes, with conditionsBSE StarMF | Yes | Yes, with conditionsUnitised — units × NAV | Yes | Yes |
| AIF | Yes, with conditionsOffline order entry, with drawdowns | Not supported | Not supported | Yes, with conditionsNon-unitised — statement value | Yes | Yes |
| PMS | Yes, with conditionsOffline order entry | Not supported | Not supported | Yes, with conditionsNon-unitised — statement value | Yes | Yes |
| Bonds | Yes, with conditionsOffline order entry | Not supported | Yes, with conditionsVia bond settlement engine | Yes, with conditionsUnitised — units × price | Yes | Yes, with conditionsRate matrix and manual entry |
| Direct Equity | Yes, with conditionsOffline order entry | Not supported | Yes | Yes, with conditionsUnitised — units × price | Yes | Yes, with conditionsNot modelled — brokerage, not commission |
| Fixed Deposits | Yes, with conditionsTransaction / holding upload | Not supported | Not supported | Yes, with conditionsNon-unitised — statement value | Yes | Yes, with conditionsRate matrix and manual entry |
| Recurring Deposits | Yes, with conditionsTransaction / holding upload | Not supported | Not supported | Yes, with conditionsNon-unitised — statement value | Yes | Yes, with conditionsRate matrix and manual entry |
| NPS | Yes, with conditionsTransaction / holding upload | Not supported | Not supported | Yes, with conditionsSet per instrument | Yes | Yes, with conditionsRate matrix and manual entry |
| Insurance | Yes, with conditionsTransaction / holding upload | Not supported | Not supported | Yes, with conditionsSet per instrument | Yes | Yes, with conditionsRate matrix and manual entry |
| Real Estate | Yes, with conditionsTransaction / holding upload | Not supported | Not supported | Yes, with conditionsSet per instrument | Yes | Yes, with conditionsRate matrix and manual entry |
Mutual Funds, AIF, PMS, Bonds and Direct Equity carry a full product specification. The other five are basic information only by design — held, valued and reported, with no product-specific fields planned. Valuation basis is set per instrument rather than per product, and defaults to unitised. Non-unitised positions report at value with zero units.
Enterprise engagements start with a conversation.
Engagements here are scoped rather than configured. Tell us what you are building and who it serves, and we will tell you what it takes — including whether we are the wrong answer.
- Mutual Funds
- AIF
- PMS
- Bonds
- Fixed Deposits
- Direct Equity
- NPS
- Insurance
- BSE StarMF
- CAMS
- KFintech
- AMFI
- CVL KRA
Every product class, one book
What api and embedded ask.
Where are the docs?
developers.finvica.com is gated on a public-API versioning decision rather than a date (00 §11). It will be public and ungated when it ships.
Can we white-label the front end instead?
Yes — if you would rather not build the interface, the white-labelled portal runs under your brand on your subdomain. The two approaches can also be combined.
What does an API engagement cost?
Quoted against scope rather than published. The model does not change: you pay for the platform, never a share of what flows through it.
Is there a rate limit?
Rate limits and SLAs publish with the developer portal and the SLA page.