Where Armature meets ISO 20022
ISO 20022 is the message standard that banks, payment systems and market infrastructures use to instruct, confirm and report payments and securities settlement. Since 22 November 2025, cross-border payment instructions between financial institutions on Swift travel in ISO 20022 only [1].
KXCO Armature, KXCO's layer-one network, speaks standard Ethereum JSON-RPC [2]. An operating institution joins the two with a gateway. The gateway reads Armature's transactions and events and produces the ISO 20022 messages the institution's systems already process. In the other direction, it reads an incoming ISO 20022 instruction and submits the matching transaction to Armature.
This document maps each Armature event to its ISO 20022 message, and the main fields of each message to their source on the chain or in the institution's records. It answers Principle 22 of the CPMI-IOSCO Principles for Financial Market Infrastructures, which asks a market infrastructure to use, or at a minimum accommodate, internationally accepted communication standards [3].
The messages in this mapping
| Message | Name |
|---|---|
| pain.001 | CustomerCreditTransferInitiation |
| pacs.008 | FIToFICustomerCreditTransfer |
| pacs.009 | FinancialInstitutionCreditTransfer |
| pacs.002 | FIToFIPaymentStatusReport |
| camt.054 | BankToCustomerDebitCreditNotification |
| camt.053 | BankToCustomerStatement |
| sese.023 | SecuritiesSettlementTransactionInstruction |
| sese.025 | SecuritiesSettlementTransactionConfirmation |
Table 1. Message names as the ISO 20022 catalogue gives them [4].
Each Armature event and its message
| Armature event | ISO 20022 message | Direction | Status |
|---|---|---|---|
| Customer transfer | pacs.008, after the customer's pain.001 to its bank. A signed transaction moves the value on Armature. | Instruction into Armature | Mapping available |
| Transfer between institutions | pacs.009 for an institution's own account. | Instruction into Armature | Mapping available |
| Transfer in a final block | pacs.002 with status ACSC, AcceptedSettlementCompleted. | Report from Armature | Mapping available |
| Token transfer event | camt.054, one notification for each confirmed transfer on an account the institution services. | Report from Armature | Mapping available |
| Account history | camt.053, built from the period's camt.054 entries. | Report from Armature | Mapping available |
| Refused or reverted | pacs.002 with status RJCT and a reason code. | Report from Armature | Mapping available |
| Delivery versus payment | sese.023 with a pacs.009 cash leg, settled in one transaction and confirmed by sese.025. | Both | Pattern available. Reference contract proposed |
| Payment versus payment | Two linked pacs.009 legs, one per currency, settled in one transaction. | Both | Pattern available. Reference contract proposed |
| Signing key published | Reference data below the message layer: KXCO's key file and on-chain signature checks. | Reference data | Live |
Table 2. Armature events mapped to ISO 20022 messages. "Mapping available" means the Armature side runs today and this document gives the mapping; the institution's gateway produces the message. The sections that follow give the detail, and Next releases lists what is proposed.
Credit transfers: pacs.008 and pacs.009
A customer credit transfer starts when a customer instructs its bank, usually with a pain.001, and the bank sends a pacs.008 to the beneficiary's bank. A transfer between institutions for their own account uses pacs.009. On Armature, either becomes one signed transaction: a transfer of a tokenised liability under the ERC-20 standard, or a call to the institution's settlement contract [5].
| pacs.008 field | Source | How the gateway fills it |
|---|---|---|
| GrpHdr/MsgId, PmtId/TxId | The transaction hash | A 32-byte hash that is unique on the chain. |
| GrpHdr/CreDtTm | The block timestamp | Blocks arrive every 2.0 seconds on average [6]. |
| PmtId/EndToEndId | The transaction's data, under the institution's convention | A standard KXCO field is proposed under Next releases. |
| IntrBkSttlmAmt | The transfer amount and the token contract | The gateway maps each token contract to its ISO 4217 currency code and applies the token's decimals. |
| DbtrAcct, CdtrAcct | The sender and receiver addresses | Each is a 20-byte address on Armature. |
| Dbtr, Cdtr names | The institution's KYC record for each admitted holder | Names stay in the institution's records, and the chain carries addresses only. |
| Dbtr, Cdtr LEI and BIC | The institution's KYC record | An optional LEI and BIC in the key registry is proposed under Next releases. |
| RmtInf/Ustrd | The transaction's data, under the institution's convention | Covered by the same proposed standard field. |
Table 3. The main pacs.008 fields and their sources. pacs.009 uses the same sources for its institution parties.
Settlement status and reporting
Armature runs QBFT consensus with deterministic finality: a committed block is final, with no forks and no reorgs [7] [8]. A transfer is either in a final block or it has not happened, so the gateway reports settlement as soon as the block is committed.
KXCO's counsel advises that a transfer in a final Armature block is legal settlement finality. Blocks arrive every 2.0 seconds on average [6], and KXCO measured 2.0000 seconds a block over 59,211 blocks on 7 October 2026 [8].
For reporting, the gateway issues one camt.054 for each confirmed transfer on an account the institution services. It builds camt.053 statements from those entries over the statement period. Every entry carries a transaction hash and a block number, and an auditor can check each one against the public explorer at chain.kxco.ai [9].
| Armature state | pacs.002 status |
|---|---|
| Awaiting a block | PDNG, Pending |
| In a final block | ACSC, AcceptedSettlementCompleted |
| Reverted | RJCT, Rejected, with AM04, InsufficientFunds, where the balance was short, or the code that matches the revert reason |
| Refused by the rule | RJCT, with the register's reason in AddtlInf. The transfer rule runs before a unit moves [8]. |
| Dropped from the pool | RJCT, with the reason in AddtlInf |
Table 4. Armature states and pacs.002 status codes.
Delivery versus payment and payment versus payment
In delivery versus payment, the securities leg and the cash leg settle together or not at all.
ISO 20022 instructs the securities leg with sese.023 and the cash leg with pacs.009, and confirms settlement with sese.025. On Armature, one transaction moves the security token and the cash token together. If either leg fails, both revert. That is gross, simultaneous settlement of both legs, Model 1 in the BIS taxonomy [10], and it removes principal risk as CPMI-IOSCO Principle 12 asks [3].
Payment versus payment works the same way for foreign exchange. Two linked pacs.009 legs, one per currency, settle in a single transaction.
Armature runs any contract that compiles to EVM bytecode, under the London rules, and ERC-20, ERC-721 and ERC-1155 tokens all work on it [5]. An institution can deploy its own settlement contract for either pattern today. KXCO's reference contracts for both are proposed under Next releases.
KXCO Sovereign is the software institutions use to hold, exchange and settle value under common rules, covering FX, securities, futures, options, bonds, tokens, stablecoins and cash. Its settlement records are anchored on Armature [11].
Keys, identity and reference data
Signing keys
ISO 20022 has no message for publishing a post-quantum public key, because key publication sits below the payment-message layer. KXCO publishes the post-quantum public keys it signs with in a key file at a stable address [12]. Armature verifies ML-DSA-87 and ML-DSA-65 signatures on chain at precompiled contracts [7]. A gateway pins the keys it relies on and checks each signed message against them.
Superseded keys stay listed, so a record signed before a rotation still checks [8].
Party identification
Party identification follows the institution's records. The institution admits each holder under its own KYC, and the holder's credential carries the result into the register [8].
When the gateway builds a message, it takes names, postal addresses, LEIs and BICs from those records. Personal data therefore stays in the institution's systems, and the chain records addresses, amounts and hashes.
Next releases
| Release | What it adds | Status |
|---|---|---|
| Payment metadata field | A standard field in the transaction's data for EndToEndId, remittance information and the purpose code, so that every gateway reads them the same way. | Proposed |
| LEI and BIC in the registry | An optional LEI and BIC beside each registered key, so that a gateway can fill party identification from the chain. | Proposed |
| Reference settlement contracts | Published contracts for delivery versus payment and payment versus payment. | Proposed |
| Reference gateway | A service that reads Armature events and sends pacs.002, camt.054 and camt.053 to the institution's own transport. | Proposed |
Table 5. Proposed releases. Until each one ships, the institution's gateway applies its own convention to the same fields, as the credit transfer table describes.
The CPMI-IOSCO map that accompanies this document sets out, principle by principle, what KXCO's software provides to an institution that runs a market infrastructure on it [13].
KXCO is a software company. Licensed institutions hold the assets and operate the regulated service. KXCO holds no financial licences, takes no custody of customer assets and is not a broker or placement agent.
Sources
- Swift, the global financial community completes the switch to ISO 20022, November 2025. The coexistence period for cross-border payment instructions ended on 22 November 2025. swift.com/news-events/press-releases/global-financial-community-completes-switch-iso-20022-paving-way-new-levels-cross-border-payment-speed-and-innovation-around-world
- KXCO Armature JSON-RPC reference: standard Ethereum JSON-RPC (EIP-1474) plus QBFT methods, read 18 October 2026. chain.kxco.ai/developers/rpc
- CPMI-IOSCO, Principles for financial market infrastructures, April 2012. bis.org/cpmi/publ/d101a.pdf
- ISO 20022, message definitions catalogue. iso20022.org/iso-20022-message-definitions
- KXCO Armature smart contracts page: EVM-compatible, ERC-20, ERC-721 and ERC-1155, ARMR the native gas and settlement asset, read 18 October 2026. chain.kxco.ai/developers/contracts
- KXCO Armature public statistics, read 18 October 2026: block 5,453,796, average block time 2.0 seconds. chain.kxco.ai/api/stats
- KXCO Armature validator page, read 18 October 2026. chain.kxco.ai/validators
- KXCO, Tokenising real-world assets on a post-quantum chain, developer blog, read 18 October 2026. kxco.ai/developers/blog/tokenising-real-world-assets-post-quantum-chain/
- KXCO Armature product page, status Live, read 18 October 2026. kxco.ai/armature/
- CPSS (now CPMI), Delivery versus payment in securities settlement systems, September 1992: the three DvP models. bis.org/cpmi/publ/d06.htm
- KXCO Sovereign product page, status Live, read 18 October 2026. kxco.ai/sovereign/
- KXCO post-quantum public key file, updated 11 October 2026. kxco.ai/.well-known/pq-keys.json
- KXCO, KXCO and the CPMI-IOSCO Principles for Financial Market Infrastructures, version 1.0, 18 October 2026. kxco.ai/developers/blog/kxco-and-the-cpmi-iosco-principles/