Use case

Sanctions screening and VPN detection for banks

For a bank, sanctions screening is checking customers, counterparties and online-banking sessions against the sanctions lists before an account opens, a payment leaves or a login from a sanctioned jurisdiction goes through. CompliAPI runs each of those checks as one API request and names the list behind every match.

Banks and other financial institutions screen at three points: who the customer is, who the payment goes to, and where the online-banking session comes from. CompliAPI covers each with a separate endpoint. Name screening fuzzy-matches a person or company against the primary names and aliases on the OFAC SDN and Consolidated lists and the UN, EU, UK, Swiss, Canadian, Australian, New Zealand, French and Japanese sanctions lists, and returns a 0-100 score with the reasons for each candidate. Identifier screening checks a passport or registration number, an email, a website, a vessel's IMO number or a crypto wallet address for an exact appearance on the same lists.

OFAC VPN detection for banks is two calls on the session's IP address. The geolocation endpoint returns the country, region and city with a flag that is true when the country carries an OFAC country designation. The VPN endpoint returns one signal, vpn: true, false or "unknown", so a session that looks domestic but arrives through a VPN can be stepped up or held instead of trusted. The signal says a VPN is in use; it does not say where the customer really is, and it does not cover proxies, Tor or datacenter ranges as separate categories.

Each request is logged to your organization's audit trail with your own reference for the customer or payment, and every response reports when each list was last refreshed. The OFAC lists are checked for a new Treasury publication every 15 minutes; the other sanctions lists refresh daily. There is one API for every customer: the same endpoints, lists and limits on the free tier and the paid plans.

Where CompliAPI fits

Customer and counterparty names

Screen a name at onboarding and before a payment is released. A date of birth and a country narrow the candidates, each match carries a score and the list it came from, and US export-control and FinCEN special-measures hits are flagged without being reported as sanctioned.

Sanctions screening API — every list, one GET request →

Online-banking sessions

Geolocate the session IP, read the sanctioned-country flag, and use the VPN signal to decide how far to trust the location. Log all three with the decision you took.

VPN Detection API for OFAC & Sanctions Screening →

Changes after onboarding

Register stored identifiers for monitoring on a paid plan and receive a webhook or an email when one is listed, delisted or relisted, within a few minutes of the list change being ingested. Re-screen a customer book in batches of up to 50 subjects per request.

Sanctions list monitoring with signed webhooks and email alerts →

Evidence for the examiner

Every match links the official source record, every response states the version of each list it was checked against, and every call appears in the dashboard's request log under the reference you sent.

OFAC API — screen against the official SDN and Consolidated lists →

Scope

CompliAPI is list screening and session signals. It is not KYC or identity verification, adverse-media screening, transaction monitoring, case management or a core-banking integration, and monitoring covers exact identifiers, not names. It has no contractual uptime commitment on self-serve plans and holds no SOC 2 report; the Trust page lists what is and is not in place. A bank will run it as one control inside a program its compliance team designs.

Frequently asked questions

Can a bank use CompliAPI as its only sanctions screening system?

That is a decision for the bank's compliance function, and for most banks the answer is no. CompliAPI checks names and identifiers against the lists and returns the evidence; it has no alert queue, no case management, no payment-message parsing and no transaction monitoring. Teams use it where a direct API check fits: a digital onboarding flow, a new product line, a crypto or payouts feature, or a second check beside an existing vendor.

How does name screening handle false positives?

Each candidate comes back with a score from 0 to 100 and the reasons behind it, so your own threshold decides what reaches a reviewer. Passing a date of birth, a country or an ID number sharpens the result: the comparison ranks the candidates and is explained in each match's reasons. Aliases a list itself marks as low quality are reported but never matched on.

Does a VPN signal mean the customer is in a sanctioned country?

No. It means the IP address belongs to a known VPN service, so the location you see is the VPN exit, not the customer. Most VPN users are ordinary customers. Banks typically treat a true or "unknown" result as a reason for step-up verification or a review, and block only on the sanctioned-country flag itself.

How current are the sanctions lists a bank is screened against?

The OFAC SDN and Consolidated lists are checked for a new Treasury publication every 15 minutes and ingested when one appears. The UN, EU, UK, Swiss, Canadian, Australian, New Zealand, French and Japanese lists refresh daily. Every screening response carries list_versions: the last refresh time of each list checked and, for the OFAC lists, Treasury's publication id.

Can we screen our existing customer base, not just new customers?

Yes. The batch endpoint screens up to 50 subjects of mixed types in one request, each with your own reference, and each item counts as one request against the monthly quota. For identifiers you hold on file, monitoring on a paid plan alerts you when a list changes instead of waiting for the next re-screen.

Does CompliAPI screen for politically exposed persons?

There is a separate endpoint that checks a person's name against the OpenSanctions politically-exposed-persons dataset and returns scored candidates. It is a name check only. It does not verify identity, collect documents or assess source of wealth, so it supports a due-diligence process and does not replace one.

The solutions behind this use case

From the blog: Real-Time vs Batch Sanctions Screening →

Try it on your own data

Get a free API key, 100 requests a month with no credit card, and screen a name or a session IP in minutes.

Free tier: 100 requests a month. No credit card required.