These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Open Banking API Platform
- Who it's for
- Account-data operations
Account-data operations
Teams using provider account data need to know which access request was approved, when the provider granted authority and what source movements arrived afterward. The access consent connects back to the banking instruction and organization; financial accounts, snapshots and reconciliation items carry the provider-side detail.
How Open Banking API Platform is set up for you
Consent owner
The preparer records the provider and parent instruction, then sends the current access request revision for independent review.
Access reviewer
The approver records a reasoned decision and checks the grant details before access is treated as completed.
Reconciliation reviewer
The team compares a provider movement with a confirmed instruction on the same account using exact amount and occurrence date.
Teams using provider account data need to know which access request was approved, when the provider granted authority and what source movements arrived afterward. The access consent connects back to the banking instruction and organization; financial accounts, snapshots and reconciliation items carry the provider-side detail.
Start with a provider application and a small set of active financial accounts whose external identifiers are known. Agree which banking instructions require data access and what evidence accompanies a consent request. Rehearse approval and provider activation as separate events, including the provider's grant time and account count.
For reconciliation, collect a dated balance snapshot and a few provider movements. Include one movement whose amount matches a confirmed instruction but whose date differs. Keep it unmatched or mark it as an exception while the reviewer investigates. That case teaches the team to read provider event identifiers and account references instead of relying on a coincidental amount.
Finally, have the Auditor trace a completed consent and a reconciled movement back to the instruction, decision and provider evidence that support them.
Features to start with
Roles on the team
- Auditor
- Read authorized evidence and reports in a scoped, read-only audit view. No record writes and no action execution.
- App Administrator
- Maintain organization configuration and membership. Administrative membership does not confer approval, financial or execution authority and cannot grant an independent reviewer entitlement.
- Independent Treasury Approver
- Review eligible instruction revisions independently and reconcile operational evidence. Approve or reject through guarded actions only; no unrestricted editing of protected or executed records; a reviewer cannot approve their own submission.
- Treasury Preparer
- Prepare assigned operational records and execute eligible reviewed actions. Own organization and draft scope only; accepted, posted and provider evidence is read-only; guarded workflows authorize every transition.
Set up Open Banking API Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.