Skip to main content

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

Customer information file interface

Updated on March 4, 2022

As delivered, Smart Investigate for Payments provides a relational database table, PCB_Accounts, to store customer information data together with the SQL to query the data. This database may be used in production as is, in which case it would be necessary to create a feed process that updates the table periodically with new, updated, and deleted records. There is also a customer information record maintenance function available with Smart Investigate for Payments to enable the data to be maintained manually rather than wait for updates to arrive from the primary CIF application.

If you prefer to use an existing CIF, Smart Investigate for Payments provides placeholder activities that can be copied and modified to enable the lookup and retrieval of customer account information from your centralized customer information database files. Based on the entry of a customer’s account number and account type, the lookup validates and returns a customer’s account name, account address, contact, and preference information. When retrieved, this information is placed on the clipboard and subsequently mapped into a customer party in a Smart Investigate for Payments case.

To create your CIF interface, select your connectivity method and determine your field mapping between the data source and Smart Investigate for Payments. Then, create and modify versions of the following activities to map and validate the data:

  • PegaSI-Party Lookup —This activity looks up the customer account information in the database and sets the properties on the clipboard.
  • PegaSI-Party Validate —This activity validates the customer’s account number and account type on entry.
Pega Smart Investigate for Payments Implementation Guide

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