Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Open banking security covers the certificates, API profiles, and consent controls that let a customer share bank data or initiate a payment through a third party without handing over their credentials.

What Is Open Banking Security?
Open banking lets a customer instruct their bank to share account data with a third party, or to make a payment on that third party’s instruction, through an interface designed for the purpose. The alternative it replaced was screen scraping, where the customer handed over their banking username and password and a provider logged in as them. Open banking security is the set of mechanisms that make the new arrangement safe enough to be worth the change: strong identification of the third party, cryptographic protection of the channel, and a consent record the customer can see and revoke.
In the UK this began as a competition remedy. The Competition and Markets Authority ordered the nine largest current account providers to build a common interface in 2017, and the Open Banking Implementation Entity produced the standard that the market now uses.
The cryptography is the strong part. The failures cluster around people and permissions.
For a bank, the work is mostly about the consent lifecycle and about treating the API estate as a first-class production system: authorisation checks on every object, rate limiting per client and per customer, token binding, anomaly detection on consent creation and payment initiation, and revocation that takes effect immediately across every token issued under that consent. Customers should be able to see and cancel every active connection in the main banking app without contacting support.
For a third party, the work is about protecting tokens and minimising what you hold. Store refresh tokens in a hardware-backed key store, do not cache transaction data beyond what the service needs, scope consent requests honestly, and build revocation into the product rather than leaving it to the bank.
The UK runs a bilateral model. Each provider connects to each bank, using a common standard and a shared directory, under FCA supervision. Governance is moving on from the original entity under the Joint Regulatory Oversight Committee, and the Data (Use and Access) Act 2025 provides a statutory basis for smart data schemes beyond banking.
Turkey took a centralised route. Payment services and electronic money are regulated by the Central Bank of the Republic of Turkey under its 2021 regulation, and open banking services run through a central gateway operated by the Interbank Card Centre rather than through direct bilateral connections. Banks and payment providers connect once to the gateway, and the gateway handles routing, participant identification, and standardisation. That makes onboarding simpler and concentrates both control and risk in a single national component. A UK fintech expanding into Turkey should plan for gateway integration and local authorisation rather than assuming its existing FAPI client will connect to Turkish banks directly.
Where an API estate or a consent journey needs testing against real abuse rather than against the specification, our web application security services cover both the interface and the authorisation logic behind it.
Substantially. Screen scraping required the customer to share their banking credentials with a third party, which gave that party full access, defeated fraud controls, and made the customer liable under most terms of service. Open banking replaces it with scoped, time-limited, revocable permissions and authentication that happens with the bank itself. The residual risk shifts to what the customer consents to.
They are the UK-specific certificates issued through the Open Banking Directory that replaced eIDAS certificates after Brexit for open banking purposes. OBWAC is used for transport-layer client authentication and OBSeal for signing. They identify the provider and the roles it is authorised to perform, and banks validate them on every connection.
Yes, from either side. Consent can be withdrawn in the third party’s application or in the bank’s own channel, and the bank must then invalidate the tokens issued under it. Customers should be able to see every active connection in their banking app. Firms should test that revocation genuinely terminates access immediately rather than at the next token refresh.
No. Turkey’s framework is set by the Central Bank of the Republic of Turkey, and participants connect through a central gateway operated by the Interbank Card Centre rather than building bilateral connections to each bank. The security concepts overlap, but the integration model, the authorisation route, and the participant onboarding process are different and require separate work.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.