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
- Implementation
How a Open Banking API Platform rollout works
Set up organization scope, rehearse independent review and connect provider evidence.
Define the operating scope
Name the organization, its currency and time zone, the team members who prepare and review, and the eligible counterparties.
Map provider accounts
Record each provider, external account identifier, currency and counterparty owner. Agree how debit and credit lines explain an instruction's amount.
Rehearse review
Prepare an instruction, send its revision to review and have a different person decide with a reason. Test rejection and a changed revision.
Connect provider outcomes
Decide how provider instruction references, events, attachments and bank-data grants enter the operating trail.
Check reconciliation
Compare source movements with confirmed instructions on the same account using amount and occurrence date; review dated balances and receipts.
What the customer provides
Bring the organization and team roster, eligible banking counterparties, provider account identifiers, a sample instruction and a sample provider event. Name the people who will prepare, independently review, monitor provider outcomes and audit exceptions. Choose a first provider relationship and agree how its grant and settlement evidence can be verified.
Changing it afterwards
When a counterparty or account changes, update its active state and preserve earlier instruction evidence. Review changes to an instruction against the revision on which its decision was made. Keep provider corrections, rejected decisions and receipt discrepancies in the record history so the next operator can see why the outcome changed.
Set up Open Banking API Platform your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.