Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Validation issue on Field 72 in 202 MT message



Validation issue on Field 72 in 202 MT message. The CSR is able to pass SWIFT non-compliant data for field 72 for correspondence 202.

Steps to Reproduce

Enter XXXXX in field 72 without the required key word as a prefix.Even then validation is working.

Root Cause

 Validation of Field 72 is not updated which causes the issue.


Hfix-21264 has been created to address the issue.
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us