AMP Bank · OAuth Scopes

AMP Bank OAuth Scopes

OAuth 2.0 derived

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

Scopes: 5 Flows: Method: derived

Scopes (5)

Scope	Description	Flows
bank:accounts.basic:read	Read basic account information (account list, masked account numbers, product category, balances) for accounts the consumer has authorised.
bank:accounts.detail:read	Read detailed account information (full account number, features, terms, rates, addresses) for authorised accounts.
bank:transactions:read	Read transaction data for authorised accounts.
bank:regular_payments:read	Read direct debits, scheduled payments and instalment plans for authorised accounts.
bank:payees:read	Read the consumer's saved payee list for authorised accounts.

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

Source

OAuth Scopes

generated: '2026-07-21'
method: derived
source: openapi/amp-bank-cds-banking-products-openapi.yml (x-scopes per operation) + DSB Consumer Data Standards
docs: https://consumerdatastandardsaustralia.github.io/standards/#authorisation-scopes
summary: >-
  OAuth 2.0 authorisation scopes governing the accredited CDR consumer
  data-sharing surface (accounts, balances, transactions, direct debits,
  scheduled payments, payees). These are the standard DSB Consumer Data
  Standards banking scopes, declared per-operation in the OpenAPI via the
  x-scopes extension. They apply to the FAPI 1.0 Advanced / OpenID Connect
  authorisation flow brokered by an Accredited Data Recipient (ADR) - NOT to
  the public, unauthenticated Product Reference Data (PRD) surface, which needs
  no scope. See authentication/amp-bank-authentication.yml for the auth profile.
flow:
  grant: authorization_code (FAPI 1.0 Advanced, OIDC, PAR, PKCE, mTLS-bound tokens)
  registry: CDR Register / Data Standards Body InfoSec profile
scopes:
- scope: bank:accounts.basic:read
  description: >-
    Read basic account information (account list, masked account numbers,
    product category, balances) for accounts the consumer has authorised.
  operations:
  - listBankingAccounts
  - listBankingBalancesBulk
  - listBankingBalancesSpecificAccounts
  - getBankingBalance
- scope: bank:accounts.detail:read
  description: >-
    Read detailed account information (full account number, features, terms,
    rates, addresses) for authorised accounts.
  operations:
  - getBankingAccountDetail
- scope: bank:transactions:read
  description: Read transaction data for authorised accounts.
  operations:
  - listBankingTransactions
  - getBankingTransactionDetail
- scope: bank:regular_payments:read
  description: >-
    Read direct debits, scheduled payments and instalment plans for authorised
    accounts.
  operations:
  - listDirectDebits
  - listDirectDebitsBulk
  - listDirectDebitsSpecificAccounts
  - listScheduledPayments
  - listScheduledPaymentsBulk
  - listScheduledPaymentsSpecificAccounts
  - listInstalmentPlans
  - listInstalmentPlansBulk
- scope: bank:payees:read
  description: Read the consumer's saved payee list for authorised accounts.
  operations:
  - listBankingPayees
  - getBankingPayeeDetail
note: >-
  Scope descriptions follow the DSB Consumer Data Standards authorisation-scopes
  reference. AMP Bank implements the standard CDR banking scope set; it does not
  define bank-proprietary scopes. The PRD product endpoints (listBankingProducts,
  getBankingProductDetail) require no scope.