Exchange contracts

Every kind of exchange on the network has a contract: the question that may be asked and the shape of the answer that comes back. Structured contracts are profiles of an ISO 20022 base message, so they interoperate with existing financial-messaging infrastructure. Free-text is the ARM member with no request schema (a note and attachments), and its prose is in this catalogue with the others.

ContractPurposeISO 20022 baseStatus
Business-Relationship Check: Response
business-relationship-check
Confirm whether a subject has a relationship with a business and, if so, of what type and under which identifiers, so a targeted follow-up can be made.ISO 20022 auth.002 (InformationRequestResponse)draft
camt.053-CA: Crypto-Asset Statement
camt053-ca
Answer a transaction-history request for a crypto or fiat account/wallet, as a statement that stays aligned with ISO 20022.ISO 20022 camt.053 (BankToCustomerStatement)draft
FIR: Fraud Incident Response (base message)
fir
Report a fraud incident between participants so it can be acted on.ISO 20022 payment-recall / investigation lineage (camt.056 FIToFIPaymentCancellationRequest, camt.029 ResolutionOfInvestigation); a new multi-message family, not a strict profiledraft
Free-Text Authority Request
free-text
A note and attachments when no structured profile fits. A member of the ARM family. There is no request schema.—draft
KYC / CDD Response
kyc
Return a customer due-diligence record for a named subject.ISO 20022 auth.002 (InformationRequestResponse) found/not-found envelope + IVMS101 identity coredraft
Field-level specifications and machine-readable schemas are available to identified developers and partners. Tell us who you are and we'll give you access to the full contracts, JSON Schemas, and a sandbox. Request developer access →
Building with an AI agent? Fetch the contracts as context via qp mcp (key-authenticated, no web sign-in): see For AI agents.