first direct · Authentication Profile

First Direct Authentication

Authentication

first direct secures its APIs with oauth2, openIdConnect, and mutualTLS across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

Financial-ServicesBankingOpen BankingPSD2OBIEUnited KingdomPaymentsAccount InformationOpen DataHSBCFintech
Methods: oauth2, openIdConnect, mutualTLS Schemes: 2 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

TPPOAuth2Security oauth2
· flows: clientCredentials
PSUOAuth2Security oauth2
· flows: authorizationCode

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-23'
method: searched
source: openapi/obie-account-info-openapi.yaml, openapi/obie-confirmation-funds-openapi.yaml,
  openapi/obie-payment-initiation-openapi.yaml
docs: https://develop.hsbc.com/knowledge-article/get-started-open-banking-apis
profile: FAPI (Financial-grade API) — UK Open Banking / OBIE Read/Write security profile
notes: >-
  The OpenAPI securitySchemes declare only the oauth2 flows (placeholder authserver.example
  URLs are the OBIE standard's examples). The real first direct / HSBC UK production model is
  FAPI-secured and adds, beyond OAuth2/OIDC: mutual-TLS client authentication with
  OBIE/eIDAS transport certificates, detached JWS request signing (x-jws-signature), and
  PSD2 strong customer authentication (SCA) for the PSU authorization-code flow. Access
  requires FCA authorisation as an AISP/PISP/CBPII and directory registration. The public
  Open Data API requires no authentication.
mechanisms:
- oauth2 (TPP client_credentials + PSU authorization_code)
- openIdConnect
- mutualTLS (OBIE/eIDAS transport certificates)
- request-signing (detached JWS, x-jws-signature)
- psd2-sca
summary:
  types:
  - oauth2
  - openIdConnect
  - mutualTLS
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: TPPOAuth2Security
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://authserver.example/token
    scopes: 1
  description: TPP client credential authorisation flow with the ASPSP
  sources:
  - openapi/obie-account-info-openapi.yaml
  - openapi/obie-confirmation-funds-openapi.yaml
  - openapi/obie-payment-initiation-openapi.yaml
- name: PSUOAuth2Security
  type: oauth2
  flows:
  - flow: authorizationCode
    authorizationUrl: https://authserver.example/authorization
    tokenUrl: https://authserver.example/token
    scopes: 1
  description: OAuth flow, it is required when the PSU needs to perform SCA with the ASPSP when
    a TPP wants to access an ASPSP resource owned by the PSU
  sources:
  - openapi/obie-account-info-openapi.yaml
  - openapi/obie-confirmation-funds-openapi.yaml
  - openapi/obie-payment-initiation-openapi.yaml

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact 
curl "https://apis.io/api/v1/security/first-direct-authentication"
All security posture 
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.