Nationwide Building Society · OAuth Scopes

Nationwide Building Society OAuth Scopes

OAuth 2.0 searched

Nationwide Building Society publishes 4 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Nationwide Building Society API on a user’s behalf.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

Financial ServicesBankingBuilding SocietyOpen BankingPSD2OBIECMA9United KingdomPaymentsAccount Information

Scopes: 4 Flows: authorizationCode, clientCredentials Method: searched

Scopes (4)

Scope	Description	Flows
openid	OpenID Connect authentication; returns an id_token binding the PSU authorisation to the consent intent.	authorizationCode
accounts	Access to the Account and Transaction Information (AIS) APIs — accounts, balances, transactions, beneficiaries, standing orders, direct debits, scheduled payments, statements, parties and products, subject to an authorised account-access-consent.	authorizationCode, clientCredentials
payments	Access to the Payment Initiation (PIS) and Variable Recurring Payments (VRP) APIs — create and authorise domestic/international payment-order consents and VRP consents, then submit payment orders.	authorizationCode, clientCredentials
fundsconfirmations	Access to the Confirmation of Funds (CBPII) API — create a funds-confirmation-consent and check whether funds are available on an account.	authorizationCode, clientCredentials

📄 Provider scope reference: https://openbankinguk.github.io/read-write-api-site3/

Source

OAuth Scopes

generated: '2026-07-23'
method: searched
source: https://developer.nationwide.co.uk/open-banking
standard: OBIE Read/Write API Standard (UK Open Banking)
docs: https://openbankinguk.github.io/read-write-api-site3/
notes: >-
  OAuth 2.0 scopes in UK Open Banking are coarse-grained and fixed at client
  registration. Fine-grained permissions are expressed through OBIE consent
  "intents" (account-access-consent, payment-order consents,
  funds-confirmation-consent) that the PSU authorises, not through additional
  scopes. Only the four canonical OBIE scopes below apply to Nationwide's
  Read/Write surface. The Open Data APIs use no scopes (public).
schemes:
- name: OAuth2
  flows:
  - flow: authorizationCode
  - flow: clientCredentials
scopes:
- scope: openid
  description: OpenID Connect authentication; returns an id_token binding the PSU authorisation to the consent intent.
  flows: [authorizationCode]
- scope: accounts
  description: >-
    Access to the Account and Transaction Information (AIS) APIs — accounts,
    balances, transactions, beneficiaries, standing orders, direct debits,
    scheduled payments, statements, parties and products, subject to an
    authorised account-access-consent.
  flows: [authorizationCode, clientCredentials]
  apis: [Nationwide Account and Transaction Information API (AIS)]
- scope: payments
  description: >-
    Access to the Payment Initiation (PIS) and Variable Recurring Payments (VRP)
    APIs — create and authorise domestic/international payment-order consents and
    VRP consents, then submit payment orders.
  flows: [authorizationCode, clientCredentials]
  apis:
  - Nationwide Payment Initiation API (PIS)
  - Nationwide Variable Recurring Payments API (VRP)
- scope: fundsconfirmations
  description: >-
    Access to the Confirmation of Funds (CBPII) API — create a
    funds-confirmation-consent and check whether funds are available on an account.
  flows: [authorizationCode, clientCredentials]
  apis: [Nationwide Confirmation of Funds API (CBPII)]