What is the latest version of pain.010?

The latest version in the ISO 20022 e-Repository release of 24 April 2025 is pain.010.001.08.

What is the root element of pain.010?

The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:pain.010.001.08, and its message element is MndtAmdmntReq (MandateAmendmentRequest).

Is there an MT equivalent of pain.010?

No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

pain: Payments Initiation

pain.010 Mandate Amendment Request

Written and maintained by ZagTrader. Last reviewed 21 October 2026. How this page is sourced and checked

pain.010 is the ISO 20022 MandateAmendmentRequest message in the Payments Initiation business area (pain). The latest version is pain.010.001.08, and 8 versions are in the repository.

Message: MandateAmendmentRequest
Latest version: pain.010.001.08
Submitting organisation: Swift
MT equivalent: None listed

In use: published in the current ISO 20022 catalogue.

What pain.010 is for

The MandateAmendmentRequest message is sent by the initiator of the request to his agent and/or counterparty. The initiator can both be the debtor or the creditor (or where appropriate the debtor agent).
The MandateAmendmentRequest message is forwarded by the agent of the initiator to the agent of the counterparty.
A MandateAmendmentRequest message is used to request the amendment of specific information in an existing mandate. The MandateAmendmentRequest message must reflect the new data of the element(s) to be amended and at a minimum a unique reference to the existing mandate. If accepted, this MandateAmendmentRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered as a valid amendment on an existing mandate, agreed upon by all parties. The amended mandate will from then on be considered the valid mandate.
The MandateAmendmentRequest message can contain one or more request(s) to amend a specific mandate.
The messages can be exchanged between creditor and creditor agent or debtor and debtor agent and between creditor agent and debtor agent.
The message can also be used by an initiating party that has authority to send the message on behalf of the creditor or debtor.
The MandateAmendmentRequest message can be used in domestic and cross-border scenarios.
If all elements in the existing Mandate need to be amended or the underlying contract is different, then the MandateAmendmentRequest message should not be used. The existing Mandate has to be cancelled and a new Mandate has to be initiated.

Definition from the ISO 20022 e-Repository, release of 24 April 2025.

pain.010 versions

Every version published in the e-Repository, newest first. A message keeps its business purpose across versions; each new version is a separate schema with its own namespace.

Version	Registration status	Published in
pain.010.001.08latest	Registered	Latest version set
pain.010.001.07	Registered	Previous version set
pain.010.001.06	Registered	Archive
pain.010.001.05	Registered	Archive
pain.010.001.04	Registered	Archive
pain.010.001.03	Registered	Archive
pain.010.001.02	Registered	Archive
pain.010.001.01	Registered	Archive

pain.010 message structure

The building blocks of pain.010.001.08 to three levels, with multiplicity ([0..1] optional, [1..1] mandatory, * any number) and the data type or component. Element names and definitions are from the ISO 20022 repository; usage guidelines such as CBPR+ or a market infrastructure's rules can restrict them further.

Document [1..1]
- MndtAmdmntReq MandateAmendmentRequest [1..1]
  - GrpHdr Group Header [1..1]GroupHeader110
    Set of characteristics to identify the message and parties playing a role in the amendment of the mandate, but which are not part of the mandate.
    - MsgId Message Identification [1..1]Max35Text
      Point to point reference, as assigned by the instructing party, and sent to the instructed party, to unambiguously identify the message.
    - CreDtTm Creation Date Time [1..1]ISODateTime
      Date and time at which the message was created.
    - Authstn Authorisation [0..2]Authorisation1Choice (choice)
      User identification or any user key to be used to check the authority of the initiating party.
      - Cd Code [1..1]Authorisation1Code
      - Prtry Proprietary [1..1]Max128Text
    - InitgPty Initiating Party [0..1]PartyIdentification272
      Party that initiates the mandate message.
      - Nm Name [0..1]Max140Text
      - PstlAdr Postal Address [0..1]PostalAddress27
      - Id Identification [0..1]Party52Choice (choice)
      - CtryOfRes Country Of Residence [0..1]CountryCode
      - CtctDtls Contact Details [0..1]Contact13
    - InstgAgt Instructing Agent [0..1]BranchAndFinancialInstitutionIdentification8
      Agent that instructs the next party in the chain to carry out an instruction.
      - FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
      - BrnchId Branch Identification [0..1]BranchData5
    - InstdAgt Instructed Agent [0..1]BranchAndFinancialInstitutionIdentification8
      Agent that is instructed by the previous party in the chain to carry out an instruction.
      - FinInstnId Financial Institution Identification [1..1]FinancialInstitutionIdentification23
      - BrnchId Branch Identification [0..1]BranchData5
  - UndrlygAmdmntDtls Underlying Amendment Details [1..*]MandateAmendment8
    Set of elements used to provide details on the amendment request.
    - OrgnlMsgInf Original Message Information [0..1]OriginalMessageInformation1
      Provides information on the original message.
      - MsgId Message Identification [1..1]Max35Text
      - MsgNmId Message Name Identification [1..1]Max35Text
      - CreDtTm Creation Date Time [0..1]ISODateTime
    - AmdmntRsn Amendment Reason [1..1]MandateAmendmentReason3
      Provides detailed information on the amendment reason.
      - Orgtr Originator [0..1]PartyIdentification272
      - Rsn Reason [1..1]MandateReason1Choice (choice)
      - AddtlInf Additional Information [0..*]Max105Text
    - Mndt Mandate [1..1]Mandate21
      Provides the amended mandate data.
      - MndtId Mandate Identification [1..1]Max35Text
      - MndtReqId Mandate Request Identification [0..1]Max35Text
      - Authntcn Authentication [0..1]MandateAuthentication1
      - Tp Type [0..1]MandateTypeInformation2
      - Ocrncs Occurrences [0..1]MandateOccurrences5
      - TrckgInd Tracking Indicator [1..1]TrueFalseIndicator
      - FrstColltnAmt First Collection Amount [0..1]ActiveCurrencyAndAmount
      - ColltnAmt Collection Amount [0..1]ActiveCurrencyAndAmount
      - MaxAmt Maximum Amount [0..1]ActiveCurrencyAndAmount
      - Adjstmnt Adjustment [0..1]MandateAdjustment1
      - Rsn Reason [0..1]MandateSetupReason1Choice (choice)
      - CdtrSchmeId Creditor Scheme Identification [0..1]PartyIdentification272
      - Cdtr Creditor [0..1]PartyIdentification272
      - CdtrAcct Creditor Account [0..1]CashAccount40
      - CdtrAgt Creditor Agent [0..1]BranchAndFinancialInstitutionIdentification8
      - UltmtCdtr Ultimate Creditor [0..1]PartyIdentification272
      - Dbtr Debtor [0..1]PartyIdentification272
      - DbtrAcct Debtor Account [0..1]CashAccount40
      - DbtrAgt Debtor Agent [0..1]BranchAndFinancialInstitutionIdentification8
      - UltmtDbtr Ultimate Debtor [0..1]PartyIdentification272
      - MndtRef Mandate Reference [0..1]Max35Text
      - RfrdDoc Referred Document [0..*]ReferredMandateDocument2
    - OrgnlMndt Original Mandate [1..1]OriginalMandate10Choice (choice)
      Provides the original mandate data.
      - OrgnlMndtId Original Mandate Identification [1..1]Max35Text
      - OrgnlMndt Original Mandate [1..1]Mandate20
    - SplmtryData Supplementary Data [0..*]SupplementaryData1
      Additional information that cannot be captured in the structured elements and/or any other specific block.
      - PlcAndNm Place And Name [0..1]Max350Text
      - Envlp Envelope [1..1]SupplementaryDataEnvelope1
  - SplmtryData Supplementary Data [0..*]SupplementaryData1
    Additional information that cannot be captured in the structured elements and/or any other specific block.
    - PlcAndNm Place And Name [0..1]Max350Text
      Unambiguous reference to the location where the supplementary data must be inserted in the message instance.
    - Envlp Envelope [1..1]SupplementaryDataEnvelope1
      Technical element wrapping the supplementary data.

Have a pain.010 message? Paste it into the parser to see every element with its name and definition, and format checks on BICs, IBANs, dates and amounts.

External code sets used in pain.010

These elements take their values from ISO 20022 external code sets, which are published separately and updated every quarter without a new message version.

pain.010 questions

What is the latest version of pain.010?: The latest version in the ISO 20022 e-Repository release of 24 April 2025 is pain.010.001.08.
What is the root element of pain.010?: The XML document is Document with the namespace urn:iso:std:iso:20022:tech:xsd:pain.010.001.08, and its message element is MndtAmdmntReq (MandateAmendmentRequest).
Is there an MT equivalent of pain.010?: No Swift MT message is listed as its direct equivalent on this site. Many ISO 20022 messages have no MT counterpart.

All ISO 20022 messages · ISO 20022 code sets · MT messages

The ISO 20022 message definitions, element names and definitions on this page are reproduced from material published at iso20022.org under the ISO 20022 Intellectual Property Rights policy. This is not the official source: the up-to-date ISO 20022 standards and repository material are published only at iso20022.org. Explanations in our own words are by ZagTrader. ZagTrader is not affiliated with or endorsed by ISO or Swift.