GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

PROGRESS
ANNOTATED SAMPLE

camt.055 customer cancellation request

A fictional corporate request asking its bank to cancel the original pain.001 payment.

Contributor Shubham Mathure

Illustrative, non-production example. Values are fictional and the message is not validated for any specific network, scheme, or implementation guide.

EVIDENCE AT ARM'S REACH

DOWNLOAD AND GOVERNING SOURCES

Download the canonical fictional sample, then open the exact official definition and profile needed for implementation testing.

An XSD checks XML structure. A usage guideline adds profile rules, conditional fields, code restrictions, and business controls. XSD-valid does not mean scheme-compliant.

XSD + definitionBase ISO 20022current

ISO 20022 message definitions and XSDs

Choose the exact message definition in the official catalogue. The base XSD checks XML structure; it does not prove compliance with a scheme profile.

Owner
ISO 20022 Registration Authority
Checked
2026-07-12
Access
Official page · Public official catalogue; select the required message version before downloading.
OPEN OFFICIAL SOURCE
Usage guidelineCBPR+current

CBPR+ usage guidelines

The network profile that restricts how ISO 20022 payment and reporting messages are used for cross-border traffic.

Owner
Swift (CBPR+ working group)
Version
Standards Release 2025
Checked
2026-07-19
Access
Login required · Full message-level guidelines require the relevant Swift MyStandards access.
VERSION TRACK
  • upcomingStandards Release 2026
    Published
    2026-03-20
    Effective
    2026-11-14
    Supersedes
    Standards Release 2025
    Access
    Login required
    Checked
    2026-07-19

    Adds the November 2026 validation and structured-address changes; implement against the final SR2026 usage guidelines.

    Final usage guidelines are published through MyStandards; the public release page gives the implementation timeline.

    Open version source
OPEN OFFICIAL SOURCE
Teaching sampleScheme-neutral teachingcurrent

camt.055 customer cancellation request — raw XML

A fictional corporate request asking its bank to cancel the original pain.001 payment. SYNTHETIC / TRAINING ONLY; illustrative unvalidated.

Owner
Payments Signal
Version
camt.055.001.13
Checked
2026-07-19
Integrity
crc32:9bdb7244
Access
Payments Signal download · Original fictional teaching sample; no login required.
DOWNLOAD
Lifecycle packScheme-neutral teachingcurrent

MX cancellation, return, reversal, and investigation lifecycle — ZIP pack

Customer and FI cancellation, resolution, return, reversal, and structured investigation messages.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:f4772381
Access
Payments Signal download · Original fictional teaching pack; no login required.
DOWNLOAD
Field matrixBase ISO 20022current

camt.055 field matrix

Curated field requirements, contexts, operational meaning, and implementation cautions.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:e4b86f86
Access
Payments Signal download · Original, source-backed teaching asset; no login required.
DOWNLOAD
Profile packCBPR+current

CBPR+ implementation pack

Generated mapping, field-matrix, test, checklist, acceptance-criteria, migration, manifest, checksum, and source-inventory bundle.

Owner
Payments Signal
Checked
2026-07-19
Integrity
crc32:9d2559ed
Access
Payments Signal download · Original generated teaching pack; no login required.
DOWNLOAD
camt.055
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.055.001.13">
  <CstmrPmtCxlReq>
    <Assgnmt>



      <CreDtTm>2026-07-18T09:08:00Z</CreDtTm>
    </Assgnmt>
    <Case><Id>DEMO-CUSTOMER-CXL-001</Id><Cretr><Pty><Nm>Demo Trading Ltd</Nm></Pty></Cretr></Case>
    <Undrlyg>
      <OrgnlGrpInfAndCxl><OrgnlMsgId>DEMO-PAIN001-001</OrgnlMsgId><OrgnlMsgNmId>pain.001.001.09</OrgnlMsgNmId></OrgnlGrpInfAndCxl>
      <OrgnlPmtInfAndCxl>
        <OrgnlPmtInfId>DEMO-PMT-001</OrgnlPmtInfId>
        <TxInf><OrgnlEndToEndId>DEMO-E2E-001</OrgnlEndToEndId></TxInf>

      </OrgnlPmtInfAndCxl>
    </Undrlyg>
  </CstmrPmtCxlReq>
</Document>

EVERY ANNOTATED FIELD

Assgnmt/Id Assignment identification — mandatory

Reference for this cancellation assignment between the parties.

Assgnmt/Assgnr Assigner — mandatory

Party sending the cancellation request.

Assgnmt/Assgne Assignee — mandatory

Party expected to handle the request.

Case/Id Case identification — optional

Case reference used to track the cancellation dialogue.

Undrlyg/OrgnlGrpInfAndCxl/OrgnlMsgId Original message identification — conditional

Identifies the original pain.001 or other customer initiation being cancelled.

Undrlyg/OrgnlPmtInfAndCxl/OrgnlPmtInfId Original payment information identification — conditional

Narrows the request to the original payment block.

Undrlyg/OrgnlPmtInfAndCxl/TxInf/OrgnlEndToEndId Original end-to-end identification — conditional

Identifies the individual business payment.

Undrlyg/OrgnlPmtInfAndCxl/CxlRsnInf/Rsn/Cd Cancellation reason — mandatory

Coded reason for asking to cancel, such as duplicate or suspected fraud.

FULL camt.055 REFERENCE →

COMMUNITY SIGNAL

Discuss this learning page

Share an operational observation or ask a concrete payments question. Your name and message are public; your email remains private.

NEXT QUESTION REVIEWMonday, 27 Jul, 8:00 amMonday answer runs use source-supported educational material. Some questions may need owner review.
WHAT ARE YOU SHARING?

Publish only lawful, relevant content. Never include confidential payment or personal data.

Public discussion

LOADING

Loading the discussion…