Introduction
The Screening Data Contract establishes the framework for secure and efficient compliance screening of ISO20022 payment messages between the PSP System and the Screening Engine. It defines the responsibilities of both parties, the data exchanged, and the outcomes of the screening process.
The PSP System sends payment messages (pacs.004, pacs.008, pacs.009) to the Screening Engine, along with a Correlation ID (UUID v7) and Contract Version for uniqueness and version control. The Screening Engine processes these messages and provides screening outcomes, such as no_hit, hit, cleared, blocked, embargoed, or rejected, in a separate header. The outcomes guide the PSP System’s actions, with no reliance on status codes in the pacs.002 message.
The Screening Engine fully controls transactions flagged as "hit" and provides further updates (e.g., cleared, blocked) after manual review. The PSP System awaits final decisions before proceeding. This contract mandates compliance with ISO20022 standards, proper message structure, and data security through mTLS encryption. All supplementary data is treated as unstructured, and the PSP System is not responsible for interpretation. The data exchange ensures clarity, accountability, and compliance with regulatory requirements, safeguarding financial transactions.
To access this content please contact your client service team