Skip to content
  • There are no suggestions because the search field is empty.

Using webhooks to stay up to date with PEP information

The PEP Webhook sends three types of events (ADD, UPDATE, and DELETE) to keep your customer database automatically updated.

1. Getting Started

To ensure a smooth setup and continuous synchronization, follow these steps in order:

  1. Build the Webhook Integration & Fast Storage Subscribe to PEP events and set up a fast-lookup storage for your customer data. For each customer, store: personal identity number (for Swedish citizens), first name, last name, date of birth, and the unique personId (PEPid) received from our service.
  2. Integrate into Onboarding Add the PEP lookup check into your customer onboarding workflow.
  3. Perform an Initial Database Cleanup Run your existing customer database against the PEP service. Save all PEP information and map the corresponding personId in your fast storage for every match.
  4. All Set! Your automatic PEP update pipeline is now fully operational.

2. Event Types

  • ADD: Triggered when a new person becomes a PEP. Match the data in the keyMap field against your customer database.
    • Unique Identifiers (e.g., Swedish Personal Identity Numbers): Matched directly.
    • Names Only: Save the PEP data and flag for manual review if a name match occurs.
  • UPDATE: Triggered when details change (e.g., name or role change). If the individual exists in your fast storage database, update their details; otherwise, you can ignore the event.
    • Note: When a PEP assignment ends, you will receive an UPDATE event with PEP status set to "inactive" (rather than a DELETE event).
  • DELETE: Triggered when a person is completely removed from the PEP register. Match the personId in keyMap and remove the PEP status from that customer.