Gravity Forms
+ Sanctions & PEP Screening

The Gravity Forms Sanctions & PEP Screening add-on checks the people and companies who submit your forms against global sanctions, politically-exposed-person (PEP) and watchlist data — before you onboard them, pay them or ship to them. You map the name field, choose which lists to screen, set how close a match must be to count, and decide what a possible match should do. Everything the add-on finds is written to the entry as a clear, auditable record.

It is built for the forms that carry a compliance duty: account and membership applications, vendor and supplier onboarding, high-value orders, donations and grants, partner and reseller sign-ups, and any know-your-customer or anti-money-laundering step that runs through a form. For a person you can also map a country and a date of birth to sharpen the match; for a company you screen the organisation name. You pick the datasets — sanctions lists, PEPs, and crime / law-enforcement sources — and the match threshold, so you control how strict the screen is.

A possible match can do one of three things, your choice per form: flag the entry so it is accepted but marked for attention, route it to a reviewer by email so someone checks it before you act, or block the submission outright. The block is enforced on the server when the form is submitted, so a visitor cannot get a blocked submission through by tampering with the browser. Either way, the add-on stores a screening record on every entry — the match score, the categories found, the top hit, the outcome and the threshold that was enforced — and writes a short note on the entry so the result is visible at a glance. It is self-serve: you connect your own screening provider account (the open OpenSanctions API, or your own self-hosted instance), and the only thing sent out is the name you asked to screen, with any country or date of birth you mapped.

When a form with screening on is submitted, the add-on reads the name you mapped (joining the parts of a Name field) and, if you mapped them, the country and date of birth. It asks your screening provider to match that entity against the datasets you chose, reads the candidates back with their scores, and keeps only those at or above your threshold. If the top candidate reaches the threshold the submission counts as a possible match; otherwise it is cleared. When the action is “block”, a match fails validation on the server and the submission is refused with your message on the name field — this runs on submit, so it holds even if the browser is tampered with. When the action is “flag” or “route”, the submission is accepted; “route” also emails a review notice to the reviewer you set. In every case the add-on writes a screening record to the entry (score, categories, top hit, outcome and threshold) and adds a short note. The only outbound request is to the screening endpoint you configured, carrying just the name and any country or date of birth you mapped.