Skip to main content

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

Connecting to systems of record

Updated on June 22, 2022

The Payment Exception Resolution application comes with several Data Pages rules that are in simulation mode. Copy each data page rule into your implementation layer (ruleset) and update the data source information for each appropriate system of record.

Pega Foundation for Financial Services

The following table lists the data page rules and its purpose in the Payment Exception Recovery application.

Data Page rules

Data Page nameLookup classPurpose
D_GetAccountDetailsPFSA-PER-Data-AccountRetrieve account details
D_GetAccountsListPFSA-PER-Data-AccountAccount search results
D_FetchDepositAcctLinkedToCardPegaFS-Data-AcctCardXrefRetrieve account linked to a card
D_GetTransactionListPFSA-PER-Data-TransactionTransaction search results
D_TransactionPFSA-PER-Data-TransactionRetrieve transaction details
D_GetCreditedTransactionsPFSA-PER-Data-TransactionRetrieve credited transactions for an account
D_GetDuplicateTransListPFSA-PER-Data-TransactionRetrieve duplicate deposit transactions
D_GetDepositTranSummaryPegaFS-Data-Transaction-DepositRetrieve deposit transactions
D_CCTranSummaryPegaFS-Data-Transaction-CardCredit card transaction search
D_PayorPFSA-PER-Data-Party-PayorRetrieve payor (customer) details
D_PayorBankPFSA-PER-Data-Party-PayorBankRetrieve payor’s bank details
  1. In the header of Dev Studio, search and select the data page rule. For example, D_GetAccountDetails.
  2. Save the data page rule into your implementation layer ruleset.
  3. Configure the data source using the source deemed appropriate for the SOR.
  4. Perform steps 1-3 for the other data page rules listed in the table above.

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