What MCP now understands about bank transaction codes
Open a bank statement message — a camt.052, camt.053, or camt.054 — and every entry on it carries a BankTransactionCodeStructure: a compact classification of what kind of transaction it actually is. A SEPA credit transfer, an ACH debit, a card settlement, a standing order — each gets a specific code, not a free-text description. That classification scheme, the Bank Transaction Code (BTC) hierarchy, is maintained separately from the core ISO 20022 specification, and it’s now something our MCP server can resolve directly.
What MCP now understands about data source schemes
ISO 20022 doesn’t force every code in a message into a fixed, standard list. In a handful of specific places, it deliberately leaves the door open for a market infrastructure, a central securities depository, or an industry body to define its own proprietary codes instead. That mechanism is called a Data Source Scheme (DSS), and it’s tracked in its own registry by the ISO 20022 Registration Authority — separate from the main specification, and until now, separate from what our MCP server could tell you.