Product

Transaction Screening

Sanctions, PEP and adverse-media screening, orchestrated into a single real-time compliance decision — with every match and its evidence written to an immutable audit trail.

The problem

Unorchestrated screening is screening you can't defend

Most fintechs bolt screening on as a separate check. The result is coverage gaps no one can prove are closed: some transfers get screened, some don't, and when a sponsor bank or regulator asks for evidence that screening was applied consistently, the answer lives across vendor dashboards, spreadsheets and developer logs. Screening that isn't orchestrated into the decision — and isn't evidenced — is screening you can't defend.

How it works

Screening as an orchestrated layer inside the decision

Fintegrity treats screening as an orchestrated layer inside the decision, not a side call. When a transaction or onboarding event hits the Decision API, Fintegrity routes the relevant parties through your configured screening provider, interprets the result against your policy, and folds it into a single decision. Every check writes its evidence to the immutable audit ledger.

Orchestrated into the decision.

Screening is one input to a deterministic decision, not a separate workflow your team has to reconcile.

Bring your own provider.

Connect ComplyAdvantage, LSEG World-Check, or another provider with your own credentials — or use a bundled option. No vendor lock-in; you keep your data relationship and your pricing.

At least two screening connectors can stay active so a provider change or outage never leaves you uncovered.

Evidence by default.

Each screening result is captured as defensible evidence, so "was screening applied to this transfer?" is answered in seconds, not days.

Evidence by default

What gets captured per check

For every screening check, Fintegrity records the following fields as an append-only entry on the audit ledger. The record is exportable as part of any evidence pack.

  • List / provider name and its version at time of check

  • Timestamp of the check (server-side, immutable)

  • Match score returned by the provider

  • Matched entity detail (name, list, category)

  • Action your policy took as a result

Every record is append-only and cannot be altered after writing. Evidence packs for any transaction or onboarding event are generated on demand.

See how Fintegrity evaluates transactions in real time

We'll walk through a live screening configuration using transaction patterns from your business — orchestrated into the decision, evidence written by default.