Permission dashboard
The customer sees every agent with access to their accounts, the purpose and the expiry, and revokes any of them in one step.
Consumer finance
Customers already point agents at their accounts; banks need to see who is acting and within what limits.
Customers are starting to let software agents read balances, pay bills and move money between their own accounts. For a bank, an agent that logs in with the customer's credentials is indistinguishable from the customer, and a broad data-sharing consent says nothing about payments. AgenticOpenFinance™ gives each agent an identity, a mandate the customer grants in the bank's own app, and a permission dashboard the customer controls.
What agents do
The customer sees every agent with access to their accounts, the purpose and the expiry, and revokes any of them in one step.
A household bills agent pays utilities within a per-payment and a monthly cap; a new payee is sent to the customer for approval.
When an action needs the customer, the approval reaches the bank app with the amount, the payee and the agent named, and is confirmed with strong customer authentication.
Requests from agents are signed and checked against published keys, so the bank can tell a registered agent from screen scraping.
Every agent payment is sealed with the mandate snapshot, the verdict and the approval, ready for a complaint or an unauthorised-payment claim.
Value chain
AgenticOpenFinance™ connects them with one identity check, one mandate model, one policy and one evidence trail.
Typical flow
Live demo
One event, the right channel: approvals, expiring mandates and consent, blocked payments (demo). Demo data
DemoAll companies, people, agents and amounts are fictional. Protocol names refer to public specifications; naming one is not a partnership or an endorsement.
Glossary