St.George Bank · OAuth Scopes

St.George Bank OAuth Scopes

OAuth 2.0 searched

St.George Bank publishes 9 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the St.George Bank 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.

FinancialBanksOpen BankingCDRConsumer BankingAustraliaProduct Reference DataWestpac Group

Scopes: 9 Flows: Method: searched

Scopes (9)

Scope	Description	Flows
openid	OpenID Connect authentication (id_token).	authorizationCode
profile	OpenID Connect basic profile claims.	authorizationCode
bank:accounts.basic:read	Read account identifiers, product association and basic account attributes (balances excluded).	authorizationCode
bank:accounts.detail:read	Read detailed account information (features, rates, addresses); additive to bank:accounts.basic:read.	authorizationCode
bank:transactions:read	Read transactions for consented accounts.	authorizationCode
bank:payees:read	Read saved payees.	authorizationCode
bank:regular_payments:read	Read direct debits, scheduled payments and instalment plans.	authorizationCode
common:customer.basic:read	Read basic customer data (name / organisation).	authorizationCode
common:customer.detail:read	Read detailed customer data (contact details); additive to common:customer.basic:read.	authorizationCode

📄 Provider scope reference: https://consumerdatastandardsaustralia.github.io/standards/#end-user-authorisation

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: >-
  The harvested OpenAPI declares no oauth2 securitySchemes (shared DSB "CDR
  Banking API" doc), so scopes cannot be derived from the spec. The scope set
  below is the standard Consumer Data Right banking authorisation scope
  registry defined by the DSB Consumer Data Standards, which St.George (a
  Westpac CDR Data Holder) accepts on consented data-sharing requests.
docs: https://consumerdatastandardsaustralia.github.io/standards/#end-user-authorisation
reference: https://cdr-support.zendesk.com/hc/en-us/articles/900004582823-Requirement-for-Basic-and-Detailed-Scopes
schemes:
  - name: CDR-OAuth2
    profile: FAPI 1.0 Advanced
    detail: >-
      Scopes are granted through the CDR consent flow (accredited Data
      Recipients only) and bind a sharing arrangement. openid + profile are
      requested alongside the CDR data scopes.
scopes:
  - scope: openid
    description: OpenID Connect authentication (id_token).
    flows: [authorizationCode]
  - scope: profile
    description: OpenID Connect basic profile claims.
    flows: [authorizationCode]
  - scope: bank:accounts.basic:read
    description: Read account identifiers, product association and basic account attributes (balances excluded).
    flows: [authorizationCode]
    operations: [listBankingAccounts, listBankingBalancesBulk, listBankingBalancesSpecificAccounts, getBankingBalance]
  - scope: bank:accounts.detail:read
    description: Read detailed account information (features, rates, addresses); additive to bank:accounts.basic:read.
    flows: [authorizationCode]
    operations: [getBankingAccountDetail]
  - scope: bank:transactions:read
    description: Read transactions for consented accounts.
    flows: [authorizationCode]
    operations: [listBankingTransactions, getBankingTransactionDetail]
  - scope: bank:payees:read
    description: Read saved payees.
    flows: [authorizationCode]
    operations: [listBankingPayees, getBankingPayeeDetail]
  - scope: bank:regular_payments:read
    description: Read direct debits, scheduled payments and instalment plans.
    flows: [authorizationCode]
    operations: [listDirectDebits, listDirectDebitsBulk, listDirectDebitsSpecificAccounts, listScheduledPayments, listScheduledPaymentsBulk, listScheduledPaymentsSpecificAccounts, listInstalmentPlans, listInstalmentPlansBulk]
  - scope: common:customer.basic:read
    description: Read basic customer data (name / organisation).
    flows: [authorizationCode]
  - scope: common:customer.detail:read
    description: Read detailed customer data (contact details); additive to common:customer.basic:read.
    flows: [authorizationCode]
notes: >-
  Product Reference Data (listBankingProducts / getBankingProductDetail) is
  public and requires no scope. detail:read scopes only take effect when the
  matching basic:read scope is also granted.

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set 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 scope set

curl "https://apis.io/api/v1/scopes/st-george-bank-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.