G&C Mutual Bank · OAuth Scopes

G&C Mutual Bank OAuth Scopes

OAuth 2.0 searched

G&C Mutual Bank publishes 9 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the G&C Mutual 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 Data RightConsumer BankingMutual BankAustralia

Scopes: 9 Flows: Method: searched

Scopes (9)

Scope	Description	Flows
openid	OIDC authentication of the consumer.
profile	Basic OIDC profile claims.
bank:accounts.basic:read	Read basic account information (account list, product category, balances).
bank:accounts.detail:read	Read detailed account information (account terms, features, addresses).
bank:transactions:read	Read account transactions.
bank:payees:read	Read saved payees.
bank:regular_payments:read	Read direct debits and scheduled/recurring payments.
common:customer.basic:read	Read basic customer information (name, occupation / organisation type).
common:customer.detail:read	Read detailed customer information (contact details, addresses).

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

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes
docs: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes
note: >-
  The public Product Reference Data surface requires NO scopes (unauthenticated).
  The scopes below are the DSB Consumer Data Standards CDR banking + common
  authorisation scopes that G&C Mutual Bank grants as a CDR Data Holder for the
  authenticated consumer-data surface. They are standard CDR scopes (not
  bank-proprietary) documented by the DSB; the harvested OpenAPI declares no
  oauth2 securitySchemes so these are captured from the standard, not derived.
schemes:
  - name: CDRConsumerDataAccess
    type: oauth2
    profile: FAPI 1.0 Advanced (OIDC hybrid)
    authorizationUrl: per Data Holder InfoSec (published via OIDC discovery)
    tokenUrl: per Data Holder InfoSec (published via OIDC discovery)
scopes:
  - scope: openid
    description: OIDC authentication of the consumer.
  - scope: profile
    description: Basic OIDC profile claims.
  - scope: bank:accounts.basic:read
    description: Read basic account information (account list, product category, balances).
  - scope: bank:accounts.detail:read
    description: Read detailed account information (account terms, features, addresses).
  - scope: bank:transactions:read
    description: Read account transactions.
  - scope: bank:payees:read
    description: Read saved payees.
  - scope: bank:regular_payments:read
    description: Read direct debits and scheduled/recurring payments.
  - scope: common:customer.basic:read
    description: Read basic customer information (name, occupation / organisation type).
  - scope: common:customer.detail:read
    description: Read detailed customer information (contact details, addresses).

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/gc-mutual-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.