📔UK Open Banking

UK Open Banking Specification

Account Access Permission Policy

In UK Open Banking API technical documents, data elements are logically grouped together into “permissions”. Permissions provide to group data elements of Account Information Services (AIS). If Account Information Service Providers (TPPs) request access to specific permission, they will have access to all the data elements included by the permission. This grouping function provides a better user experience allowing TPPs to be selective, and better understandable a consent process for PSUs. ApiGo enables API providers specialize endpoints on Management Portal with account access permissions.

To allow TPPs to be selective but at the same time creating a consent process that is at an acceptable level of granularity for the PSU, ApiGo provides two main clusters to make clear the permissions which include Account Access Permission Policy and Account Transaction Permission Policy. The detail permission contains all data elements which provide by TPPs.

To get access Account Information Services (AIS), the TPP presents to the PSU a description of the data that it requires to support its service proposition. When TPP sent a request to get consent to reach AIS, ApiGo informs the ApiGo to authenticate the customer and to select the account(s) they want to give access to. Once the PSU has been authenticated, ApiGo will be able to respond to the TPP’s request by providing the account information that has been requested.

When an environment has been created with UK Open Banking Standard, the permission for the related endpoints will be configured automatically.

The endpoints which will be autogenerated depend on the Open Banking Standard of the environment can be managed on the Endpoints page. Also, Account Access Permission Policy can be configured for any other endpoint from the policy list.

Management Portal -> Endpoints -> The Related Endpoint -> Account Access Permission Policy