Integrations
Connected where it matters.
Order routing, RTA feeds, KYC, market data, payments and identity — at the API layer, not by file upload.
What connects, and what flows through it.
Seven categories
Order routing
Orders leave the platform and reach the exchange.
RTA feeds
Folio masters and transaction files land and reconcile.
KYC and KRA
Identity checked inside onboarding, not beside it.
Market data
NAVs, prices and corporate action announcements.
Payments and mandates
Collection and recurring authorisation.
Identity
Your existing sign-in, not another password.
Open API
REST endpoints and webhooks for your own flows.
The rule
One order-routing entity at a time — and you can change which one.
A distributor is registered with one routing entity at any given moment. Finvica follows that registration rather than replacing it: orders leave under your membership, settle to your book, and appear in your reconciliation. If you move your registration, the platform moves with it — your clients do not re-register and your history does not reset.
Setup
What connecting actually takes.
Confirm your registrations
Your ARN or RIA code, your routing-entity membership, and the RTA codes your book sits under. Nothing starts until these are verified as yours.
Provision credentials
Per-tenant credentials are issued for each connection. They belong to your firm and are held encrypted — we never share a pooled credential between clients.
Run a file through
A real folio master and a real transaction file, processed into a sandbox tenant you can inspect before anything touches your live book.
Reconcile and go live
Holdings from the feed are reconciled against what you expect, differences are explained, and the connection is switched to live.
Questions about connecting.
Do I need my own BSE, NSE or MFU membership?
Yes. You transact under your own registration, not ours — that is the whole point of us not holding an ARN. Finvica connects to the routing entity you are registered with; it does not stand between you and it.
Can I switch routing entity later?
Yes. One routing entity is active at a time, and changing it does not require re-registering your clients or re-keying your book. Buyers ask this constantly, and the honest answer is that the switch is an operational task rather than a migration.
How often do RTA feeds run?
Feed files are processed as they arrive, and holdings recalculate from the processed file rather than on a nightly batch you have to wait for. A file that lands mid-morning is reflected in the book that morning.
What if my RTA file format is non-standard?
Feed formats vary more in practice than the specifications suggest, and mapping a variant is routine setup work rather than a change request. Bring a sample file to the demo and we will run it.
Do you charge for integrations?
Not by us. Exchange, RTA and payment charges are pass-through and itemised on your quote — you pay those to whoever levies them, at cost. We do not mark them up and we do not charge a connection fee.