acmt.035.001.01
The AccountSwitchPaymentResponse message is sent by the new account servicer to the old account servicer to confirm whether it will make the requested payment in a request payment message. The AccountSwitchPaymentResponse message is only used to respond to a AccountSwitchRequestPayment message.
Message Construction
Every ISO20022 message has at the highest level what we call ‘building blocks’. Because the message is constructed as immutable records, the association is by composition. Below you can see the relationship between the message and its constituent building blocks: For comparison, see the ISO20022 official specification
classDiagram
direction LR
%% AccountSwitchPaymentResponseV01 recursion level 0 with max 0
AccountSwitchPaymentResponseV01 *-- "1..1" MessageIdentification1 : MessageIdentification
AccountSwitchPaymentResponseV01 *-- "1..1" AccountSwitchDetails1 : AccountSwitchDetails
AccountSwitchPaymentResponseV01 *-- "0..1" SupplementaryData1 : SupplementaryData
Now, we will zero-in one-by-one on each of these building blocks.
MessageIdentification building block
Unique identification for the message. Identifies a message by a unique identifier and the date and time when the message was created by the sender. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% MessageIdentification1 recursion level 0 with max 1
class MessageIdentification1{
Identification IsoMax35Text
CreationDateTime IsoISODateTime
}
MessageIdentification1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| Identification | Identification of the message. | IsoMax35Text - Required 1..1 |
| CreationDateTime | Date of creation of the message. | IsoISODateTime - Required 1..1 |
AccountSwitchDetails building block
Contains information about the details of the account switch. Details of the account switch, including its status and any response codes. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% AccountSwitchDetails1 recursion level 0 with max 1
class AccountSwitchDetails1{
UniqueReferenceNumber IsoMax35Text
RoutingUniqueReferenceNumber IsoMax35Text
SwitchReceivedDateTime IsoISODateTime
SwitchDate IsoISODate
SwitchType SwitchType1Code
SwitchStatus SwitchStatus1Code
BalanceTransferWindow BalanceTransferWindow1Code
}
AccountSwitchDetails1 *-- "0..0" ResponseDetails1 : Response
%% ResponseDetails1 recursion level 1 with max 1
class ResponseDetails1{
ResponseCode IsoMax35Text
AdditionalDetails IsoMax350Text
}
AccountSwitchDetails1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| UniqueReferenceNumber | Unique number that provides unique and unambiguous identification of the account switch. | IsoMax35Text - Required 1..1 |
| RoutingUniqueReferenceNumber | Unique number that provides unique and unambiguous identification of the account switch. Usage: Where one or more account switches have taken place since the original account switch this field contains the unique number that relates to the switch that transferred the account to the latest new account servicer. | IsoMax35Text - Required 1..1 |
| SwitchReceivedDateTime | Date and time that the request was received by the central switch service, populated by the central switch service only. | IsoISODateTime - Optional 0..1 |
| SwitchDate | Date on which the account switch is expected to have completed. The value is the same as the targeted switch date if the switch completes in the expected timeline. | IsoISODate - Optional 0..1 |
| SwitchType | Indicates whether the account switch is a full switch or a partial switch. Usage: A full switch indicates the transfer of the full balance of the account and associated payment mandates. A partial switch indicates the transfer of certain payment mandates to a new account. | SwitchType1Code - Required 1..1 |
| SwitchStatus | State of the account switch at the time the message is sent. | SwitchStatus1Code - Optional 0..1 |
| BalanceTransferWindow | Identifies the processing window in which the balance transfer will be processed on the day of the account switch. | BalanceTransferWindow1Code - Optional 0..1 |
| Response | Response code and additional information. | ResponseDetails1 - Unknown 0..0 |
SupplementaryData building block
Additional information that cannot be captured in the structured elements and/or any other specific block. Additional information that can not be captured in the structured fields and/or any other specific block. For comparison, see the ISO20022 official specification
classDiagram
direction tb
%% SupplementaryData1 recursion level 0 with max 1
class SupplementaryData1{
PlaceAndName IsoMax350Text
}
SupplementaryData1 *-- "1..1" IsoSupplementaryDataEnvelope1 : Envelope
%% IsoSupplementaryDataEnvelope1 recursion level 1 with max 1
SupplementaryData1 members
| Member name | Description | Data Type / Multiplicity |
|---|---|---|
| PlaceAndName | Unambiguous reference to the location where the supplementary data must be inserted in the message instance. In the case of XML, this is expressed by a valid XPath. | IsoMax350Text - Optional 0..1 |
| Envelope | Technical element wrapping the supplementary data. | IsoSupplementaryDataEnvelope1 - Required 1..1 |
Extensibility and generalization considerations
To facilitate generalized design patterns in the system, the AccountSwitchPaymentResponseV01 implementation follows a specific implementaiton pattern. First of all, AccountSwitchPaymentResponseV01 impleemnts IOuterRecord indicating it is the outermost logical part of the message definition. Like all message wrappers, AccountSwitchPaymentResponseV01Document implements IOuterDocument. Because AccountSwitchPaymentResponseV01 implements IOuterDocument, it is a suitable template parameter for IOuterDocument, and causes the internal ‘Message’ to be of type AccountSwitchPaymentResponseV01.
classDiagram
class IOuterRecord
AccountSwitchPaymentResponseV01 --|> IOuterRecord : Implements
AccountSwitchPaymentResponseV01Document --|> IOuterDocument~AccountSwitchPaymentResponseV01~ : Implements
class IOuterDocument~AccountSwitchPaymentResponseV01~ {
AccountSwitchPaymentResponseV01 Message
}
Document wrapper for serialization
The only real purpose AccountSwitchPaymentResponseV01Document serves is to cause the document to be serialized into the ‘urn:iso:std:iso:20022:tech:xsd:acmt.035.001.01’ namespace. Therefore, it will probably be the usual practice to build the message and construct this wrapper at the last minute using AccountSwitchPaymentResponseV01.ToDocument() method. The returned AccountSwitchPaymentResponseV01Document value will serialize correctly according to ISO 20022 standards.
classDiagram
AccountSwitchPaymentResponseV01Document *-- AccountSwitchPaymentResponseV01 : Document
Sample of message format
This is an abbreviated version of what the message should look like.
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:acmt.035.001.01">
<AcctSwtchPmtRspn>
<MsgId>
<!-- MessageIdentification inner content -->
</MsgId>
<AcctSwtchDtls>
<!-- AccountSwitchDetails inner content -->
</AcctSwtchDtls>
<SplmtryData>
<!-- SupplementaryData inner content -->
</SplmtryData>
</AcctSwtchPmtRspn>
</Document>
Data from ISO specification
This is the technical data from the specification document.
<messageDefinition
xmi:id="_gmteAhMLEeSTk5fcu7tr9w"
nextVersions="_7HT_YW42EeiU9cctagi5ow"
name="AccountSwitchPaymentResponseV01"
definition="The AccountSwitchPaymentResponse message is sent by the new account servicer to the old account servicer to confirm whether it will make the requested payment in a request payment message. The AccountSwitchPaymentResponse message is only used to respond to a AccountSwitchRequestPayment message."
registrationStatus="Registered"
messageSet="_5yPOsCPkEemp2Y6dmY6qHw"
xmlTag="AcctSwtchPmtRspn"
rootElement="Document"
xmlns:xmi="http://www.omg.org/XMI">
<messageBuildingBlock
xmi:id="_5bTbwa5jEee17eDA_q0a9g"
nextVersions="_7HT_Y242EeiU9cctagi5ow"
name="MessageIdentification"
definition="Unique identification for the message."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="MsgId"
complexType="_Q7pG5Np-Ed-ak6NoX_4Aeg_-967008570" />
<messageBuildingBlock
xmi:id="_6fvUQa5jEee17eDA_q0a9g"
nextVersions="_7HT_ZW42EeiU9cctagi5ow"
name="AccountSwitchDetails"
definition="Contains information about the details of the account switch."
registrationStatus="Provisionally Registered"
maxOccurs="1"
minOccurs="1"
xmlTag="AcctSwtchDtls"
complexType="_8m2xcQ2ZEeSNWNtJlXOAhg" />
<messageBuildingBlock
xmi:id="_qlOy4A8DEeeJ4ZumUkzG4Q"
nextVersions="_7HT_Z242EeiU9cctagi5ow"
name="SupplementaryData"
definition="Additional information that cannot be captured in the structured elements and/or any other specific block."
registrationStatus="Provisionally Registered"
minOccurs="0"
xmlTag="SplmtryData"
complexType="_Qn0zC9p-Ed-ak6NoX_4Aeg_468227563" />
<messageDefinitionIdentifier
businessArea="acmt"
messageFunctionality="035"
flavour="001"
version="01" />
</messageDefinition>
ISO Building Blocks
The following items are used as building blocks to construct this message.