Extending to other payment types

The SDAA application contains an implementation layer. However, clients must run the New Application wizard to create their own implementation.

SDAA contains the following Case Types:

Initiate dispute: Used for initiating disputes and is linked to all disputed transactions.

Dispute: Manages the lifecycle for disputed transactions. This is a model Case Type that you can use as it is to provide a generic dispute process, or that you can specialize into payment-specific Case Types.

SDAA application provides a model dispute (payment exception) Case Type that is meant to be extended to support new payment types and their specific processing needs.

Below are the high-level steps for adding a new payment Case type:

1. In App Studio, in the navigation menu, click Case types.
2. On the Case types landing page, click New.
3. In the dialog box:
   1. Enter a name for your Case Type.
   2. Expand the Advanced section.
   3. Reuse assets from Payment Exception.
   4. Check the Reuse Case life cycle.
   5. Click Next.
4. The process creates the Case Type and opens your new Case Type.

The following figure shows the Create Case Type view:

To support your new Case type, you need to define it as a valid payment network type in the D_ApplicationSettings application extension data page rule. The following steps are required.

1. In the PegaFSPE-Data-AppExtension class, create a new property to store the value of the payment network. For example, to add Venmo as a payment type, the pattern for the property name is <CaseType>PaymentNetwork (VenmoPaymentNetwork) and must be of theText type.
2. Save a copy of PegaFSPE-Data-AppExtension.GeneralSettings_PE data transform Rule into your implementation Ruleset.
3. Update GeneralSettings_PE to set the value of your payment network property created in step 1 to a text identifier to represent the new Case type (Venmo).
4. Save the Rule.

The following figure shows General settings for payment exception application Data Transform:

To instantiate your new Case type, you must define it as a valid work class in the D_ApplicationSettings application extension Data Page Rule. The following steps are required.

1. In the PegaFSPE-Data-AppExtension class, create a new property to store the value of the work class. The property name must be of type text.
2. Save a copy of PegaFSPE-Data-AppExtension.ClassSettings_PE Data Transform Rule into your implementation rule set.
3. Update ClassSettings_PE to set the value of your work class property created in step 1 to a class of the new Case type.
4. Save the Rule.

The following figure shows Class settings for the payment exception Data Transform:

To enable instantiation of your new Case Type, you must update Common-LDM-Entity-Transaction.EvaluateTransactionNetwork decision table Rule. This Rule uses inputs from the transaction information to determine which dispute Case Type to invoke. To extend this Rule, you must save it into your implementation rule set. This rule is invoked during the transaction search at which time it sets a property on the results of which payment network the transaction should be attributed.

This rule references the new dispute work class field previously added to the D_ApplicationSettings in the Return column.

The following figure shows the Evaluate transaction network decision table:

If you want to create a new claim type similar to the dispute type, update the EvaluateClaimProcessingClass decision table.

The following figure shows the Evaluate claim processing class decision table: