Skip to main content

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

Reason and sub-reason codes

Updated on June 22, 2022

In this new questionnaire class, the pattern is to create a section for each reason code or sub-reason code combination. You need to copy Customer Interview section from the payment exception case type into your new case type. You also need to include your custom sections for each reason code or sub-reason code combination.

Pega Foundation for Financial Services

To configure new dispute reason and sub-reason codes, you must add records to the dispute reason matrix table. To add codes to support your new payment case type, complete the following steps:

  1. Log in to App Studio and select Data from the navigation menu.
  2. From the Data objects and integration landing page, select DisputeResonMatrix.
  3. Click the Records tab.
  4. Click Add record at the bottom of the table.
  5. In the new row add the following data:
    • Network name should match the name of your payment type.
    • Source should be Customer (Sample is reserved).
    • Optionally provide a dispute category to group a subset of reason/sub-reason codes.
    • Provide a dispute reason code.
    • Provide a dispute reason description (displayed to end user).
    • Optional: Provide a dispute sub-reason code.
    • Optional: Provide a sub-reason code description (displayed to end user).
    • Provide the name of the UI section that supports this reason/sub-reason code combination.
    • Optional: Provide the name of a Flow rule to execute post the Customer Interview step to support the specific reason/sub-reason code combination.
    • Provide an effective date for this reason/sub-reason code combination.
    • Provide an expiration date for this reason/sub-reason code combination.
  6. Tab out of the new row to save the record.

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