Trust
Built to the rules, on your systems.
AiBanker prepares the work; your staff decide. Here is who does what, the rules built into every call and file, where your data lives and what comes with every pilot. AiBanker is software for regulated lenders. It is not a bank or a lender, and it does not claim any regulator's approval.
What AiBanker prepares, what your staff decide
| Step | AiBanker prepares | Your staff decide |
|---|---|---|
| First contact | AiBanker prepares · Explains the product in the customer's language and says it is the bank's AI assistant | Your staff decide · Product approval and scripts |
| Consent | AiBanker prepares · Asks for consent for each purpose, set to No until the customer says yes, and logs the time and channel | Your staff decide · Consent policy. The records belong to you |
| Documents | AiBanker prepares · Asks for, fetches, reads and pre-checks documents through your own credentials | Your staff decide · Final verification and fraud-unit sampling |
| KYC | AiBanker prepares · Guides the customer, fetches and pre-fills, and books the video KYC slot | Your staff decide · The KYC decision. Your trained official runs video KYC |
| Credit | AiBanker prepares · Assembles the file and drafts the credit memo in your template, every number traced to its source, with a recommendation and reasons | Your staff decide · Login acceptance, field checks and sanction |
| Early warning | AiBanker prepares · Flags stress with plain reason codes and makes a help call | Your staff decide · Any change to limits, offers or terms. Fraud tagging stays with your fraud unit |
| Payments | AiBanker prepares · Prepares a payment to a saved payee and reads it back in words | Your staff decide · The customer approves with your bank's own UPI PIN, OTP or biometric |
Built into every call and file
- The customer hears at the start that they are talking to the bank's AI assistant, and can ask for a person at any time.
- Consent is asked for each purpose, defaults to No and is logged with the time and channel. The records belong to the lender.
- Service calls go out on the lender's 1600-series number, between 8am and 7pm, and are recorded.
- Payments are approved only by the bank's own UPI PIN, OTP or biometric. The AI never sees, stores or enters them.
- There is no approve button. AiBanker recommends with reasons; your officer decides, and the record shows what they saw and why.
- Every figure in a credit memo is traced to the document it came from.
Your data
- AiBanker runs on your servers or your own cloud, in India.
- Each bank has its own model. It learns only from that bank's data, on that bank's servers. Nothing is pooled across banks.
- AiBanker keeps only the data each task needs.
- Logs stay in India for 180 days, and security incidents are reported within 6 hours, as CERT-In requires.
- You can switch AiBanker off at any time and leave with your data and your credit memory.
With every pilot: the compliance pack
Banks must list, validate and be able to switch off every vendor model. The pack does the hardest part of that work for you.
- An entry for your model inventory, a model card and a validation pack
- A kill switch you control
- Audit rights for your bank and for RBI
- A deployment kit for your servers or your cloud, with data kept in India
- A security test report from a CERT-In-empanelled auditor, and our ISO 27001 roadmap
- A due-diligence pack for lending service providers, with a website-listing template
- An AI disclosure script in line with RBI's FREE-AI framework
- A consent and dark-pattern check for the rules that start on 1 January 2027
- An exit and data-portability plan
The company
- AiBanker is built by Altiora Capital Solution, Kerala, India.
- DPIIT-recognised startup · Kerala Startup Mission
- Incubated at IIT Madras and by Innovation Incubator
- Backed by Group Meeran and JAIN University
- Patent application 202641000710 (published, not granted)
Questions for the team: support@altioracapitalsolution.com