CommonSchema
Request access
Request access

One schema across banking, energy and lending.

CommonSchema is an open data model for accounts, transactions, holdings and energy usage, and the access arrangements behind it. Every provider arrives in one shape, with consent per app and per agent, revocable and audited.

Request accessAsk for an institution
cdr-banking · transactionsource
{
  "accountId": "a1f3c9e2",
  "transactionId": "tx-55120931",
  "isDetailAvailable": false,
  "type": "PAYMENT",
  "status": "POSTED",
  "description": "HARBOUR COFFEE ROASTERS SYDNEY",
  "postingDateTime": "2026-10-12T09:14:00+11:00",
  "amount": "-42.50",
  "currency": "AUD",
  "merchantName": "Harbour Coffee Roasters",
  "merchantCategoryCode": "5814"
}
commonschema · transactionnormalised
{
  "object": "transaction",
  "id": "txn_7Hq2LmR8",
  "provider": {
    "industry": "banking",
    "region": "au"
  },
  "source": {
    "format": "cdr-banking",
    "id": "tx-55120931"
  },
  "amount": {
    "value": "-42.50",
    "currency": "AUD"
  },
  "direction": "debit",
  "status": "posted",
  "bookedAt": "2026-10-12T09:14:00+11:00",
  "description": "Harbour Coffee Roasters",
  "merchant": {
    "name": "Harbour Coffee Roasters",
    "category": "5814"
  },
  "consent": {
    "grant": "cg_31Kd9w",
    "scope": ["transactions:read"],
    "audience": "app:ledgerly"
  }
}
Illustrative payloads. Field names follow each source’s published format; every value is invented.

From many formats to one record you can account for.

  1. Connect

    One integration and one consent flow per region, in place of a separate build for every bank, retailer and broker. The customer chooses the provider and approves exactly what is shared.

  2. Normalise

    Each provider’s payload is mapped onto the open schema: one transaction, one holding, one usage interval, whatever the source called it. The original field names stay attached for provenance.

  3. Consent & audit

    Consent is part of the schema, not an afterthought. Every record carries the grant it was read under, its scope and its audience, so one app or one agent can be revoked without touching the rest.

Built for data that crosses industries.

  • Banking

    In development

    Banks and other deposit takers

    • Accounts
    • Balances
    • Transactions
    • Statements
    • Payees

  • Credit unions & mutuals

    In development

    Member-owned banks, credit unions and building societies

    • Accounts
    • Balances
    • Transactions
    • Statements

  • Brokerages

    Roadmap

    Share brokers, investment platforms and wrap accounts

    • Holdings
    • Trades
    • Cash balances
    • Corporate actions

  • Crypto exchanges

    Roadmap

    Digital asset exchanges and custodial wallets

    • Balances
    • Trades
    • Deposits and withdrawals

  • Energy retailers

    In development

    Electricity and gas retailers

    • Usage intervals
    • Bills
    • Plans and tariffs
    • Service points

  • Payment processors

    Roadmap

    Card acquirers, payment gateways and payout platforms

    • Payments
    • Payouts
    • Fees
    • Disputes

  • Lenders

    In development

    Non-bank lenders, buy now pay later and finance providers

    • Loan accounts
    • Repayments
    • Balances
    • Rates

  • Need another provider?

    Name the institution and the data you need. Every request is read by a person and shapes the order we build in.

    Ask for an institution

For teams that need the whole picture.

  • Lenders and brokers

    Income, expenses, liabilities and repayment history in one shape for serviceability and ongoing monitoring.

  • Mutuals and credit unions

    Give members a clear view of what they hold elsewhere without maintaining a connector per institution.

  • Energy companies

    Usage intervals, bills and tariffs from any retailer, modelled the same way, for switching, solar and efficiency products.

  • Fintech builders

    Budgeting, accounting and wealth products on one model instead of one per country and per provider.

  • AI agent builders

    Give each agent its own narrow consent scope, see what it read, and revoke it on its own.

Regions arrive one at a time, and we say which.

See coverage
  • Australia
    In development

    Banking, Credit unions & mutuals, Energy retailers, Lenders

  • New Zealand
    Roadmap
  • United Kingdom
    Roadmap
  • European Union
    Roadmap
  • United States
    Roadmap
  • Canada
    Roadmap

Australia’s Consumer Data Right is the first region in development. Every other region is on the roadmap.

The schema is open. The access is arranged here.

The data model lives at commonschema.org: the specification, field definitions, mappings from each provider’s format and the fixtures that test them. Anyone can read it, use it and propose changes.

commonschema.com is the company that makes the schema usable in production: regional arrangements, access to providers, consent flows, operations and support.

How the open schema works
commonschema.org
Specification, field definitions, provider mappings and conformance fixtures.
commonschema.com
Regional arrangements, provider access, consent flows, operations and support.