3.1.1 Input Preparation/Using the Individual Services/Output Capture

The JSON inputs required for verification differ based on Customer type, jurisdiction, data sources, and external vendors. The JSON input preparation for each service is made configurable, transparent, and flexible by the Table to JSON Utility. The output differs based on the above attributes. The KYC system uses the output for risk scoring and is used for audit purposes. The JSON to Table Utility allows you to transform the JSON output into a table structure.

For information on configuring the utility, see Oracle Financial Services Know Your Customer Utilities Guide.

The PMF workflow can be used to include the input, execution, and output-related sub-tasks in one process, which can be configured using the PMF User Interface. In PMF, these are termed as Pre Rule, Execution Rule, and Post Rule.

The Pre Rule is used to define what data to pick for the input of each individual sub-process. The Pre Rule is a URL of the Table to JSON utility for a specific mapping created to generate the JSON.

For information on the Pre Rule mapping IDs, see Oracle Financial Services Know Your Customer Utilities Guide.

The Execution Rule contains a placeholder for the Pre Rule URL to perform the task. For example, in Customer Screening, the Execution Rule is the URL of the OFS CS real-time screening URL.

For information on the URL formats used to invoke the service, see invoking-kyc-onboarding-service.html#GUID-E5AA402C-980E-4173-B921-C8447023DD62.

The Post Rule defines where the output data must be captured in the OFS KYC system. This is the JSON to Table URL for a specific mapping created to copy the output data into the KYC tables.