Core banking, lending and India data connectors
API files for Finacle, TCS BaNCS, Fiserv, FIS, Jack Henry, Encompass, MeridianLink, the Account Aggregator, CIBIL, CRIF High Mark, GSTN and a V-CIP partner, the contract each one needs, and which bank agents read them.
Browse documentation
Connect the systems your bank's agents ask about
Bank staff agents work from the knowledge base and from what people hand them. These connector files let them read the bank's core, its loan origination system, the India data rails and the video KYC partner at source. Ask your provider for the connector packs; each file is an OpenAPI file you import. All of them are Beta.
Each file is a template built from public documentation. Your
integration team must confirm endpoints and fields against the vendor's
documentation under your own contract. None of these vendors publishes
an API the files could copy exactly, so each file models the operations
agents need on a placeholder bank.example address. The files contain
no credentials and have never been called.
How to connect one
- Edit the file: replace the server address with your gateway, API layer or provider, and change the paths and fields to match it. Keep the operation names, so the agents' grants still match.
- On Connectors, choose Import manifest and pick the file (see adding a connector). For a system inside your network, use Add an internal system with a relay manifest instead (see connecting an internal system); the core banking pack has an example. For a vendor MCP server, use the MCP server tab.
- Set the sign-in on the connector: mutual TLS, OAuth client credentials or a key, as the vendor or your gateway asks. Calls leave from the workspace's fixed address, so your gateway can allow-list it.
- Leave Data protection on Tokenise and set Response fields to what the agents need (see protecting data in connector calls).
- Confirm each operation. Every read is declared read. Every write is declared internal or external and its summary starts with "Needs approval".
- Apply the governance in the pack's
connector-pack.jsonunder Governance: each write's number of approvers (see approvals and audit for connectors). Every write also waits for an approval on each call. - Grant each agent the operations the pack lists for it.
Core banking
| File | Core | Route | Contract you need |
|---|---|---|---|
finacle.yaml | Finacle | Your Finacle MCP server through the MCP tab, where you run one; otherwise this file on your gateway or a relay | Your Finacle licence with API or MCP server entitlement |
tcs-bancs.yaml | TCS BaNCS | This file on your gateway or a relay | Your BaNCS licence with service interface entitlement |
fiserv.yaml | Fiserv DNA, Premier, Signature, Cleartouch | Your own trimmed Fiserv API file, keeping these names; otherwise this file | Your Fiserv contract with API access |
fis.yaml | FIS IBS, Horizon, Systematics, Modern Banking Platform | As for Fiserv | Your FIS contract with API access |
jack-henry.yaml | Jack Henry SilverLake, CIF 20/20, Core Director | A REST facade on your gateway, or SOAP operations on a relay | Your Jack Henry contract with core service access |
All five share one operation set. Reads: customer lookup and profile, accounts, account status, balance, transactions (92 days a call), liens and holds, credit limits, card status, standing instructions, loan account status and repayment schedule. Writes: mark a lien (2 approvers), block a card and stop a standing instruction (1 approver each).
With an MCP server, every tool starts Locked. Confirm each as read, internal or external by what it does, using the core banking classes, and apply the same approvers to its writes.
Loan origination
| File | System | Contract you need |
|---|---|---|
encompass.yaml | Encompass | Your Encompass licence with developer API access |
meridianlink.yaml | MeridianLink | Your MeridianLink contract with API access |
Reads: loan files, status and milestones, conditions, documents. Writes: a note on a condition, and a document request to the borrower using a template you approved (1 approver each). Nothing clears or waives a condition or decides a loan.
India data rails
| File | Rail | Contract you need |
|---|---|---|
account-aggregator-fiu.yaml | Account Aggregator, with your bank as FIU | Registration as a Financial Information User (FIU), onboarding with each AA you use and listing in the Sahamati central registry, and an FIU module certified for the ReBIT specification |
cibil.yaml | TransUnion CIBIL | Membership as a credit institution under the Credit Information Companies (Regulation) Act, 2005 |
crif-high-mark.yaml | CRIF High Mark | As for CIBIL |
gstn-gsp.yaml | GST returns | An agreement with a GST Suvidha Provider (GSP) |
Consent comes first on every rail:
- Account Aggregator. Raising a consent request reaches the customer and needs an approver. Agents read the consent's status and terms, and use data only inside its purpose, accounts, periods and data life. Your FIU module signs, holds the keys and decrypts: no AA key or encrypted data passes through an agent.
- Bureaus. A pull needs the customer's recorded consent reference and an allowed purpose, records an enquiry on the customer's file, and needs an approver. Agents read reports already pulled.
- GST. Registration and filing status are public. Return figures need the taxpayer's OTP consent, and the request for it needs an approver.
Video KYC (V-CIP)
vcip.yaml is provider-neutral: map your V-CIP vendor's API to it on
your gateway. It needs a contract with a V-CIP vendor, or your own V-CIP
system, that meets the RBI KYC Directions, with recordings kept in your
storage in India.
The KYC Onboarding Orchestrator uses it as the V-CIP step. It requests a session, which waits for the KYC officer's approval before the customer is invited, then tracks it and reads the results and artefact references for the V-CIP audit checklist. The official on the call and the concurrent auditor decide; nothing in the connector approves a session or activates an account.
Which agents read what
| Agents | Connector |
|---|---|
| Servicing Request Preparer, Complaint Investigator and Letter Drafter, Business Client Service Desk | Core banking |
| Collections Desk Orchestrator, Hardship and Restructuring Preparer, Post-disbursement Tracker | Core banking loan accounts |
| Covenant and Early Warning Monitor | Core banking limits, liens and conduct; GST filing status |
| Mule Account Alert Triage, Card Dispute and Chargeback Preparer | Core banking accounts, transactions and cards |
| Cash Flow and Statement Analyser | Core banking; Account Aggregator |
| MSME GST Limit Analyst | Account Aggregator, bureaus, GST |
| Credit Appraisal Note Drafter | Bureaus |
| Loan File Orchestrator, Document Intake and QC, Sanction to Disbursement Tracker | Loan origination |
| Entity KYB Verifier | GST |
| KYC Onboarding Orchestrator, Individual KYC Verifier, KYC Document and Evidence Checker, Periodic KYC Refresh | V-CIP |
Agents get reads. The only write mapped to an agent is the orchestrator's V-CIP session request, and it waits for approval. If you grant another write, every call still waits for approval and its approvers. Until a system is connected, each agent asks a person for the extract and labels it unverified.
Data minimisation
- Agents send references your gateway resolves: case, customer, account, consent and report references. No operation takes an Aadhaar number, a full PAN, a card number, a date of birth or a phone number.
- Aadhaar appears only as your Aadhaar Data Vault reference key or its last four digits.
- On Tokenise, account and card numbers reach agents as tokens and are turned back into the real value only inside the call.
- Recordings, images and full bureau reports stay in your systems. The connectors return summaries, references and hashes.