Validations

The purpose of this page is to summarise the additional usage validations performed by the Iberpay (SCT Inst) scheme pack when processing a message.

All messages undergo an XSD schema check to make sure that the fields are technically correct, but only certain fields have additional usage validations performed on them. If an additional usage validation is not listed below then it is not validated by the scheme pack.

This is in line with Icon’s rationale and prioritisation of making sure client constructed messages conform to all scheme rules and are not likely to be rejected, please refer to CSM Service - Validations. Messages from the scheme have, however, already been validated, so the priority for those is swift, safe processing through to the customer’s account.

Inbound pacs.008

The following validations are performed on an Inbound pacs.008 from the scheme. Failures will result in a pacs.002 sent back to the scheme with the Return Code quoted below, and an ERROR level InboundMessageFailed system event to inform the Client.

Field

Validation Details

Return Code

System Event Description

All Fields

Checks if the message is valid against the Iberpay (SCT Inst) pacs.008 xsd

FF01

An error message from schema validation failure.

Example:

org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08":CreDtTm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08":MsgId}' is expected.

GrpHdr+TtlIntrBkSttlmAmt

Must be equal to the value of the underlying transactions

IT05

Interbank Settlement Amount between group header and transaction do not match

CdtTrfTxInf+PmtId++TxId

Technical Duplicate Check (same DbtrAgt and TxId) within timeframe configured by iberpay.rule.processing-entity.pacs008-duplicate-message-check-period

AM05

Duplicate Transaction

CdtTrfTxInf+UltmtDbtr++Id+++OrgId

Either 'AnyBIC', 'LEI' and/or one occurrence of 'Other' is allowed

FF01

One of:

  • OrganisationIdentification is present but no subfields (AnyBIC, LEI, Other) are populated in CdtTrfTxInf.UltmtDbtr.Id.OrgId

  • Only one occurrence of Other is allowed in CdtTrfTxInf.UltmtDbtr.Id.OrgId

CdtTrfTxInf+UltmtDbtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.UltmtDbtr.Id.PrvtId

CdtTrfTxInf+Dbtr++PstlAdr+++Ctry

Debtor Postal Address Country is mandatory if Debtor Agent and/or Creditor Agent are not in the EEA. Note - this validation can be disabled - see configurations page.

RR02

CdtTrfTxinf.Dbtr.PstlAdr.Ctry is mandatory if payment involves a non-EEA country or territory

CdtTrfTxInf+Dbtr++PstlAdr

Addresses are classified according to the address fields populated as per the Postal Address Structural Validations

Note - these validations can be disabled - see configurations page.

RR02

CdtTrfTxInf.Dbtr.PstlAdr - address must be either structured, hybrid or unstructured

CdtTrfTxInf+Dbtr++Id+++OrgId

Either 'AnyBIC', 'LEI' and/or one occurrence of 'Other' is allowed

FF01

One of:

  • OrganisationIdentification is present but no subfields (AnyBIC, LEI, Other) are populated in CdtTrfTxInf.Dbtr.Id.OrgId

  • Only one occurrence of Other is allowed in CdtTrfTxInf.Dbtr.Id.OrgId

CdtTrfTxInf+Dbtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.Dbtr.Id.PrvtId

CdtTrfTxInf+CdtrAgt++FinInstnId+++BICFI

Validated against IPF configuration to ensure that this BIC corresponds to a BIC that this instance of IPF has responsibility for iberpay.rule.allowed-bics.cdtragt

RC01

BIC value not allowed

CdtTrfTxInf+Cdtr++PstlAdr

Addresses are classified according to the address fields populated as per the Postal Address Structural Validations

Note - these validations can be disabled - see configurations page.

RR03

CdtTrfTxInf.Cdtr.PstlAdr - address must be either structured, hybrid or unstructured

CdtTrfTxInf+Cdtr++Id+++OrgId

Either 'AnyBIC', 'LEI' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.Cdtr.Id.OrgId

CdtTrfTxInf+Cdtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.Cdtr.Id.PrvtId

CdtTrfTxInf+UltmtCdtr++Id+++OrgId

Either 'AnyBIC', 'LEI' or one occurrence of 'Other' is allowed.

FF01

Mutually exclusive fields populated in CdtTrfTxInf.UltmtCdtr.Id.OrgId

CdtTrfTxInf+UltmtCdtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed.

FF01

Mutually exclusive fields populated in CdtTrfTxInf.UltmtCdtr.Id.PrvtId

CdtTrfTxInf+RmtInf

Either Unstructured or Structured may be present. If both components are included, the message will be rejected during the validation process.

FF01

Mutually exclusive fields populated in CdtTrfTxInf.RmtInf

Outbound pacs.008

If any of the below validations fail then a Response is sent back to the client and an ERROR level SchemeRuleValidationFailed system event is raised. Both response and system event quote the Return Code.

Field

Validation Details

Return Code

System Event Description

All Fields

Checks if the message is valid against the Iberpay (SCT Inst) pacs.008 xsd

FF01

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08":CreDtTm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08":MsgId}' is expected.

GrpHdr+MsgId

Must be in required scheme format: AAA: Service identifier STI - Immediate Transfer XXXXXXXXXX : Type of message to be exchanged 00800108 - Immediate transfer order (this is the pacs.008 version being used) ZZZZZZZZZZZZZZZZZZZZZZZZ: Identifier for the submitting entity

IT29

Incorrect message identification

GrpHdr+NbOfTxs

Iberpay (SCT Inst) supports only one transaction per message. If this field is not 1, the message will be rejected.

IT03

Number of transactions must be equal to 1

GrpHdr+TtlIntrBkSttlmAmt

Must be equal to the value of the underlying transactions

FF01

Interbank Settlement Amount between group header and transaction do not match

GrpHdr+IntrBkSttlmDt

Must be within range of D-1 to D+1

IT06

Group Header Interbank Settlement Date is not in allowed range of D-1, D, D+1

CdtTrfTxInf+InstrId

Must be follow the required format for Iberpay (SCT Inst) transfers, the first 4 characters have to be CORE

IT16

The first four characters of InstrId must match one of the codes defined to identify the product type

CdtTrfTxInf+UltmtDbtr++Id+++OrgId

Either 'AnyBIC', 'LEI' and/or one occurrence of 'Other' is allowed

FF01

One of:

  • OrganisationIdentification is present but no subfields (AnyBIC, LEI, Other) are populated in CdtTrfTxInf.UltmtDbtr.Id.OrgId

  • Only one occurrence of Other is allowed in CdtTrfTxInf.UltmtDbtr.Id.OrgId

CdtTrfTxInf+UltmtDbtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.UltmtDbtr.Id.PrvtId

CdtTrfTxInf+Dbtr++PstlAdr+++Ctry

Debtor Postal address Country is mandatory if Debtor Agent and/or Creditor Agent are not in the EEA. Note - this validation can be disabled - see configurations page.

BE07

CdtTrfTxinf.Dbtr.PstlAdr.Ctry is mandatory if payment involves a non-EEA country or territory

CdtTrfTxInf+Dbtr++PstlAdr

Addresses are classified according to the address fields populated as per the Postal Address Structural Validations

Note - these validations can be disabled - see configurations page.

BE07

CdtTrfTxInf.Dbtr.PstlAdr - address must be either structured, hybrid or unstructured

CdtTrfTxInf+Dbtr++Id+++OrgId

Either 'AnyBIC', 'LEI' and/or one occurrence of 'Other' is allowed

FF01

One of:

  • OrganisationIdentification is present but no subfields (AnyBIC, LEI, Other) are populated in CdtTrfTxInf.Dbtr.Id.OrgId

  • Only one occurrence of Other is allowed in CdtTrfTxInf.Dbtr.Id.OrgId

CdtTrfTxInf+Dbtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.Dbtr.Id.PrvtId

CdtTrfTxInf+Cdtr++PstlAdr

Addresses are classified according to the address fields populated as per the Postal Address Structural Validations

Note - these validations can be disabled - see configurations page.

BE04

CdtTrfTxInf.Cdtr.PstlAdr - address must be either structured, hybrid or unstructured

CdtTrfTxInf+Cdtr++Id+++OrgId

Either 'AnyBIC', 'LEI' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.Cdtr.Id.OrgId

CdtTrfTxInf+Cdtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed

FF01

Mutually exclusive fields populated in CdtTrfTxInf.Cdtr.Id.PrvtId

CdtTrfTxInf+UltmtCdtr++Id+++OrgId

Either 'AnyBIC', 'LEI' or one occurrence of 'Other' is allowed.

FF01

Mutually exclusive fields populated in CdtTrfTxInf.UltmtCdtr.Id.OrgId

CdtTrfTxInf+UltmtCdtr++Id+++PrvtId

Either 'Date and Place of Birth' or one occurrence of 'Other' is allowed.

FF01

Mutually exclusive fields populated in CdtTrfTxInf.UltmtCdtr.Id.PrvtId

CdtTrfTxInf+IntrBkSttlmAmt

If amount limit validation is enabled iberpay.rule.amount-limit-enabled, amount should be less than the amount configured by property iberpay.rule.amount-limit-eur

AM02

Amount exceeds scheme limit

CdtTrfTxInf+DbtrAgt++FinInstnId+++BICFI

Validated against IPF configuration to ensure that this BIC corresponds to a BIC that this instance of IPF has responsibility for iberpay.rule.allowed-bics.dbtragt

RC01

BIC value not allowed

CdtTrfTxInf+RmtInf

Either Unstructured or Structured may be present. If both components are included, the message will be rejected during the validation process.

FF01

Mutually exclusive fields populated in CdtTrfTxInf.RmtInf

Inbound pacs.004

The following validations are performed on an Inbound pacs.004 from the the Scheme. Failures will result in a pacs.002 sent back to the scheme with the Return Code quoted below, and an ERROR level InboundMessageFailed system event to inform the Client.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) pacs.004 xsd

FF01

An error message from schema validation failure.

Example:

org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.004.001.09":CreDtTm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.004.001.09":MsgId}' is expected.

OrgnlGrpInf

'Original Group Information' must exist as a child underneath PmtRtr or TxInf, but not both or the message will be rejected.

FF01

One of:

  • Either PmtRtr.GrpHdr.OrgnlGrpInf or PmtRtr.TxInf.OrgnlGrpInf must be populated

  • Both PmtRtr.GrpHdr.OrgnlGrpInf and PmtRtr.TxInf.OrgnlGrpInf cannot be populated.OrgnlGrpInf must be populated

TxInf+RtrId

Technical Duplicate Check (same DbtrAgt and TxId)

AM05

Duplicate Transaction

Outbound pacs.004

If any of the below validations fail then a Response is sent back to the client and an ERROR level SchemeRuleValidationFailed system event is raised. Both response and system event quote the Return Code.

Field

Validation Details

Return Code

System Event Description

All Fields

Checks if the message is valid against the Iberpay (SCT Inst) pacs.004 xsd

FF01

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.004.001.09":CreDtTm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.004.001.09":MsgId}' is expected.

GrpHdr+MsgId

Must be in required scheme format: AAA: Service identifier STI - Immediate Transfer XXXXXXXXXX : Type of message to be exchanged 00400109 - Immediate transfer order (this is the pacs.004 version being used) ZZZZZZZZZZZZZZZZZZZZZZZZ: Identifier for the submitting entity

IT29

Incorrect message identification

GrpHdr+NbOfTxs

Iberpay (SCT Inst) supports only one transaction per message. If this field is not 1, the message will be rejected.

FF01

Number of transactions must be equal to 1

GrpHdr+TtlRtrdIntrBkSttlmAmt

Must be equal to the value of the underlying transactions

IT05

Interbank Returned Settlement Amount between Group Header and transaction do not match

GrpHdr+IntrBkSttlmDt

Must be within range of D-1 to D+1

IT06

Group Header Interbank Settlement Date is not in allowed range of D-1, D, D+1

TxInf+RtrdIntrBkSttlmAmt

RtrdIntrBkSttlmAmt plus ChrgsInf/Amt must be equal to OrgnlIntrBkSttlmAmt

IT17

The return amount plus charges amount must equal the original settlement amount

OrgnlGrpInf

'Original Group Information' must exist as a child underneath PmtRtr or TxInf, but not both or the message will be rejected.

FF01

One of:

  • Either PmtRtr.GrpHdr.OrgnlGrpInf or PmtRtr.TxInf.OrgnlGrpInf must be populated

  • Both PmtRtr.GrpHdr.OrgnlGrpInf and PmtRtr.TxInf.OrgnlGrpInf cannot be populated.OrgnlGrpInf must be populated

TxInf+RtrRsnInf

RtrRsnInf/Orgtr/Nm or RtrRsnInf/Orgtr/Id/OrgId/AnyBIC must be populated but BOTH cannot be populated

FF01

Originator AnyBIC (TxInf/RtrRsnInf/Orgtr/Id/OrgId/AnyBIC) and Originator Name (TxInf/RtrRsnInf/Orgtr/Nm) are mutually exclusive

Inbound pacs.002

A pacs.002 cannot be sent to scheme as the result of failed pacs.002 validation. In this situation an ERROR level InboundMessageFailed system event to inform the Client will be raised.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) pacs.002 xsd

Not Applicable

An error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":CreDtTm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":MsgId}' is expected.

OrgnlGrpInfAndSts+GrpSts

GrpSts must exist as a child underneath OrgnlGrpInfAndSts or alternatively TxSts must exist as a child underneath TxInfAndSts, but both should not be present

Not Applicable

One of:

  • Either FIToFIPmtStsRpt.OrgnlGrpInfAndSts.GrpSts or FIToFIPmtStsRpt.TxInfAndSts.TxSts must be populated

  • Both FIToFIPmtStsRpt.OrgnlGrpInfAndSts.GrpSts and FIToFIPmtStsRpt.TxInfAndSts.TxSts cannot be populated

OrgnlGrpInfAndSts+GrpSts

If GrpSts = ACCP then OrgnlGrpInfAndSts.StsRsnInf should NOT be populated

Not Applicable

Status reason Information can only be populated if GrpSts is Rejected

OrgnlGrpInfAndSts+GrpSts

If GrpSts = RJCT then OrgnlGrpInfAndSts.StsRsnInf should be populated

Not Applicable

Original Group Information and Status reason Information must be populated if GrpSts is Rejected

TxInfAndSts+TxSts

If TxSts = RJCT then TxInfAndSts.StsRsnInf should be populated

Not Applicable

Transaction Information and Status reason Information must be populated if TxSts is Rejected

When processing an incoming (from scheme) pacs.002 message which is in response to an outgoing (to scheme) pacs.008 message the only additional validation check performed is to check that the pacs.002 received correlates with an outbound pacs.008. If the pacs.008 cannot be located then a system event is raised to payment service stating an invalid pacs.002 was received.

Outbound pacs.002

If any of the below validations fail then a Response is sent back to the client and an ERROR level SchemeRuleValidationFailed system event is raised. Both response and system event quote the Return Code.

Field

Validation Details

Return Code

System Event Description

All Fields

Checks if the message is valid against the Iberpay (SCT Inst) pacs.002 xsd

FF01

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":LclInstrm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":SvcLvl}' is expected.

GrpHdr+MsgId

Must be in required scheme format: AAA: Service identifier STI - Immediate Transfer XXXXXXXXXX : Type of message to be exchanged 00200110 - Immediate transfer order (this is the pacs.002 version being used) ZZZZZZZZZZZZZZZZZZZZZZZZ: Identifier for the submitting entity

IT29

Incorrect message identification

OrgnlGrpInfAndSts+GrpSts

GrpSts must exist as a child underneath OrgnlGrpInfAndSts or alternatively TxSts must exist as a child underneath TxInfAndSts, but both should not be present

FF01

One of:

  • Either FIToFIPmtStsRpt.OrgnlGrpInfAndSts.GrpSts or FIToFIPmtStsRpt.TxInfAndSts.TxSts must be populated

  • Both FIToFIPmtStsRpt.OrgnlGrpInfAndSts.GrpSts and FIToFIPmtStsRpt.TxInfAndSts.TxSts cannot be populated

OrgnlGrpInfAndSts+GrpSts

If GrpSts = ACCP then OrgnlGrpInfAndSts.StsRsnInf should NOT be populated

FF01

Status reason Information can only be populated if GrpSts is Rejected

OrgnlGrpInfAndSts+GrpSts

If GrpSts = RJCT then OrgnlGrpInfAndSts.StsRsnInf should be populated

FF01

Original Group Information and Status reason Information must be populated if GrpSts is Rejected

OrgnlGrpInfAndSts+GrpSts

GrpSts has to be either ACCP or RJCT

FF01

Only ACCP or RJCT can be used in OrgnlGrpInfAndSts/GrpSts

TxInfAndSts+TxSts

If TxSts = RJCT then TxInfAndSts.StsRsnInf should be populated

FF01

Transaction Information and Status reason Information must be populated if TxSts is Rejected

TxInfAndSts+TxSts

TxSts can only be RJCT

FF01

Only RJCT can be used in TxInfAndSts/TxSts by Participants

Inbound pacs.028

The following validations are performed on an Inbound pacs.028 from the Scheme. Failures will result in an ERROR level InboundMessageFailed system event to inform the Client.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) pacs.028 xsd

Not Applicable

An error message from schema validation failure.

Example:

org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.028.001.03":CreDtTm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.028.001.03":MsgId}' is expected.

OrgnlGrpInf+OrgnlMsgNmId

Field must contain either pacs.008 or camt.056

Not Applicable

Not able to handle received payment status request for orgnlMsgNmId

Outbound pacs.028

If any of the below validations fail then a Response is sent back to the client and an ERROR level SchemeRuleValidationFailed system event is raised. Both response and system event quote the Return Code.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) pacs.028 xsd

FF01

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":LclInstrm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":SvcLvl}' is expected.

TxInf+AccptncDtTm

MUST be populated

FF01

FIToFIPmtStsReq.TxInf.AccptncDtTm is mandatory on a payment status request

Inbound camt.056

The following validations are performed on an Inbound camt.056 from the Scheme. Failures will result in an ERROR level InboundMessageFailed system event to inform the Client.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) camt.056 xsd

Not Applicable

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":LclInstrm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":SvcLvl}' is expected.

Outbound camt.056

If any of the below validations fail then a Response is sent back to the client and an ERROR level SchemeRuleValidationFailed system event is raised. Both response and system event quote the Return Code.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) camt.056 xsd

FF01

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":LclInstrm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":SvcLvl}' is expected.

Assgnmt/Id

Must be in required scheme format: AAA: Service identifier STI - Immediate Transfer XXXXXXXXXX : Type of message to be exchanged 05600108 - Immediate transfer order (this is the camt.056 version being used) ZZZZZZZZZZZZZZZZZZZZZZZZ: Identifier for the submitting entity

IT29

Incorrect message identification

UndrlygTxInf/CxlRsnInf/Rsn/Cd

Must be one of the below codes or the message will be rejected; * DUPL - Duplicate Payment * TECH - Technical problems have resulted in erroneous SCT Inst payment * FRAD - Fraudulent origin of the SCT Inst payment * CUST - Initiated by ordering customer * AM09 - Incorrect amount * AC03 - Incorrect IBAN

FF01

Invalid Cancellation Reason Code in Undrlyg/TxInf/CxlRsnInf/Rsn/Cd

UndrlygTxInf/CxlRsnInf/Orgtr/Nm

Must be populated if CxlRsnInf/Rsn/Cd is either CUST, AM09 or AC03

FF01

Originator Name (Undrlyg/TxInf/CxlRsnInf/Orgtr/Nm) must be provided when Cancellation Reason Code (Undrlyg/TxInf/CxlRsnInf/Rsn/Cd) is CUST, AM09 or AC03

UndrlygTxInf/CxlRsnInf/Orgtr/Id/OrgId/AnyBIC

Must be populated if CxlRsnInf/Rsn/Cd is either FRAD, TECH or TECH

FF01

Originator AnyBIC (Undrlyg/TxInf/CxlRsnInf/Orgtr/Id/OrgId/AnyBIC) must be provided when Cancellation Reason Code (Undrlyg/TxInf/CxlRsnInf/Rsn/Cd) is FRAD, DUPL or TECH

UndrlygTxInf/CxlRsnInf/AddtlInf

Can only be populated if CxlRsnInf/Rsn/Cd is either FRAD, CUST, AM09 or AC03

FF01

Additional Info (Undrlyg/TxInf/CxlRsnInf/AddtlInf) is only allowed when Cancellation Reason Code (Undrlyg/TxInf/CxlRsnInf/Cd) is FRAD, CUST, AM09 or AC03

Inbound camt.029

The following validations are performed on an Inbound camt.029 from the Scheme. Failures will result in an ERROR level InboundMessageFailed system event to inform the Client.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) camt.029 xsd

Not Applicable

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":LclInstrm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":SvcLvl}' is expected.

Outbound camt.029

If any of the below validations fail then a Response is sent back to the client and an ERROR level SchemeRuleValidationFailed system event is raised. Both response and system event quote the Return Code.

Field

Validation Details

Return Code

System Event Description

All Fields

Checked to make sure the message is valid against the Iberpay (SCT Inst) camt.029 xsd

FF01

An error starting with the prefixed text 'XSD Schema Validation failure -' followed by an error message from schema validation failure.

Example:

XSD Schema Validation failure - cvc-complex-type.2.4.a: Invalid content was found starting with element '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":LclInstrm}'. One of '{"urn:iso:std:iso:20022:tech:xsd:pacs.002.001.10":SvcLvl}' is expected.

Assgnmt/Id

Must be in required scheme format: AAA: Service identifier STI - Immediate Transfer XXXXXXXXXX : Type of message to be exchanged 02900109 - Immediate transfer order (this is the camt.029 version being used) ZZZZZZZZZZZZZZZZZZZZZZZZ: Identifier for the submitting entity

IT29

Incorrect message identification

CxlDtls/TxInfAndSts/CxlStsRsnInf/Orgtr

Either CxlDtls/TxInfAndSts/CxlStsRsnInf/Orgtr/Nm or CxlDtls/TxInfAndSts/CxlStsRsnInf/Orgtr/Id/OrgId/AnyBIC must be populated but BOTH cannot be populated

FF01

Originator AnyBIC (Undrlyg/TxInf/CxlRsnInf/Orgtr/Id/OrgId/AnyBIC) and Originator Name (Undrlyg/TxInf/CxlRsnInf/Orgtr/Nm) are mutually exclusive

CxlDtls/TxInfAndSts/CxlStsRsnInf/Rsn/Cd

Must be one of the below codes or the message will be rejected; * AC04 - Account closed * AM04 - Insufficient funds in the account * NOAS - No response from beneficiary * NOOR - The original immediate transfer was never received * ARDT - The immediate transfer has already been returned * CUST - Refused by customer * LEGL - Refusal for legal reasons

FF01

Invalid Cancellation Reason Code in CxlDtls/TxInfAndSts/CxlStsRsnInf/Rsn/Cd

Postal Address Structural Validations

Address Line Populated Town Name Populated Country Populated Any Other Address Fields Populated Classification

No

Yes

Yes

–

Structured

Yes

No

Yes

No

Unstructured

Yes

No

No

No

Unstructured

Yes

Yes

Yes

–

Hybrid

If configured, transactions that cannot be classified as one of the above address types will result in a validation failure