Agent Marketplace CBA side, mock catalogue
Illustrative reference model

This is a CBA side illustration standing in for the catalogue the bank already runs, such as ServiceNow or Backstage. It is deliberately thin. What is being demonstrated is the handoff, not the catalogue.

Catalogue ag-bureau-settlement

Meridian Settlement Agent

Settles supplier invoices for business banking customers through Meridian Payments Bureau, under the bank's accreditation.

Catalogue: registered Identity: recognised by federation production version 5.4.0

Held here, by the catalogue

Registration

Catalogue id
ag-bureau-settlement
Business unit
Business Banking, Payments Partnerships
Legal entity
Commonwealth Bank of Australia
Division
agentic
Accountable owner
Payments Partnerships, Business Banking
Version
5.4.0
Environment
production
Repository
https://github.com/meridian-bureau/settlement-agent
Software bill of materials
sbom/meridian-settlement-5.4.0.cdx.json
Risk assessment
RA-2304
Change reference
CHG-4421
Registered by
Payments Partnerships, Business Banking

None of this is in the Trust Controller, and none of it needs to be. This is what a catalogue is for.

Held elsewhere, by the Trust Controller

Identity

Entity id
https://settlement-agent.meridian-bureau.example.io
Authorisation server
CommBiz Identity Platform
Capability role
cba.agentic.settlement.bureau
May request
payment_initiationsupplier_invoice
May move money
yes, inside a delegated envelope
Federation roles
cba.oidc.participantcba.agentic.membercba.agentic.settlement.bureaucba.accredited.payments.bureaucba.payments.initiatorcba.supplier.reader
Manufacturer
Settlement Bureau Agent Provider
Signing key
held by Meridian Payments Bureau, never by CBA
Lifecycle state
recognised by federation

An accredited external payments bureau that settles individual supplier invoices for a business customer. The single payment limit and the cumulative envelope bind it exactly as they bind an agent the bank built itself.

Published by the group against the capability role. The catalogue does not write it and cannot change it.

Shown here as a last known outcome. This app did not decide any of it, cannot change any of it, and would be misrepresenting the model if it implied otherwise.

What this agent calls

Integration

The protected resources this agent is built to reach. Being built to call a resource is not the same as being entitled to, which is what the capability role decides and the delegated envelope then narrows.

Supplier and Invoice API

svc-supplier

Payments API

svc-payments