Skip to main content

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

Configuring KYC Types and Items

Updated on November 5, 2021

A class hierarchy has been created to organize and store instances of KYC Type rules. The class hierarchy is organized by global regions and regulations and it has a corresponding set of rulesets that follows the same structure. In addition to the class hierarchy shipped with the application, there are pre-configured due diligence rules that can serve as a design model or as reusable assets in production implementations.

The use of class structures to organize KYC Type rules is intended to facilitate configuration and maintenance updates while allowing clients to logically separate their due diligence rules. Specialized class hierarchies should be constructed to store the client's specialized due diligence rules. The client's specialized classes can be configured to inherit from the PegaKYC-Data-Type-Policies- classes to promote reuse.

Important: Upon implementation of a specialized KYC application, specialized KYC Types must be created in new, specialized data classes unique to the organization's KYC requirements and architecture. Careful design and planning of the class structure is required to promote reuse for faster implementation and easy maintenance of KYC Types. It is recommended that you use Pega Know Your Customer Regulatory Compliance, which contains KYC types, for certain jurisdictions and regulations. It also contains a rich class structure which can be easily extended to customize and facilitate your implementation.
Note: No matter how data classes are named or structured, the data classes must inherit from the PegaKYC-Data-Type- class to reuse the core processing assets of the KYC application.
What to do next: Follow the following steps to configure KYC Types and Items:

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