- Developer zone
- Directory sandbox
- API availability
- Conformance service
- Documentation
- Directory
- How to guide: enrolling onto the Directory
- Sign up
- Login
- News
- News and press releases
- Insights
- Articles, reports and thought leadership
- Case studies
- Guides
- Resources
- Document library
- Open banking glossary
- API specifications
- Customer Experience Guidelines
- Get started
- Authentication methods
- Account information services
- Payment initiation services
- Card based payment instrument issuers
- Dashboards
- Operational guidelines
- Dedicated interfaces
- Problem resolution
- Change and communication management
- Operational guidelines checklist
- Security profiles
- Why open banking is safe
- Open banking FAQs
- Open banking glossary
- Open finance
- How open banking can help consumers
- How open banking can help businesses
- Open banking case studies
- Regulated open banking providers
- Open banking app store
- OBL leadership team
- OBL external engagement
- Delivering the roadmap
- Careers at OBL
- Account providers (ASPSPs)
- Fintechs (TPPs)
- Technical service providers (TSPs)
- Regulatory
- Find a regulated provider
- Open banking apps
- Open banking case studies
- MiData - API performance
- Open Banking Directory
- Crown Dependencies Directory
- Confirmation of Payee (CoP)
- Variable Recurring Payments (VRPs)
- Why open banking is safe
- Customer Experience Guidelines
- Latest guidelines v4.0
- Customer journey
- Customer communication
- Directory sandbox
- API availability
- Conformance service
- Documentation
- How to guide: enrolling onto the Directory
- Sign up
- Login
- News and press releases
- Articles, reports and thought leadership
- Case studies
- Guides
- Document library
- Open banking glossary
- API specifications
- Get started
- Authentication methods
- Account information services
- Payment initiation services
- Card based payment instrument issuers
- Dashboards
- Dedicated interfaces
- Problem resolution
- Change and communication management
- Operational guidelines checklist
- Security profiles
Close
How can we help?
Built on security and transparency, open banking puts you in control every step of the way.
Join over 6 million users
More than 6 million people already use open banking services in the UK. Opt in to a world of secure apps and services for more clarity and control over your finances – all built around secure transactions.
Visit our app store
Savings or investments. Budgeting or donating. Loans or payments. Open banking powers new ways to access a wide range of financial services – all built on secure systems from regulated providers.
Find an app
Bank level security
Apps and services are regulated
Opt-in only
Personalised services
Built on existing secure systems
It’s linked to your bank
Access open banking services in the same way as your online banking and other online services and apps. New ways to manage your money, with reliable security and counter-fraud controls.
APIs are well-established
APIs are commonly used to share information between services. Logging in to a website via Facebook? That’s done via APIs. Uber pinpointing location on a map? That’s Google Maps’ API at work.
Less data. More security.
Forget handing over reams of sensitive financial information to apply for accounts. With open banking, you share minimal data necessary for the service through a secure digital process.
FAQs
Some commonly asked open banking related security questions
How do I knowopenbanking is safe?
Open banking has been designed with security at its heart – here’s how:
Bank-level security – open banking uses rigorously tested software and security systems. You’ll never be asked to give access to your bank login details, PINs or passwords to anyone other than your own bank or building society.
It’s regulated – only apps and websites regulated by the FCA or a European National Competent Authority can enrol in the Open Banking Directory.
You’re in charge – you choose when, with whom, and for how long you give access to your data.
Extra protection – your bank or building society should pay your money back if a payment is made which is unauthorised. You’re also protected by data protection laws and the Financial Ombudsman Service.
How can I stay safe online?
Open banking uses secure technology. Here are a few more steps you can take to stay extra safe online:
Check if it’s regulated – see if the app or website is listed on our regulated providers page, check the FCA register, or a European National Competent Authority.
Read the small print – always read the terms and conditions before you agree to give a regulated app or website access to your data.
Check your bank account – if you see something that doesn’t look right, contact your bank or building society straight away.
Find out more – the FCA website has tips on protecting yourself online, as do the Take 5 Campaign and Action Fraud website.
How do I control who has access to my information?
You choose which regulated apps and websites you want to use – so you’re always in charge. You decide what information they can access, and for how long. No one gets access unless you say so.
Find more answers
Cookies on the OBL website
We use cookies to improve your experience and to measure the performance of our website content. You can either consent to accept all the cookies or choose which ones you want.
Read More
Accept
Reject AllChange settings
Privacy Overview
Our website uses cookies to improve your experience while you navigate through the website. Cookies categorised as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. In addition, we also use third-party cookies that help us analyse and understand how you use this website. These cookies are only stored in your browser with your consent. You also have the option to opt out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-advertisem*nt | 1 year | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisem*nt". |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
| Cookie | Duration | Description |
|---|---|---|
| _gat | 1 minute | This cookies is installed by Google Universal Analytics to throttle the request rate to limit the colllection of data on high traffic sites. |
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors. |
| _gid | 1 day | This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form. |
| _hjAbsoluteSessionInProgress | 30 minutes | No description available. |
| _hjFirstSeen | 30 minutes | This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. |
| _hjid | 1 year | This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID. |
| _hjIncludedInPageviewSample | 2 minutes | No description available. |
| _hjTLDTest | session | No description available. |
| pardot | past | The cookie is set when the visitor is logged in as a Pardot user. |
| vuid | 2 years | This domain of this cookie is owned by Vimeo. This cookie is used by vimeo to collect tracking information. It sets a unique ID to embed videos to the website. |
Advertisem*nt cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
| Cookie | Duration | Description |
|---|---|---|
| lpv840283 | 30 minutes | No description |
| visitor_id840283 | 10 years | No description |
| visitor_id840283-hash | 10 years | No description |
Powered by 
