Skip to content

Use case

KYC and AML screening for fintech and payments

A fintech or payments firm can screen every new customer with one API call. AdverseMe checks sanctions, PEP status, adverse media and ownership across 110+ sources, returns a score from 4 independent AI judges that is reproducible for 14 days, and returns the result through a polling API. Every search stays on the record.

Start a screening
POST /screen
Auth
X-API-Key header
Result
Poll GET /screening/{id}
Score
Reproducible 14 days

The workflow, in plain language

Onboarding is the first screening. The book you already have is the bigger one.

  1. 1

    Onboarding

    Screen the applicant and, for a business account, its directors and owners before the account is opened. A clean result lets the flow continue; a hit routes to a reviewer.

  2. 2

    Periodic review

    Customers already on the books need re-screening on a schedule, and immediately when a sanctions list changes.

  3. 3

    Merchant and counterparty checks

    Payment processors screen merchants and their beneficial owners, where a hidden owner is the risk rather than the named signatory.

  4. 4

    The audit question

    When a regulator or partner bank asks what you checked and why you decided as you did, the answer has to be on file, per customer.

How AdverseMe fits

Screening as an API call, with the working kept

One call, every source

POST /screen with an X-API-Key starts a person or company screening across 110+ sources, including 13 official sanctions feeds snapshotted twice a day. Poll GET /screening/{id} until the status is completed.

API reference →

A score with reviewable evidence

4 judges from 4 model families score blind. The median is the score and dissent is counted. Matching evidence signatures can reuse a cached verdict for 14 days when the subject, source versions and methodology remain unchanged.

Methodology →

Ownership without a second vendor

Company screenings trace officers, parents and beneficial owners to depth 6 with GLEIF LEI and SEC 13D and 13G edges. The OFAC 50 percent rule is computed for you.

Ownership graph →

Delta re-screening for the whole book

Put customers on a daily, weekly, monthly monitor. Light delta checks against changed list versions are free; only a confirmed hit triggers a full re-screen and uses 1 credit.

Monitoring →

Evidence per customer

GET /screening/{id}/pdf returns the branded report with findings, sources, coverage, exclusions and limitations. Per-judge reasoning is available in the app. Attach it to the customer record and it is there when someone asks.

Engine Trace →

Migrate the back book

Upload the existing customer list as a CSV, watch it screen with live progress, and escalate hits to cases for review.

Batch screening →

What a call looks like

POST /screen
X-API-Key: your_key

{
  "entity_type": "person",
  "name": "Jonathan A. Doe",
  "country": "GB"
}

201 Created
{ "screening_id": "...", "status": "queued" }

GET /screening/{id}
GET /screening/{id}/pdf
GET /credits

Field names are illustrative; the API page has the exact request and response shapes. Plans from $49 a month on the pricing page.

Frequently asked questions

How do I integrate AdverseMe into an onboarding flow?

Create an API key in the app, then POST /screen with the X-API-Key header and the person or company details, against the base URL adverseme.com/api/public-api. Poll GET /screening/{id} until the result is completed. GET /credits tells you how many screenings remain.

How should an onboarding flow use the score?

Use the score alongside identity checks, source evidence, coverage limitations and your own review rules. Matching evidence signatures can reuse a verdict for 14 days; a changed input can change the result. A low score is not a guarantee that a customer should be approved.

Does the API cost more than the app?

No. An API screening uses the same 1 credit as a screening started in the app. Fetching results, PDFs or your balance over the API does not use credits.

Where is customer data processed?

The platform uses Microsoft Azure in Western Europe. Review the privacy policy and sub-processor list for processing details, and use the audit log to review recorded account activity.

Put screening in the onboarding flow this week.

Plans start at $49 a month for 50 screenings. Every plan includes the AI council, ownership graph, Engine Trace and PDF reports.