What's included
The version number of the Payment Exception Recovery application is PFSAPER:8. The application is built on the Pega Foundation for Financial Services(PFFS) as well as the Pega Infinity Platform version 8.7.
Rulesets
The Payment Exception Recovery application consists of the following rulesets:
- PSFAPER – Core rules for the Payment Exception and Recovery application.
- PSFAPERInt – Integration ruleset for integrating with other systems.
- PFSA – Organizational level ruleset for organizational rules.
- PFSAInt - Organizational level integration ruleset for integrating with other systems.
Case types
The Payment Exception Recovery application contains an implementation layer. However, clients need to run the new application wizard to create their own implementation. The following two case types are included:
Case Type
| Case type | Description |
| Claim | Used for intake of new payment disputes and is linked to all disputed transactions. |
| Payment exception | Manages the lifecycle of a single disputed transaction. This is a model case type that can be used as is to provide a generic dispute process or it can be specialized into payment specific case types. |
Data model
The Payment Exception Recovery application contains the following data objects.
Data Model
| Data type | Description |
| Account | Customer account attributes |
| Accounting entry | Attributes for a single accounting entry |
| App Extension | Application attributes requiring custom values when extending the application. For more information, see Next Steps. |
| Dispute reason matrix | Storage for dispute reason metadata |
| Party | Attributes for a party to a dispute |
| QnA | Container for questions/answers related to dispute reasons |
| Supplemental information | Container for capturing supplemental information |
| Transaction | Payment transaction attributes |
| Validations | Container for validations that determine probable dispute success. |
Dispute reason matrix
The Dispute Reason Matrix stores the possible dispute/fraud reason codes by payment type. Sample reason codes are provided but each implementation must provide its own reason codes.
QnA (Questionnaire)
The QnA or Questionnaire class is the source for questions that support the Customer Interview step in the Payment Exception case type. Sample questions are provided as an example for implementation.
Supplemental information
The Supplemental Information is the source for questions that support the Supplemental Information step in the Claim case type. Sample questions are provided as an example for implementation.
Validations
Validations stores the link to the rule to execute for a particular validation scenario. These validations are used to determine the viability of a dispute prior to submission for processing. Sample validations are provided for the Payment Exception case type.
Work queues and work groups
The following table lists the main work queue and their associated work group.
Work Queue and Work Group
| Work Queue | Work Group |
| PER_Exception | default@PFSA |
| PER_Fraud | default@PFSA |
Access groups and portals
The core System Administrator account for the Payment Exception Recovery application is PERSysAministrator. To use this account, enable the Operator ID and change the password.
Portals
The following are the end user portals and the access groups that utilize them.
Portals
| Portal | Access group |
| Developer | PFSAPER:Admin |
| Case Worker | PFSAPER:BackOfficeUser |
| Case Worker | PFSAPER:FrontOfficeUser |
| Case Manager | PFSAPER:Manager |
Personas
The Payment Exception Recovery application contains the following example personas, listed with their corresponding Access Group and Channels.
Persona
| Persona name | Access group | Channels |
| Back-office user | PFSAPER:BackOfficeUser | Case worker portal |
| Front-office user | PFSAPER:FrontOfficeUser | Case worker portal |
| Manager | PFSAPER:Manager | Case manager portal |
Previous topic Payment Exception Recovery Implementation Guide Next topic Extending the application