Trust
What we do about security, and what we do not claim.
You should be able to see how a platform handles access, keeps data separate, records history and describes its own limits.
Controls
How access and data are handled
Access is denied by default
Data is not readable unless a policy allows it, and that check runs in the database rather than only in the application.
Access depends on role
What a user can see and do follows their role and approval authority. Staff accounts are invited, and role records are held separately from user profiles.
Codes are verified on the server
Simulation access codes are checked on the server. They are stored only as hashes and never validated in the browser.
Important actions are recorded
Approvals, overrides and changes to terms are recorded with the user and the time.
Corrections, not edits
Financial history is corrected through reversals and adjustments, each with its own author and date.
Your data is exportable
Institutions keep ownership of their data and can take it out. Bankli can also run alongside an existing system of record.
Security certifications will be published here only once they have been earned.
The simulation
What the simulation contains
The simulation exists so you can judge Bankli on what it does rather than on a slide deck.
- All data belongs to Meridian Finance & Credit Ltd, a fictional institution.
- There is no real customer, account or transaction data in it.
- Anything you do during a session applies to your session only.
- Access is granted on request, is time-bound, and can be withdrawn.
- Bankli is a technology provider, not a bank, and holds no banking licence.
Simulation
See how Bankli works inside a financial institution.
Use a fictional finance company to explore credit, collateral, collections, funding, reconciliation and approvals. All information in the simulation is synthetic.
Synthetic data. Fictional institution. Not a live banking environment.