An account context. A clear principal. A defined mandate.
Bring financial context into agent-led workflows without separating money from the business responsible for it.
Financial services need an accountable owner.
An AI-led Payment Account is our product direction for an account environment that intelligent software can work with on behalf of an eligible business. The business remains the principal; an agent receives permission to perform specific tasks.
That distinction matters. Software does not become the beneficial owner of funds, and a prompt does not replace onboarding, authorisation or the obligations of the financial institution providing an account.
Connect the workflow, not just the final instruction.
A useful account environment links the business profile, supporting documents, service permissions and operational records. This gives an agent the context it needs to prepare a task and gives a reviewer the context needed to approve it.
As financial capabilities are enabled, the same approach can support account information, payment preparation and reconciliation. Each action needs its own permission and supported service; access to one capability is not unrestricted access to the rest.
Designed around the way your platform works.
An assistant inside business software has different responsibilities from an agent coordinating supplier operations. We work through those differences before an integration is enabled: who gives instructions, what the software can see, and where a human decision is required.
Tell us which account services your workflow needs. We will discuss the available integration scope and the provider requirements, rather than assume every account feature is available in every market.
The account belongs to the business.
Imagine a company using several software assistants for different tasks. One helps organise suppliers; another supports financial reporting. They may require access to different information and should not inherit the same authority simply because they serve the same business. The account context connects their work to a common principal while preserving the boundaries around each role.
For an enabled service, the application can connect a proposed action to the relevant mandate and approval. A reviewer sees the business purpose, and the resulting provider record can be associated with that instruction. The product direction is an account environment that supports intelligent software responsibly, not a separate legal owner called an AI agent. Specific account capabilities and provider requirements are confirmed during onboarding.
Good questions.
Clear answers.
Does an AI agent own the account?
No. The eligible business remains the principal and account arrangements remain with the relevant provider. Software acts only within delegated permissions.
Is every account feature available through the API?
No. Information access, preparation and execution are separate capabilities. Each depends on the enabled interface, service and authority.
Can different agents have different access?
That is the intended approach: access should reflect each agent’s purpose and the business’s mandate. The concrete controls are specified for the integration.
A closer look.
Agent-enabled services are being introduced in stages. Access, permissions and financial capabilities are agreed during onboarding and depend on the service provider, jurisdiction and use case.
Where could we take you?
Tell us what you want to build, connect or make possible.