Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Parsing receiver - transaction references

Updated on March 4, 2022

The receiver’s transaction reference is usually in a known format. It may contain embedded dates, often in a Julian date format, with a few characters that represent a product code and a sequence number of some kind. The PegaSI_Sample RuleSet provides a sample Transaction Reference pattern that can be cloned and modified as needed.

Pega Smart Investigate for Payments Implementation Guide


The parser recognizes inquiry references in the format BBBYYJJJPP-99999, where:

  • BBB is a known branch number, such as LON, PAR, NYK, FFT, COP, HEL, or SYD
  • YY is a year from 1995 onwards
  • JJJ is a Julian date from 001 to 366
  • PP is a known product code, such as AA, BB, CC, DD, EE, FF, GG
  • - is a literal dash
  • 99999 is a 5-digit sequence number

The parser checks for cases where the sequence number contains “O” rather than zeros, where the sequence number is missing lead zeros, and where the “-” is missing or replaced by a “/” or “.” or “_”.

Manipulate/Translate Step

The output of the TRANSLATE step ensures that the value is a correctly formatted case ID.

Validate Step

May reference a WHEN block.

Map/Output Step

If the Test/Validate step returns TRUE, or no test/validate step is used and data has been successfully located, the output is saved as a property.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us