pain

type CreditorPaymentActivationRequestStatusReportV01 ¶

type CreditorPaymentActivationRequestStatusReportV01 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader46 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation25 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInformation5 `xml:"OrgnlPmtInfAndSts,omitempty"`
}

Scope This message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

func (c *CreditorPaymentActivationRequestStatusReportV01) AddGroupHeader() *iso20022.GroupHeader46

func (c *CreditorPaymentActivationRequestStatusReportV01) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation25

func (c *CreditorPaymentActivationRequestStatusReportV01) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInformation5

type CreditorPaymentActivationRequestStatusReportV02 ¶

type CreditorPaymentActivationRequestStatusReportV02 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader46 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation25 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction5 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope This message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

func (c *CreditorPaymentActivationRequestStatusReportV02) AddGroupHeader() *iso20022.GroupHeader46

func (c *CreditorPaymentActivationRequestStatusReportV02) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation25

func (c *CreditorPaymentActivationRequestStatusReportV02) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction5

func (c *CreditorPaymentActivationRequestStatusReportV02) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestStatusReportV03 ¶

type CreditorPaymentActivationRequestStatusReportV03 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader46 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation25 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction9 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequestStatusReport message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

func (c *CreditorPaymentActivationRequestStatusReportV03) AddGroupHeader() *iso20022.GroupHeader46

func (c *CreditorPaymentActivationRequestStatusReportV03) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation25

func (c *CreditorPaymentActivationRequestStatusReportV03) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction9

func (c *CreditorPaymentActivationRequestStatusReportV03) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestStatusReportV04 ¶

type CreditorPaymentActivationRequestStatusReportV04 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader46 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation25 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction14 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequestStatusReport message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

func (c *CreditorPaymentActivationRequestStatusReportV04) AddGroupHeader() *iso20022.GroupHeader46

func (c *CreditorPaymentActivationRequestStatusReportV04) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation25

func (c *CreditorPaymentActivationRequestStatusReportV04) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction14

func (c *CreditorPaymentActivationRequestStatusReportV04) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestStatusReportV05 ¶

type CreditorPaymentActivationRequestStatusReportV05 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader46 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation25 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction19 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequestStatusReport message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

func (c *CreditorPaymentActivationRequestStatusReportV05) AddGroupHeader() *iso20022.GroupHeader46

func (c *CreditorPaymentActivationRequestStatusReportV05) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation25

func (c *CreditorPaymentActivationRequestStatusReportV05) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction19

func (c *CreditorPaymentActivationRequestStatusReportV05) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestStatusReportV06 ¶

type CreditorPaymentActivationRequestStatusReportV06 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader46 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation28 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction24 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequestStatusReport message is sent by a party to the next party in the creditor payment activation request chain. It is used to inform the latter about the positive or negative status of a creditor payment activation request (either single or file).

func (c *CreditorPaymentActivationRequestStatusReportV06) AddGroupHeader() *iso20022.GroupHeader46

func (c *CreditorPaymentActivationRequestStatusReportV06) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation28

func (c *CreditorPaymentActivationRequestStatusReportV06) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction24

func (c *CreditorPaymentActivationRequestStatusReportV06) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestV01 ¶

type CreditorPaymentActivationRequestV01 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader45 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the creditor payment initiation.
	PaymentInformation []*iso20022.PaymentInstruction5 `xml:"PmtInf"`
}

Scope This message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used to initiate a creditor payment activation request.

func (c *CreditorPaymentActivationRequestV01) AddGroupHeader() *iso20022.GroupHeader45

func (c *CreditorPaymentActivationRequestV01) AddPaymentInformation() *iso20022.PaymentInstruction5

type CreditorPaymentActivationRequestV02 ¶

type CreditorPaymentActivationRequestV02 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader45 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the creditor payment initiation.
	PaymentInformation []*iso20022.PaymentInstruction8 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope This message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used to initiate a creditor payment activation request.

func (c *CreditorPaymentActivationRequestV02) AddGroupHeader() *iso20022.GroupHeader45

func (c *CreditorPaymentActivationRequestV02) AddPaymentInformation() *iso20022.PaymentInstruction8

func (c *CreditorPaymentActivationRequestV02) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestV03 ¶

type CreditorPaymentActivationRequestV03 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader45 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the creditor payment initiation.
	PaymentInformation []*iso20022.PaymentInstruction11 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequest message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used to initiate a creditor payment activation request.

func (c *CreditorPaymentActivationRequestV03) AddGroupHeader() *iso20022.GroupHeader45

func (c *CreditorPaymentActivationRequestV03) AddPaymentInformation() *iso20022.PaymentInstruction11

func (c *CreditorPaymentActivationRequestV03) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestV04 ¶

type CreditorPaymentActivationRequestV04 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader45 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the creditor payment initiation.
	PaymentInformation []*iso20022.PaymentInstruction17 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequest message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used to initiate a creditor payment activation request.

func (c *CreditorPaymentActivationRequestV04) AddGroupHeader() *iso20022.GroupHeader45

func (c *CreditorPaymentActivationRequestV04) AddPaymentInformation() *iso20022.PaymentInstruction17

func (c *CreditorPaymentActivationRequestV04) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestV05 ¶

type CreditorPaymentActivationRequestV05 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader45 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the creditor payment initiation.
	PaymentInformation []*iso20022.PaymentInstruction19 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequest message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used by a Creditor to request movement of funds from the debtor account to a creditor.

func (c *CreditorPaymentActivationRequestV05) AddGroupHeader() *iso20022.GroupHeader45

func (c *CreditorPaymentActivationRequestV05) AddPaymentInformation() *iso20022.PaymentInstruction19

func (c *CreditorPaymentActivationRequestV05) AddSupplementaryData() *iso20022.SupplementaryData1

type CreditorPaymentActivationRequestV06 ¶

type CreditorPaymentActivationRequestV06 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader45 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the creditor payment initiation.
	PaymentInformation []*iso20022.PaymentInstruction23 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

The CreditorPaymentActivationRequest message is sent by the Creditor sending party to the Debtor receiving party, directly or through agents. It is used by a Creditor to request movement of funds from the debtor account to a creditor.

func (c *CreditorPaymentActivationRequestV06) AddGroupHeader() *iso20022.GroupHeader45

func (c *CreditorPaymentActivationRequestV06) AddPaymentInformation() *iso20022.PaymentInstruction23

func (c *CreditorPaymentActivationRequestV06) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerCreditTransferInitiationV02 ¶

type CustomerCreditTransferInitiationV02 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader1 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstructionInformation1 `xml:"PmtInf"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead. If it is agreed to include the payment information related to the debit side only once (i.e. Grouped mode), the PaymentInformation block will be present only once. If it is agreed to repeat the payment information related to the debit side (i.e. Single mode), the PaymentInformation block must be present once per occurrence of the CreditTransferTransactionInformation block. The CustomerCreditTransferInitiation message also allows for a Mixed mode where the PaymentInformation block can be repeated and each PaymentInformation block can contain one or several CreditTransferTransactionInformation block(s). Single When grouping is set to Single, information for each individual instruction is included separately. This means the PaymentInformation block is repeated, and present for each occurrence of the CreditTransferTransactionInformation block. Grouped When grouping is set to Grouped, the PaymentInformation block will be present once and the CreditTransferTransactionInformation block will be repeated. Mixed When grouping is set to Mixed, the PaymentInformation block may be present once or may be repeated. Each sequence of the PaymentInformation block may contain one or several CreditTransferTransactionInformation block(s).

func (c *CustomerCreditTransferInitiationV02) AddGroupHeader() *iso20022.GroupHeader1

func (c *CustomerCreditTransferInitiationV02) AddPaymentInformation() *iso20022.PaymentInstructionInformation1

type CustomerCreditTransferInitiationV03 ¶

type CustomerCreditTransferInitiationV03 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader32 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstructionInformation3 `xml:"PmtInf"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

func (c *CustomerCreditTransferInitiationV03) AddGroupHeader() *iso20022.GroupHeader32

func (c *CustomerCreditTransferInitiationV03) AddPaymentInformation() *iso20022.PaymentInstructionInformation3

type CustomerCreditTransferInitiationV04 ¶

type CustomerCreditTransferInitiationV04 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader48 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstruction6 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

func (c *CustomerCreditTransferInitiationV04) AddGroupHeader() *iso20022.GroupHeader48

func (c *CustomerCreditTransferInitiationV04) AddPaymentInformation() *iso20022.PaymentInstruction6

func (c *CustomerCreditTransferInitiationV04) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerCreditTransferInitiationV05 ¶

type CustomerCreditTransferInitiationV05 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader48 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstruction9 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

func (c *CustomerCreditTransferInitiationV05) AddGroupHeader() *iso20022.GroupHeader48

func (c *CustomerCreditTransferInitiationV05) AddPaymentInformation() *iso20022.PaymentInstruction9

func (c *CustomerCreditTransferInitiationV05) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerCreditTransferInitiationV06 ¶

type CustomerCreditTransferInitiationV06 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader48 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstruction16 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

func (c *CustomerCreditTransferInitiationV06) AddGroupHeader() *iso20022.GroupHeader48

func (c *CustomerCreditTransferInitiationV06) AddPaymentInformation() *iso20022.PaymentInstruction16

func (c *CustomerCreditTransferInitiationV06) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerCreditTransferInitiationV07 ¶

type CustomerCreditTransferInitiationV07 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader48 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstruction20 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

func (c *CustomerCreditTransferInitiationV07) AddGroupHeader() *iso20022.GroupHeader48

func (c *CustomerCreditTransferInitiationV07) AddPaymentInformation() *iso20022.PaymentInstruction20

func (c *CustomerCreditTransferInitiationV07) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerCreditTransferInitiationV08 ¶

type CustomerCreditTransferInitiationV08 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader48 `xml:"GrpHdr"`

	// Set of characteristics that applies to the debit side of the payment transactions included in the credit transfer initiation.
	PaymentInformation []*iso20022.PaymentInstruction22 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerCreditTransferInitiation message is sent by the initiating party to the forwarding agent or debtor agent. It is used to request movement of funds from the debtor account to a creditor. Usage The CustomerCreditTransferInitiation message can contain one or more customer credit transfer instructions. The CustomerCreditTransferInitiation message is used to exchange: - One or more instances of a credit transfer initiation; - Payment transactions that result in book transfers at the debtor agent or payments to another financial institution; - Payment transactions that result in an electronic cash transfer to the creditor account or in the emission of a cheque. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the debtor agent. The debtor agent is the account servicer of the debtor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerCreditTransferInitiation message to the debtor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the debtor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerCreditTransferInitiation message can be used in domestic and cross-border scenarios. The CustomerCreditTransferInitiation message must not be used by the debtor agent to execute the credit transfer instruction(s). The FIToFICustomerCreditTransfer message must be used instead.

func (c *CustomerCreditTransferInitiationV08) AddGroupHeader() *iso20022.GroupHeader48

func (c *CustomerCreditTransferInitiationV08) AddPaymentInformation() *iso20022.PaymentInstruction22

func (c *CustomerCreditTransferInitiationV08) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerDirectDebitInitiationV01 ¶

type CustomerDirectDebitInitiationV01 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader1 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstructionInformation2 `xml:"PmtInf"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead. If it is agreed to include the payment information related to the credit side only once (i.e. Grouped mode), the PaymentInformation block will be present only once. If it is agreed to repeat the payment information related to the credit side (i.e. Single mode), the PaymentInformation block must be present once per occurrence of the DirectDebitTransactionInformation block. The CustomerDirectDebitInitiation message also allows for a Mixed mode where the PaymentInformation block can be repeated and each PaymentInformation block can contain one or several DirectDebitTransactionInformation block(s). Single When grouping is set to Single, information for each individual instruction is included separately. This means the PaymentInformation block is repeated, and present for each occurrence of the Direct Debit TransactionInformation block. Grouped When grouping is set to Grouped, the PaymentInformation block will be present once and the Direct Debit TransactionInformation block will be repeated. Mixed When grouping is set to Mixed, the PaymentInformation block may be present once or may be repeated. Each sequence of the PaymentInformation block may contain one or several Direct Debit TransactionInformation block(s).

func (c *CustomerDirectDebitInitiationV01) AddGroupHeader() *iso20022.GroupHeader1

func (c *CustomerDirectDebitInitiationV01) AddPaymentInformation() *iso20022.PaymentInstructionInformation2

type CustomerDirectDebitInitiationV02 ¶

type CustomerDirectDebitInitiationV02 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader39 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstructionInformation4 `xml:"PmtInf"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

func (c *CustomerDirectDebitInitiationV02) AddGroupHeader() *iso20022.GroupHeader39

func (c *CustomerDirectDebitInitiationV02) AddPaymentInformation() *iso20022.PaymentInstructionInformation4

type CustomerDirectDebitInitiationV03 ¶

type CustomerDirectDebitInitiationV03 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader55 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstruction7 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

func (c *CustomerDirectDebitInitiationV03) AddGroupHeader() *iso20022.GroupHeader55

func (c *CustomerDirectDebitInitiationV03) AddPaymentInformation() *iso20022.PaymentInstruction7

func (c *CustomerDirectDebitInitiationV03) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerDirectDebitInitiationV04 ¶

type CustomerDirectDebitInitiationV04 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader55 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstruction10 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

func (c *CustomerDirectDebitInitiationV04) AddGroupHeader() *iso20022.GroupHeader55

func (c *CustomerDirectDebitInitiationV04) AddPaymentInformation() *iso20022.PaymentInstruction10

func (c *CustomerDirectDebitInitiationV04) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerDirectDebitInitiationV05 ¶

type CustomerDirectDebitInitiationV05 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader55 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstruction15 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

func (c *CustomerDirectDebitInitiationV05) AddGroupHeader() *iso20022.GroupHeader55

func (c *CustomerDirectDebitInitiationV05) AddPaymentInformation() *iso20022.PaymentInstruction15

func (c *CustomerDirectDebitInitiationV05) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerDirectDebitInitiationV06 ¶

type CustomerDirectDebitInitiationV06 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader55 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstruction18 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

func (c *CustomerDirectDebitInitiationV06) AddGroupHeader() *iso20022.GroupHeader55

func (c *CustomerDirectDebitInitiationV06) AddPaymentInformation() *iso20022.PaymentInstruction18

func (c *CustomerDirectDebitInitiationV06) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerDirectDebitInitiationV07 ¶

type CustomerDirectDebitInitiationV07 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader55 `xml:"GrpHdr"`

	// Set of characteristics that apply to the credit side of the payment transactions included in the direct debit transaction initiation.
	PaymentInformation []*iso20022.PaymentInstruction21 `xml:"PmtInf"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerDirectDebitInitiation message is sent by the initiating party to the forwarding agent or creditor agent. It is used to request single or bulk collection(s) of funds from one or various debtor's account(s) for a creditor. Usage The CustomerDirectDebitInitiation message can contain one or more direct debit instructions. The message can be used in a direct or a relay scenario: - In a direct scenario, the message is sent directly to the creditor agent. The creditor agent is the account servicer of the creditor. - In a relay scenario, the message is sent to a forwarding agent. The forwarding agent acts as a concentrating financial institution. It will forward the CustomerDirectDebitInitiation message to the creditor agent. The message can also be used by an initiating party that has authority to send the message on behalf of the creditor. This caters for example for the scenario of a payments factory initiating all payments on behalf of a large corporate. The CustomerDirectDebitInitiation message can be used in domestic and cross-border scenarios. The CustomerDirectDebitInitiation may or may not contain mandate related information, i.e. extracts from a mandate, such as MandateIdentification or DateOfSignature. The CustomerDirectDebitInitiation message must not be considered as a mandate. The CustomerDirectDebitInitiation message must not be used by the creditor agent to execute the direct debit instruction(s). The FIToFICustomerDirectDebit message must be used instead.

func (c *CustomerDirectDebitInitiationV07) AddGroupHeader() *iso20022.GroupHeader55

func (c *CustomerDirectDebitInitiationV07) AddPaymentInformation() *iso20022.PaymentInstruction21

func (c *CustomerDirectDebitInitiationV07) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentReversalV01 ¶

type CustomerPaymentReversalV01 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader8 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupInformation5 `xml:"OrgnlGrpInf"`

	// Information concerning the original transactions, to which the reversal message refers.
	TransactionInformation []*iso20022.PaymentTransactionInformation4 `xml:"TxInf,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV01) AddGroupHeader() *iso20022.GroupHeader8

func (c *CustomerPaymentReversalV01) AddOriginalGroupInformation() *iso20022.OriginalGroupInformation5

func (c *CustomerPaymentReversalV01) AddTransactionInformation() *iso20022.PaymentTransactionInformation4

type CustomerPaymentReversalV02 ¶

type CustomerPaymentReversalV02 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader40 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupInformation22 `xml:"OrgnlGrpInf"`

	// Information concerning the original payment information, to which the reversal message refers.
	OriginalPaymentInformationAndReversal []*iso20022.OriginalPaymentInformation2 `xml:"OrgnlPmtInfAndRvsl,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV02) AddGroupHeader() *iso20022.GroupHeader40

func (c *CustomerPaymentReversalV02) AddOriginalGroupInformation() *iso20022.OriginalGroupInformation22

func (c *CustomerPaymentReversalV02) AddOriginalPaymentInformationAndReversal() *iso20022.OriginalPaymentInformation2

type CustomerPaymentReversalV03 ¶

type CustomerPaymentReversalV03 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader56 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupHeader3 `xml:"OrgnlGrpInf"`

	// Information concerning the original payment information, to which the reversal message refers.
	OriginalPaymentInformationAndReversal []*iso20022.OriginalPaymentInstruction2 `xml:"OrgnlPmtInfAndRvsl,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV03) AddGroupHeader() *iso20022.GroupHeader56

func (c *CustomerPaymentReversalV03) AddOriginalGroupInformation() *iso20022.OriginalGroupHeader3

func (c *CustomerPaymentReversalV03) AddOriginalPaymentInformationAndReversal() *iso20022.OriginalPaymentInstruction2

func (c *CustomerPaymentReversalV03) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentReversalV04 ¶

type CustomerPaymentReversalV04 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader56 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupHeader3 `xml:"OrgnlGrpInf"`

	// Information concerning the original payment information, to which the reversal message refers.
	OriginalPaymentInformationAndReversal []*iso20022.OriginalPaymentInstruction7 `xml:"OrgnlPmtInfAndRvsl,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV04) AddGroupHeader() *iso20022.GroupHeader56

func (c *CustomerPaymentReversalV04) AddOriginalGroupInformation() *iso20022.OriginalGroupHeader3

func (c *CustomerPaymentReversalV04) AddOriginalPaymentInformationAndReversal() *iso20022.OriginalPaymentInstruction7

func (c *CustomerPaymentReversalV04) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentReversalV05 ¶

type CustomerPaymentReversalV05 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader56 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupHeader3 `xml:"OrgnlGrpInf"`

	// Information concerning the original payment information, to which the reversal message refers.
	OriginalPaymentInformationAndReversal []*iso20022.OriginalPaymentInstruction11 `xml:"OrgnlPmtInfAndRvsl,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV05) AddGroupHeader() *iso20022.GroupHeader56

func (c *CustomerPaymentReversalV05) AddOriginalGroupInformation() *iso20022.OriginalGroupHeader3

func (c *CustomerPaymentReversalV05) AddOriginalPaymentInformationAndReversal() *iso20022.OriginalPaymentInstruction11

func (c *CustomerPaymentReversalV05) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentReversalV06 ¶

type CustomerPaymentReversalV06 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader56 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupHeader3 `xml:"OrgnlGrpInf"`

	// Information concerning the original payment information, to which the reversal message refers.
	OriginalPaymentInformationAndReversal []*iso20022.OriginalPaymentInstruction16 `xml:"OrgnlPmtInfAndRvsl,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV06) AddGroupHeader() *iso20022.GroupHeader56

func (c *CustomerPaymentReversalV06) AddOriginalGroupInformation() *iso20022.OriginalGroupHeader3

func (c *CustomerPaymentReversalV06) AddOriginalPaymentInformationAndReversal() *iso20022.OriginalPaymentInstruction16

func (c *CustomerPaymentReversalV06) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentReversalV07 ¶

type CustomerPaymentReversalV07 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader56 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupHeader3 `xml:"OrgnlGrpInf"`

	// Information concerning the original payment information, to which the reversal message refers.
	OriginalPaymentInformationAndReversal []*iso20022.OriginalPaymentInstruction21 `xml:"OrgnlPmtInfAndRvsl,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentReversal message is sent by the initiating party to the next party in the payment chain. It is used to reverse a payment previously executed. Usage The CustomerPaymentReversal message is exchanged between a non-financial institution customer and an agent to reverse a CustomerDirectDebitInitiation message that has been settled. The result will be a credit on the debtor account. The CustomerPaymentReversal message refers to the original CustomerDirectDebitInitiation message by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentReversal message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentReversalV07) AddGroupHeader() *iso20022.GroupHeader56

func (c *CustomerPaymentReversalV07) AddOriginalGroupInformation() *iso20022.OriginalGroupHeader3

func (c *CustomerPaymentReversalV07) AddOriginalPaymentInformationAndReversal() *iso20022.OriginalPaymentInstruction21

func (c *CustomerPaymentReversalV07) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentStatusReportV03 ¶

type CustomerPaymentStatusReportV03 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader36 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation20 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInformation1 `xml:"OrgnlPmtInfAndSts,omitempty"`
}

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentStatusReportV03) AddGroupHeader() *iso20022.GroupHeader36

func (c *CustomerPaymentStatusReportV03) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation20

func (c *CustomerPaymentStatusReportV03) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInformation1

type CustomerPaymentStatusReportV04 ¶

type CustomerPaymentStatusReportV04 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader52 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupHeader1 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction1 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentStatusReportV04) AddGroupHeader() *iso20022.GroupHeader52

func (c *CustomerPaymentStatusReportV04) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupHeader1

func (c *CustomerPaymentStatusReportV04) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction1

func (c *CustomerPaymentStatusReportV04) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentStatusReportV05 ¶

type CustomerPaymentStatusReportV05 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader52 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupHeader1 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction6 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentStatusReportV05) AddGroupHeader() *iso20022.GroupHeader52

func (c *CustomerPaymentStatusReportV05) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupHeader1

func (c *CustomerPaymentStatusReportV05) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction6

func (c *CustomerPaymentStatusReportV05) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentStatusReportV06 ¶

type CustomerPaymentStatusReportV06 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader52 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupHeader1 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction12 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentStatusReportV06) AddGroupHeader() *iso20022.GroupHeader52

func (c *CustomerPaymentStatusReportV06) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupHeader1

func (c *CustomerPaymentStatusReportV06) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction12

func (c *CustomerPaymentStatusReportV06) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentStatusReportV07 ¶

type CustomerPaymentStatusReportV07 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader52 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupHeader1 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction18 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios.

func (c *CustomerPaymentStatusReportV07) AddGroupHeader() *iso20022.GroupHeader52

func (c *CustomerPaymentStatusReportV07) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupHeader1

func (c *CustomerPaymentStatusReportV07) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction18

func (c *CustomerPaymentStatusReportV07) AddSupplementaryData() *iso20022.SupplementaryData1

type CustomerPaymentStatusReportV08 ¶

type CustomerPaymentStatusReportV08 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader52 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupHeader7 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original payment information, to which the status report message refers.
	OriginalPaymentInformationAndStatus []*iso20022.OriginalPaymentInstruction23 `xml:"OrgnlPmtInfAndSts,omitempty"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The CustomerPaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The CustomerPaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The CustomerPaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions. The CustomerPaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The CustomerPaymentStatusReport message can be used in domestic and cross-border scenarios. The CustomerPaymentStatusReport may also be sent to the receiver of the payment in a real time payment scenario, as both sides of the transactions must be informed of the status of the transaction (e.g. either the beneficiary is credited, or the transaction is rejected).

func (c *CustomerPaymentStatusReportV08) AddGroupHeader() *iso20022.GroupHeader52

func (c *CustomerPaymentStatusReportV08) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupHeader7

func (c *CustomerPaymentStatusReportV08) AddOriginalPaymentInformationAndStatus() *iso20022.OriginalPaymentInstruction23

func (c *CustomerPaymentStatusReportV08) AddSupplementaryData() *iso20022.SupplementaryData1

type Document00100102 ¶

type Document00100102 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.02 Document"`
	Message *CustomerCreditTransferInitiationV02 `xml:"pain.001.001.02"`
}

func (d *Document00100102) AddMessage() *CustomerCreditTransferInitiationV02

type Document00100103 ¶

type Document00100103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.03 Document"`
	Message *CustomerCreditTransferInitiationV03 `xml:"CstmrCdtTrfInitn"`
}

func (d *Document00100103) AddMessage() *CustomerCreditTransferInitiationV03

type Document00100104 ¶

type Document00100104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.04 Document"`
	Message *CustomerCreditTransferInitiationV04 `xml:"CstmrCdtTrfInitn"`
}

func (d *Document00100104) AddMessage() *CustomerCreditTransferInitiationV04

type Document00100105 ¶

type Document00100105 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.05 Document"`
	Message *CustomerCreditTransferInitiationV05 `xml:"CstmrCdtTrfInitn"`
}

func (d *Document00100105) AddMessage() *CustomerCreditTransferInitiationV05

type Document00100106 ¶

type Document00100106 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.06 Document"`
	Message *CustomerCreditTransferInitiationV06 `xml:"CstmrCdtTrfInitn"`
}

func (d *Document00100106) AddMessage() *CustomerCreditTransferInitiationV06

type Document00100107 ¶

type Document00100107 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.07 Document"`
	Message *CustomerCreditTransferInitiationV07 `xml:"CstmrCdtTrfInitn"`
}

func (d *Document00100107) AddMessage() *CustomerCreditTransferInitiationV07

type Document00100108 ¶

type Document00100108 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.001.001.08 Document"`
	Message *CustomerCreditTransferInitiationV08 `xml:"CstmrCdtTrfInitn"`
}

func (d *Document00100108) AddMessage() *CustomerCreditTransferInitiationV08

type Document00200102 ¶

type Document00200102 struct {
	XMLName xml.Name                `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.02 Document"`
	Message *PaymentStatusReportV02 `xml:"pain.002.001.02"`
}

func (d *Document00200102) AddMessage() *PaymentStatusReportV02

type Document00200103 ¶

type Document00200103 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.03 Document"`
	Message *CustomerPaymentStatusReportV03 `xml:"CstmrPmtStsRpt"`
}

func (d *Document00200103) AddMessage() *CustomerPaymentStatusReportV03

type Document00200104 ¶

type Document00200104 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.04 Document"`
	Message *CustomerPaymentStatusReportV04 `xml:"CstmrPmtStsRpt"`
}

func (d *Document00200104) AddMessage() *CustomerPaymentStatusReportV04

type Document00200105 ¶

type Document00200105 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.05 Document"`
	Message *CustomerPaymentStatusReportV05 `xml:"CstmrPmtStsRpt"`
}

func (d *Document00200105) AddMessage() *CustomerPaymentStatusReportV05

type Document00200106 ¶

type Document00200106 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.06 Document"`
	Message *CustomerPaymentStatusReportV06 `xml:"CstmrPmtStsRpt"`
}

func (d *Document00200106) AddMessage() *CustomerPaymentStatusReportV06

type Document00200107 ¶

type Document00200107 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.07 Document"`
	Message *CustomerPaymentStatusReportV07 `xml:"CstmrPmtStsRpt"`
}

func (d *Document00200107) AddMessage() *CustomerPaymentStatusReportV07

type Document00200108 ¶

type Document00200108 struct {
	XMLName xml.Name                        `xml:"urn:iso:std:iso:20022:tech:xsd:pain.002.001.08 Document"`
	Message *CustomerPaymentStatusReportV08 `xml:"CstmrPmtStsRpt"`
}

func (d *Document00200108) AddMessage() *CustomerPaymentStatusReportV08

type Document00600101 ¶

type Document00600101 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:pain.006.001.01 Document"`
	Message *PaymentCancellationRequestV01 `xml:"pain.006.001.01"`
}

func (d *Document00600101) AddMessage() *PaymentCancellationRequestV01

type Document00700101 ¶

type Document00700101 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.01 Document"`
	Message *CustomerPaymentReversalV01 `xml:"pain.007.001.01"`
}

func (d *Document00700101) AddMessage() *CustomerPaymentReversalV01

type Document00700102 ¶

type Document00700102 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.02 Document"`
	Message *CustomerPaymentReversalV02 `xml:"CstmrPmtRvsl"`
}

func (d *Document00700102) AddMessage() *CustomerPaymentReversalV02

type Document00700103 ¶

type Document00700103 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.03 Document"`
	Message *CustomerPaymentReversalV03 `xml:"CstmrPmtRvsl"`
}

func (d *Document00700103) AddMessage() *CustomerPaymentReversalV03

type Document00700104 ¶

type Document00700104 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.04 Document"`
	Message *CustomerPaymentReversalV04 `xml:"CstmrPmtRvsl"`
}

func (d *Document00700104) AddMessage() *CustomerPaymentReversalV04

type Document00700105 ¶

type Document00700105 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.05 Document"`
	Message *CustomerPaymentReversalV05 `xml:"CstmrPmtRvsl"`
}

func (d *Document00700105) AddMessage() *CustomerPaymentReversalV05

type Document00700106 ¶

type Document00700106 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.06 Document"`
	Message *CustomerPaymentReversalV06 `xml:"CstmrPmtRvsl"`
}

func (d *Document00700106) AddMessage() *CustomerPaymentReversalV06

type Document00700107 ¶

type Document00700107 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.007.001.07 Document"`
	Message *CustomerPaymentReversalV07 `xml:"CstmrPmtRvsl"`
}

func (d *Document00700107) AddMessage() *CustomerPaymentReversalV07

type Document00800101 ¶

type Document00800101 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.01 Document"`
	Message *CustomerDirectDebitInitiationV01 `xml:"pain.008.001.01"`
}

func (d *Document00800101) AddMessage() *CustomerDirectDebitInitiationV01

type Document00800102 ¶

type Document00800102 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.02 Document"`
	Message *CustomerDirectDebitInitiationV02 `xml:"CstmrDrctDbtInitn"`
}

func (d *Document00800102) AddMessage() *CustomerDirectDebitInitiationV02

type Document00800103 ¶

type Document00800103 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.03 Document"`
	Message *CustomerDirectDebitInitiationV03 `xml:"CstmrDrctDbtInitn"`
}

func (d *Document00800103) AddMessage() *CustomerDirectDebitInitiationV03

type Document00800104 ¶

type Document00800104 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.04 Document"`
	Message *CustomerDirectDebitInitiationV04 `xml:"CstmrDrctDbtInitn"`
}

func (d *Document00800104) AddMessage() *CustomerDirectDebitInitiationV04

type Document00800105 ¶

type Document00800105 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.05 Document"`
	Message *CustomerDirectDebitInitiationV05 `xml:"CstmrDrctDbtInitn"`
}

func (d *Document00800105) AddMessage() *CustomerDirectDebitInitiationV05

type Document00800106 ¶

type Document00800106 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.06 Document"`
	Message *CustomerDirectDebitInitiationV06 `xml:"CstmrDrctDbtInitn"`
}

func (d *Document00800106) AddMessage() *CustomerDirectDebitInitiationV06

type Document00800107 ¶

type Document00800107 struct {
	XMLName xml.Name                          `xml:"urn:iso:std:iso:20022:tech:xsd:pain.008.001.07 Document"`
	Message *CustomerDirectDebitInitiationV07 `xml:"CstmrDrctDbtInitn"`
}

func (d *Document00800107) AddMessage() *CustomerDirectDebitInitiationV07

type Document00900101 ¶

type Document00900101 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:pain.009.001.01 Document"`
	Message *MandateInitiationRequestV01 `xml:"MndtInitnReq"`
}

func (d *Document00900101) AddMessage() *MandateInitiationRequestV01

type Document00900102 ¶

type Document00900102 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:pain.009.001.02 Document"`
	Message *MandateInitiationRequestV02 `xml:"MndtInitnReq"`
}

func (d *Document00900102) AddMessage() *MandateInitiationRequestV02

type Document00900103 ¶

type Document00900103 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:pain.009.001.03 Document"`
	Message *MandateInitiationRequestV03 `xml:"MndtInitnReq"`
}

func (d *Document00900103) AddMessage() *MandateInitiationRequestV03

type Document00900104 ¶

type Document00900104 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:pain.009.001.04 Document"`
	Message *MandateInitiationRequestV04 `xml:"MndtInitnReq"`
}

func (d *Document00900104) AddMessage() *MandateInitiationRequestV04

type Document00900105 ¶

type Document00900105 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:pain.009.001.05 Document"`
	Message *MandateInitiationRequestV05 `xml:"MndtInitnReq"`
}

func (d *Document00900105) AddMessage() *MandateInitiationRequestV05

type Document01000101 ¶

type Document01000101 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.010.001.01 Document"`
	Message *MandateAmendmentRequestV01 `xml:"MndtAmdmntReq"`
}

func (d *Document01000101) AddMessage() *MandateAmendmentRequestV01

type Document01000102 ¶

type Document01000102 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.010.001.02 Document"`
	Message *MandateAmendmentRequestV02 `xml:"MndtAmdmntReq"`
}

func (d *Document01000102) AddMessage() *MandateAmendmentRequestV02

type Document01000103 ¶

type Document01000103 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.010.001.03 Document"`
	Message *MandateAmendmentRequestV03 `xml:"MndtAmdmntReq"`
}

func (d *Document01000103) AddMessage() *MandateAmendmentRequestV03

type Document01000104 ¶

type Document01000104 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.010.001.04 Document"`
	Message *MandateAmendmentRequestV04 `xml:"MndtAmdmntReq"`
}

func (d *Document01000104) AddMessage() *MandateAmendmentRequestV04

type Document01000105 ¶

type Document01000105 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.010.001.05 Document"`
	Message *MandateAmendmentRequestV05 `xml:"MndtAmdmntReq"`
}

func (d *Document01000105) AddMessage() *MandateAmendmentRequestV05

type Document01100101 ¶

type Document01100101 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:pain.011.001.01 Document"`
	Message *MandateCancellationRequestV01 `xml:"MndtCxlReq"`
}

func (d *Document01100101) AddMessage() *MandateCancellationRequestV01

type Document01100102 ¶

type Document01100102 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:pain.011.001.02 Document"`
	Message *MandateCancellationRequestV02 `xml:"MndtCxlReq"`
}

func (d *Document01100102) AddMessage() *MandateCancellationRequestV02

type Document01100103 ¶

type Document01100103 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:pain.011.001.03 Document"`
	Message *MandateCancellationRequestV03 `xml:"MndtCxlReq"`
}

func (d *Document01100103) AddMessage() *MandateCancellationRequestV03

type Document01100104 ¶

type Document01100104 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:pain.011.001.04 Document"`
	Message *MandateCancellationRequestV04 `xml:"MndtCxlReq"`
}

func (d *Document01100104) AddMessage() *MandateCancellationRequestV04

type Document01100105 ¶

type Document01100105 struct {
	XMLName xml.Name                       `xml:"urn:iso:std:iso:20022:tech:xsd:pain.011.001.05 Document"`
	Message *MandateCancellationRequestV05 `xml:"MndtCxlReq"`
}

func (d *Document01100105) AddMessage() *MandateCancellationRequestV05

type Document01200101 ¶

type Document01200101 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.012.001.01 Document"`
	Message *MandateAcceptanceReportV01 `xml:"MndtAccptncRpt"`
}

func (d *Document01200101) AddMessage() *MandateAcceptanceReportV01

type Document01200102 ¶

type Document01200102 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.012.001.02 Document"`
	Message *MandateAcceptanceReportV02 `xml:"MndtAccptncRpt"`
}

func (d *Document01200102) AddMessage() *MandateAcceptanceReportV02

type Document01200103 ¶

type Document01200103 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.012.001.03 Document"`
	Message *MandateAcceptanceReportV03 `xml:"MndtAccptncRpt"`
}

func (d *Document01200103) AddMessage() *MandateAcceptanceReportV03

type Document01200104 ¶

type Document01200104 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.012.001.04 Document"`
	Message *MandateAcceptanceReportV04 `xml:"MndtAccptncRpt"`
}

func (d *Document01200104) AddMessage() *MandateAcceptanceReportV04

type Document01200105 ¶

type Document01200105 struct {
	XMLName xml.Name                    `xml:"urn:iso:std:iso:20022:tech:xsd:pain.012.001.05 Document"`
	Message *MandateAcceptanceReportV05 `xml:"MndtAccptncRpt"`
}

func (d *Document01200105) AddMessage() *MandateAcceptanceReportV05

type Document01300101 ¶

type Document01300101 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.013.001.01 Document"`
	Message *CreditorPaymentActivationRequestV01 `xml:"CdtrPmtActvtnReq"`
}

func (d *Document01300101) AddMessage() *CreditorPaymentActivationRequestV01

type Document01300102 ¶

type Document01300102 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.013.001.02 Document"`
	Message *CreditorPaymentActivationRequestV02 `xml:"CdtrPmtActvtnReq"`
}

func (d *Document01300102) AddMessage() *CreditorPaymentActivationRequestV02

type Document01300103 ¶

type Document01300103 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.013.001.03 Document"`
	Message *CreditorPaymentActivationRequestV03 `xml:"CdtrPmtActvtnReq"`
}

func (d *Document01300103) AddMessage() *CreditorPaymentActivationRequestV03

type Document01300104 ¶

type Document01300104 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.013.001.04 Document"`
	Message *CreditorPaymentActivationRequestV04 `xml:"CdtrPmtActvtnReq"`
}

func (d *Document01300104) AddMessage() *CreditorPaymentActivationRequestV04

type Document01300105 ¶

type Document01300105 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.013.001.05 Document"`
	Message *CreditorPaymentActivationRequestV05 `xml:"CdtrPmtActvtnReq"`
}

func (d *Document01300105) AddMessage() *CreditorPaymentActivationRequestV05

type Document01300106 ¶

type Document01300106 struct {
	XMLName xml.Name                             `xml:"urn:iso:std:iso:20022:tech:xsd:pain.013.001.06 Document"`
	Message *CreditorPaymentActivationRequestV06 `xml:"CdtrPmtActvtnReq"`
}

func (d *Document01300106) AddMessage() *CreditorPaymentActivationRequestV06

type Document01400101 ¶

type Document01400101 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:pain.014.001.01 Document"`
	Message *CreditorPaymentActivationRequestStatusReportV01 `xml:"CdtrPmtActvtnReqStsRpt"`
}

func (d *Document01400101) AddMessage() *CreditorPaymentActivationRequestStatusReportV01

type Document01400102 ¶

type Document01400102 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:pain.014.001.02 Document"`
	Message *CreditorPaymentActivationRequestStatusReportV02 `xml:"CdtrPmtActvtnReqStsRpt"`
}

func (d *Document01400102) AddMessage() *CreditorPaymentActivationRequestStatusReportV02

type Document01400103 ¶

type Document01400103 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:pain.014.001.03 Document"`
	Message *CreditorPaymentActivationRequestStatusReportV03 `xml:"CdtrPmtActvtnReqStsRpt"`
}

func (d *Document01400103) AddMessage() *CreditorPaymentActivationRequestStatusReportV03

type Document01400104 ¶

type Document01400104 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:pain.014.001.04 Document"`
	Message *CreditorPaymentActivationRequestStatusReportV04 `xml:"CdtrPmtActvtnReqStsRpt"`
}

func (d *Document01400104) AddMessage() *CreditorPaymentActivationRequestStatusReportV04

type Document01400105 ¶

type Document01400105 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:pain.014.001.05 Document"`
	Message *CreditorPaymentActivationRequestStatusReportV05 `xml:"CdtrPmtActvtnReqStsRpt"`
}

func (d *Document01400105) AddMessage() *CreditorPaymentActivationRequestStatusReportV05

type Document01400106 ¶

type Document01400106 struct {
	XMLName xml.Name                                         `xml:"urn:iso:std:iso:20022:tech:xsd:pain.014.001.06 Document"`
	Message *CreditorPaymentActivationRequestStatusReportV06 `xml:"CdtrPmtActvtnReqStsRpt"`
}

func (d *Document01400106) AddMessage() *CreditorPaymentActivationRequestStatusReportV06

type Document01700101 ¶

type Document01700101 struct {
	XMLName xml.Name               `xml:"urn:iso:std:iso:20022:tech:xsd:pain.017.001.01 Document"`
	Message *MandateCopyRequestV01 `xml:"MndtCpyReq"`
}

func (d *Document01700101) AddMessage() *MandateCopyRequestV01

type Document01800101 ¶

type Document01800101 struct {
	XMLName xml.Name                     `xml:"urn:iso:std:iso:20022:tech:xsd:pain.018.001.01 Document"`
	Message *MandateSuspensionRequestV01 `xml:"MndtSspnsnReq"`
}

func (d *Document01800101) AddMessage() *MandateSuspensionRequestV01

type MandateAcceptanceReportV01 ¶

type MandateAcceptanceReportV01 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader31 `xml:"GrpHdr"`

	// Set of elements used to provide information on the acception or rejection of the mandate request.
	UnderlyingAcceptanceDetails *iso20022.MandateAcceptance1 `xml:"UndrlygAccptncDtls"`
}

Scope The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor). A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver. Usage The MandateAcceptanceReport message can contain only one confirmation of acceptance of rejection of one specific MandateRequest message. The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor. The MandateAcceptanceReport message can be used in domestic and cross-border scenarios.

func (m *MandateAcceptanceReportV01) AddGroupHeader() *iso20022.GroupHeader31

func (m *MandateAcceptanceReportV01) AddUnderlyingAcceptanceDetails() *iso20022.MandateAcceptance1

type MandateAcceptanceReportV02 ¶

type MandateAcceptanceReportV02 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide information on the acception or rejection of the mandate request.
	UnderlyingAcceptanceDetails *iso20022.MandateAcceptance2 `xml:"UndrlygAccptncDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor). A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver. Usage The MandateAcceptanceReport message can contain only one confirmation of acceptance of rejection of one specific MandateRequest message. The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor. The MandateAcceptanceReport message can be used in domestic and cross-border scenarios.

func (m *MandateAcceptanceReportV02) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAcceptanceReportV02) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAcceptanceReportV02) AddUnderlyingAcceptanceDetails() *iso20022.MandateAcceptance2

type MandateAcceptanceReportV03 ¶

type MandateAcceptanceReportV03 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide information on the acception or rejection of the mandate request.
	UnderlyingAcceptanceDetails []*iso20022.MandateAcceptance3 `xml:"UndrlygAccptncDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor). A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver. Usage The MandateAcceptanceReport message can contain one or more confirmation(s) of acceptance or rejection of a specific Mandate Request. The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor. The MandateAcceptanceReport message can be used in domestic and cross-border scenarios.

func (m *MandateAcceptanceReportV03) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAcceptanceReportV03) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAcceptanceReportV03) AddUnderlyingAcceptanceDetails() *iso20022.MandateAcceptance3

type MandateAcceptanceReportV04 ¶

type MandateAcceptanceReportV04 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide information on the acception or rejection of the mandate request.
	UnderlyingAcceptanceDetails []*iso20022.MandateAcceptance4 `xml:"UndrlygAccptncDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor). A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver. Usage The MandateAcceptanceReport message can contain one or more confirmation(s) of acceptance or rejection of a specific Mandate Request. The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor. The MandateAcceptanceReport message can be used in domestic and cross-border scenarios.

func (m *MandateAcceptanceReportV04) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAcceptanceReportV04) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAcceptanceReportV04) AddUnderlyingAcceptanceDetails() *iso20022.MandateAcceptance4

type MandateAcceptanceReportV05 ¶

type MandateAcceptanceReportV05 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate acceptance, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Provides information on the acceptance or rejection of the mandate request.
	UnderlyingAcceptanceDetails []*iso20022.MandateAcceptance5 `xml:"UndrlygAccptncDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateAcceptanceReport message is sent from the agent of the receiver (debtor or creditor) of the MandateRequest message (initiation, amendment or cancellation) to the agent of the initiator of the MandateRequest message (debtor or creditor). A MandateAcceptanceReport message is used to confirm the acceptance or rejection of a MandateRequest message. Where acceptance is part of the full process flow, a MandateRequest message only becomes valid after a confirmation of acceptance is received through a MandateAcceptanceReport message from the agent of the receiver. Usage The MandateAcceptanceReport message can contain one or more confirmation(s) of acceptance or rejection of a specific Mandate Request. The messages can be exchanged between debtor agent and creditor agent and between debtor agent and debtor and creditor agent and creditor. The MandateAcceptanceReport message can be used in domestic and cross-border scenarios.

func (m *MandateAcceptanceReportV05) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAcceptanceReportV05) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAcceptanceReportV05) AddUnderlyingAcceptanceDetails() *iso20022.MandateAcceptance5

type MandateAmendmentRequestV01 ¶

type MandateAmendmentRequestV01 struct {

	// 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.
	GroupHeader *iso20022.GroupHeader31 `xml:"GrpHdr"`

	// Set of elements used to provide details on the amendment request.
	UnderlyingAmendmentDetails *iso20022.MandateAmendment1 `xml:"UndrlygAmdmntDtls"`
}

Scope 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. Usage The MandateAmendmentRequest message can contain only one request to amend one 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.

func (m *MandateAmendmentRequestV01) AddGroupHeader() *iso20022.GroupHeader31

func (m *MandateAmendmentRequestV01) AddUnderlyingAmendmentDetails() *iso20022.MandateAmendment1

type MandateAmendmentRequestV02 ¶

type MandateAmendmentRequestV02 struct {

	// 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.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the amendment request.
	UnderlyingAmendmentDetails *iso20022.MandateAmendment2 `xml:"UndrlygAmdmntDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope 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. Usage The MandateAmendmentRequest message can contain only one request to amend one 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.

func (m *MandateAmendmentRequestV02) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAmendmentRequestV02) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAmendmentRequestV02) AddUnderlyingAmendmentDetails() *iso20022.MandateAmendment2

type MandateAmendmentRequestV03 ¶

type MandateAmendmentRequestV03 struct {

	// 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.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the amendment request.
	UnderlyingAmendmentDetails []*iso20022.MandateAmendment3 `xml:"UndrlygAmdmntDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope 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. Usage 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.

func (m *MandateAmendmentRequestV03) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAmendmentRequestV03) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAmendmentRequestV03) AddUnderlyingAmendmentDetails() *iso20022.MandateAmendment3

type MandateAmendmentRequestV04 ¶

type MandateAmendmentRequestV04 struct {

	// 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.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the amendment request.
	UnderlyingAmendmentDetails []*iso20022.MandateAmendment4 `xml:"UndrlygAmdmntDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope 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. Usage 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.

func (m *MandateAmendmentRequestV04) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAmendmentRequestV04) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAmendmentRequestV04) AddUnderlyingAmendmentDetails() *iso20022.MandateAmendment4

type MandateAmendmentRequestV05 ¶

type MandateAmendmentRequestV05 struct {

	// 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.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the amendment request.
	UnderlyingAmendmentDetails []*iso20022.MandateAmendment5 `xml:"UndrlygAmdmntDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope 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. Usage 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.

func (m *MandateAmendmentRequestV05) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateAmendmentRequestV05) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateAmendmentRequestV05) AddUnderlyingAmendmentDetails() *iso20022.MandateAmendment5

type MandateCancellationRequestV01 ¶

type MandateCancellationRequestV01 struct {

	// Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader31 `xml:"GrpHdr"`

	// Set of elements used to provide details on the cancellation request.
	UnderlyingCancellationDetails *iso20022.MandateCancellation1 `xml:"UndrlygCxlDtls"`
}

Scope The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties. Usage The MandateCancellationRequest message can contain only one request to cancel one 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 MandateCancellationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateCancellationRequestV01) AddGroupHeader() *iso20022.GroupHeader31

func (m *MandateCancellationRequestV01) AddUnderlyingCancellationDetails() *iso20022.MandateCancellation1

type MandateCancellationRequestV02 ¶

type MandateCancellationRequestV02 struct {

	// Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the cancellation request.
	UnderlyingCancellationDetails *iso20022.MandateCancellation2 `xml:"UndrlygCxlDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties. Usage The MandateCancellationRequest message can contain only one request to cancel one 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 MandateCancellationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateCancellationRequestV02) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateCancellationRequestV02) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateCancellationRequestV02) AddUnderlyingCancellationDetails() *iso20022.MandateCancellation2

type MandateCancellationRequestV03 ¶

type MandateCancellationRequestV03 struct {

	// Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the cancellation request.
	UnderlyingCancellationDetails []*iso20022.MandateCancellation3 `xml:"UndrlygCxlDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties. Usage The MandateCancellationRequest message can contain one or more request(s) to cancel 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 MandateCancellationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateCancellationRequestV03) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateCancellationRequestV03) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateCancellationRequestV03) AddUnderlyingCancellationDetails() *iso20022.MandateCancellation3

type MandateCancellationRequestV04 ¶

type MandateCancellationRequestV04 struct {

	// Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the cancellation request.
	UnderlyingCancellationDetails []*iso20022.MandateCancellation4 `xml:"UndrlygCxlDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties. Usage The MandateCancellationRequest message can contain one or more request(s) to cancel 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 MandateCancellationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateCancellationRequestV04) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateCancellationRequestV04) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateCancellationRequestV04) AddUnderlyingCancellationDetails() *iso20022.MandateCancellation4

type MandateCancellationRequestV05 ¶

type MandateCancellationRequestV05 struct {

	// Set of characteristics to identify the message and parties playing a role in the cancellation of the mandate, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide details on the cancellation request.
	UnderlyingCancellationDetails []*iso20022.MandateCancellation5 `xml:"UndrlygCxlDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateCancellationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCancellationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCancellationRequest message is used to request the cancellation of an existing mandate. If accepted, this MandateCancellationRequest message together with the MandateAcceptanceReport message confirming the acceptance will be considered a valid cancellation of an existing mandate, agreed upon by all parties. Usage The MandateCancellationRequest message can contain one or more request(s) to cancel 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 MandateCancellationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateCancellationRequestV05) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateCancellationRequestV05) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateCancellationRequestV05) AddUnderlyingCancellationDetails() *iso20022.MandateCancellation5

type MandateCopyRequestV01 ¶

type MandateCopyRequestV01 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate copy request, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of information used to identify the mandate for which a copy is requested.
	UnderlyingCopyRequestDetails []*iso20022.MandateCopy1 `xml:"UndrlygCpyReqDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateCopyRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateCopyRequest message is forwarded by the agent of the initiator to the agent of the counterparty. A MandateCopyRequest message is used to request a copy of an existing mandate. If accepted, the mandate copy can be sent using the MandateAcceptanceReport message. Usage The MandateCopyRequest message can contain one or more copy requests. 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 MandateCopyRequest message can be used in domestic and cross-border scenarios.

func (m *MandateCopyRequestV01) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateCopyRequestV01) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateCopyRequestV01) AddUnderlyingCopyRequestDetails() *iso20022.MandateCopy1

type MandateInitiationRequestV01 ¶

type MandateInitiationRequestV01 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate initiation, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader31 `xml:"GrpHdr"`

	// Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor.
	Mandate *iso20022.MandateInformation2 `xml:"Mndt"`
}

Scope The MandateInitiationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. The MandateInitiationRequest message is used to set-up the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor. Usage The MandateInitiationRequest message can contain only one request to set-up one 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateInitiationRequestV01) AddGroupHeader() *iso20022.GroupHeader31

func (m *MandateInitiationRequestV01) AddMandate() *iso20022.MandateInformation2

type MandateInitiationRequestV02 ¶

type MandateInitiationRequestV02 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate initiation, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor.
	Mandate *iso20022.Mandate2 `xml:"Mndt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateInitiationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. The MandateInitiationRequest message is used to set-up the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor. Usage The MandateInitiationRequest message can contain only one request to set-up one 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateInitiationRequestV02) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateInitiationRequestV02) AddMandate() *iso20022.Mandate2

func (m *MandateInitiationRequestV02) AddSupplementaryData() *iso20022.SupplementaryData1

type MandateInitiationRequestV03 ¶

type MandateInitiationRequestV03 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate initiation, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor.
	Mandate []*iso20022.Mandate4 `xml:"Mndt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateInitiationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. The MandateInitiationRequest message is used to set-up the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor. Usage The MandateInitiationRequest message can contain one or more request(s) to set-up 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateInitiationRequestV03) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateInitiationRequestV03) AddMandate() *iso20022.Mandate4

func (m *MandateInitiationRequestV03) AddSupplementaryData() *iso20022.SupplementaryData1

type MandateInitiationRequestV04 ¶

type MandateInitiationRequestV04 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate initiation, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor.
	Mandate []*iso20022.Mandate7 `xml:"Mndt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateInitiationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. The MandateInitiationRequest message is used to setup the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor. Usage The MandateInitiationRequest message can contain one or more request(s) to setup 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateInitiationRequestV04) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateInitiationRequestV04) AddMandate() *iso20022.Mandate7

func (m *MandateInitiationRequestV04) AddSupplementaryData() *iso20022.SupplementaryData1

type MandateInitiationRequestV05 ¶

type MandateInitiationRequestV05 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate initiation, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide the details of the mandate signed between the (ultimate) creditor and the (ultimate) debtor.
	Mandate []*iso20022.Mandate10 `xml:"Mndt"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateInitiationRequest message is sent by the initiator of the request to his agent. The initiator can either be the debtor or the creditor. The MandateInitiationRequest message is forwarded by the agent of the initiator to the agent of the counterparty. The MandateInitiationRequest message is used to setup the instruction that allows the debtor agent to accept instructions from the creditor, through the creditor agent, to debit the account of the debtor. Usage The MandateInitiationRequest message can contain one or more request(s) to setup 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 MandateInitiationRequest message can be used in domestic and cross-border scenarios.

func (m *MandateInitiationRequestV05) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateInitiationRequestV05) AddMandate() *iso20022.Mandate10

func (m *MandateInitiationRequestV05) AddSupplementaryData() *iso20022.SupplementaryData1

type MandateSuspensionRequestV01 ¶

type MandateSuspensionRequestV01 struct {

	// Set of characteristics to identify the message and parties playing a role in the mandate suspension request, but which are not part of the mandate.
	GroupHeader *iso20022.GroupHeader47 `xml:"GrpHdr"`

	// Set of elements used to provide information on the suspension request of the mandate.
	UnderlyingSuspensionDetails []*iso20022.MandateSuspension1 `xml:"UndrlygSspnsnDtls"`

	// Additional information that cannot be captured in the structured elements and/or any other specific block.
	SupplementaryData []*iso20022.SupplementaryData1 `xml:"SplmtryData,omitempty"`
}

Scope The MandateSuspensionRequest message is sent by the initiator of the request to its agent. The initiator can either be the debtor, debtor agent, creditor or creditor agent. A MandateSuspensionRequest message is used to request the suspension of an existing mandate until the suspension is lifted. Usage The MandateSuspensionRequest message can contain one or more suspension requests. The messages can be exchanged between creditor and creditor agent or debtor and debtor agent and between creditor agent and debtor agent. The MandateSuspensionRequest message can be used in domestic and cross-border scenarios.

func (m *MandateSuspensionRequestV01) AddGroupHeader() *iso20022.GroupHeader47

func (m *MandateSuspensionRequestV01) AddSupplementaryData() *iso20022.SupplementaryData1

func (m *MandateSuspensionRequestV01) AddUnderlyingSuspensionDetails() *iso20022.MandateSuspension1

type PaymentCancellationRequestV01 ¶

type PaymentCancellationRequestV01 struct {

	// Set of characteristics shared by all individual transactions included in the message.
	GroupHeader *iso20022.GroupHeader7 `xml:"GrpHdr"`

	// Information concerning the original group of transactions, to which the message refers.
	OriginalGroupInformation *iso20022.OriginalGroupInformation4 `xml:"OrgnlGrpInf"`

	// Information concerning the original transactions, to which the cancellation request message refers.
	TransactionInformation []*iso20022.PaymentTransactionInformation3 `xml:"TxInf,omitempty"`
}

Scope The PaymentCancellationRequest message is sent by the initiating party or any agent, to the next party in the payment chain. It is used to request the cancellation of an instruction previously sent. Usage The PaymentCancellationRequest message is exchanged between non-financial institution customers and agents to request the cancellation of a payment initiation message previously sent (i.e. the CustomerCreditTransferInitiation message and the CustomerDirectDebitInitiation messages). The PaymentCancellationRequest message can be used to request the cancellation of single instructions or multiple instructions, from one or multiple files. The PaymentCancellationRequest message can be used in domestic and cross-border scenarios. The PaymentCancellationRequest message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The PaymentCancellationRequest message exchanged between non-financial institution customers and agents is identified in the schema as follows: urn:iso:std:iso:20022:tech:xsd:pain.006.001.01

func (p *PaymentCancellationRequestV01) AddGroupHeader() *iso20022.GroupHeader7

func (p *PaymentCancellationRequestV01) AddOriginalGroupInformation() *iso20022.OriginalGroupInformation4

func (p *PaymentCancellationRequestV01) AddTransactionInformation() *iso20022.PaymentTransactionInformation3

type PaymentStatusReportV02 ¶

type PaymentStatusReportV02 struct {

	// Set of characteristics shared by all individual transactions included in the status report message.
	GroupHeader *iso20022.GroupHeader5 `xml:"GrpHdr"`

	// Original group information concerning the group of transactions, to which the status report message refers to.
	OriginalGroupInformationAndStatus *iso20022.OriginalGroupInformation1 `xml:"OrgnlGrpInfAndSts"`

	// Information concerning the original transactions, to which the status report message refers.
	TransactionInformationAndStatus []*iso20022.PaymentTransactionInformation1 `xml:"TxInfAndSts,omitempty"`
}

Scope The PaymentStatusReport message is sent by an instructed agent to the previous party in the payment chain. It is used to inform this party about the positive or negative status of an instruction (either single or file). It is also used to report on a pending instruction. Usage The PaymentStatusReport message is exchanged between an agent and a non-financial institution customer to provide status information on instructions previously sent. Its usage will always be governed by a bilateral agreement between the agent and the non-financial institution customer. The PaymentStatusReport message can be used to provide information about the status (e.g. rejection, acceptance) of the initiation of a credit transfer, a direct debit, as well as on the initiation of other customer instructions (e.g. PaymentCancellationRequest). The PaymentStatusReport message refers to the original instruction(s) by means of references only or by means of references and a set of elements from the original instruction. The PaymentStatusReport message can be used in domestic and cross-border scenarios. The PaymentStatusReport message exchanged between agents and non-financial institution customers is identified in the schema as follows: urn:iso:std:iso:20022:tech:xsd:pain.002.001.02

func (p *PaymentStatusReportV02) AddGroupHeader() *iso20022.GroupHeader5

func (p *PaymentStatusReportV02) AddOriginalGroupInformationAndStatus() *iso20022.OriginalGroupInformation1

func (p *PaymentStatusReportV02) AddTransactionInformationAndStatus() *iso20022.PaymentTransactionInformation1