Rules checked twice
What the assistant may read or prepare is checked when it is offered and again when it runs. It can never exceed what the customer's own role allows.
How it works
From a sentence to a transfer, inside your rules.
The assistant never moves money on its own. It works through the same forms, permissions and second factor as your app.
- The customer asks"Pay this invoice", typed, spoken or as an attached PDF.
- The assistant preparesIt finds the payee, the amount and the reference, and opens your transfer form already filled, next to the conversation.
- Your rules applyPermissions, limits and the second factor you configured: a new payee asks for a code.
- The customer confirmsThe app saves it under the customer's session. Every step is in the audit log.
Repeat a usual payment
Repeat any payment in a few words.
The assistant knows the customer’s payment history. “Same as last month”, “the usual to my landlord”, “pay Elena again”: it finds the matching payment and opens your transfer form already filled with the payee, amount and reference, dated today.
- Your own transfer form, with its checks
- Saved only when the customer confirms
- The saved line comes from the server, not the model
Pay from a document
Upload a document, let the assistant read it.
Customers attach a file to the conversation, such as an invoice or a bill. The assistant reads the payee, the IBAN, the amount and the reference, and turns them into the right action: a new payee, then the payment.
- A new payee asks for the second factor you configured
- Nothing is saved before the customer confirms
- The file stays in the customer’s conversation
Speak instead of typing
Talk to the assistant.
Customers can send voice messages instead of typing, in English, French or Spanish. Every request works by voice: questions, payments, card control or documents. Handy on the move, and more accessible for customers who prefer not to type.
- Same forms, rules and confirmation as a typed request
- Answers in the language the customer speaks
Act on any product
Act on any product you allow.
Cards, accounts, payments, standing orders, loans: the assistant can act on any product the bank grants it. Freeze a lost card and activate it again, set up a standing order, prepare a payment. The customer says what they need, the assistant opens the right operation.
- Only the actions you grant, per customer profile
- Your app’s own operations, nothing new to integrate
- Every action in the bank’s audit
Documents on demand
Statements and documents on request.
The customer asks for an account statement in their own words, choosing the account, the period and the language. The bank’s PDF arrives in the conversation, ready to download or send.
- The bank’s own statement, not a generated summary
- Any period, in English, French or Spanish
Why banks trust it
Control by design, not by prompt.
Every guarantee below is enforced by the platform, not by instructions to the model.
Nothing is saved without the customer
The model never saves. The customer reviews the prefilled form and confirms; the server, not the model, reports what was saved.
Sensitive data stays out of the model
Masked, encrypted and system fields never reach the AI. Tables are shown to the customer under their session, not sent to the model.
One platform, one model
Same customers, profiles, forms and core-banking connectors as your online banking. A new product becomes conversational with a grant, not a project.
In your back office
Configured by the bank, audited by the bank.
What the assistant may do, how it answers and who can review it are back-office settings, applied on the next message without a release.
Grants per customer profile
Which accounts, payments and cards the assistant may read or prepare. Without a grant, it is off.
Fields and screens
Which fields it shows and may fill, and how each screen looks, per entity.
Out-of-scope topics
Where to send the customer for complaints, mortgages or insurance, in every language.
Conversation audit
Every prompt, reply, action and result, read-only, for staff holding the audit role.
Second factor
Which operations ask for a code: e-mail or authenticator app, as for the rest of the app.
Wording per language
Confirmation messages and fallback channels translated by the bank.
Deployment
Your choice of model.
The language model is configuration, not code. Choose a provider and a region that fit your policies, or run your own model in your infrastructure so no conversation leaves it. The platform keeps the rules, the data access and the audit on your side.
OpenAIGoogle GeminiVertex AI (EU region)AnthropicYour own model, hosted by you
Deployed like any module
Scope workshop, configuration, acceptance testing and go-live on your usual roll-out. Retail banking today; corporate is next on the roadmap.
See IBS in action.
Request a demo: a guided tour with our team, or a personal demo account you explore on your own.