Best Sanctions Screening APIs for Money Transmitters (2026)

Last Updated: September 4, 2026

We compared 8 sanctions screening APIs against 8 transaction-level requirements for money transmitters, including real-time responses, false-positive control, and auditable screening records. Screening both sides of every transfer means a 5,000-screening plan covers 2,500 transactions, so the pricing model matters as much as features. Prices as of September 2026, based on public vendor pages.

What Money Transmitters Need From a Screening API

A money transmitter needs a screening API that runs sender and recipient checks inside the transaction flow, often with only a name and country for the recipient, without blocking legitimate payments. Most sanctions screening tools instead target customer onboarding: batch jobs, manual review queues, and periodic re-screening.

1. Real-Time Response

Screening runs inside the transmitter’s live flows: sender and recipient checks at transaction time, and again before payout release. The API must return a result in under 1 second, so the transfer can be approved or blocked within the same request. If screening runs only as an overnight batch job, a listed person can send or receive money before the batch flags them.

2. False Positive Control at Scale

Transaction volumes run to thousands of counterparties a month, and common names match sanctioned individuals on name alone. Without additional attributes, legitimate transfers get held for manual review and the payment stalls. The transmitter must send date of birth, country, and, where available, nationality and ID numbers alongside the name, and the API must use those attributes to score the match. The response must include a confidence score per match so you can set your own review threshold.

3. Both Sides of Every Transaction

Onboarding tools screen the account holder, but a money transmitter must screen both sides of every transaction: the sender and the recipient. The recipient is usually not your customer. You may have only a name, a country, and sometimes a phone number, with no date of birth or ID to narrow the match. The API must score matches using these limited attributes rather than relying on customer-level data. The counterparty may also be a bank, agent, or payment institution, so the same endpoint must support both individual and entity screening. The Non-SDN Consolidated List, an OFAC sanctions list, also covers SSI-listed Russian banks, so an API that only screens the SDN List can pass them as clean.

4. Re-Screening When Lists Update

A customer who passed screening at signup can be added to a sanctions list later. OFAC publishes sanctions list updates several times a month, so a one-time screen cannot catch subsequent additions. The transmitter must re-screen its customer base after list updates, not only at signup. Two approaches are common. The vendor can monitor registered subjects and send alerts, billed per subject per month. Alternatively, the transmitter can run scheduled re-screening through a batch endpoint, billed per screening. For a base of 20,000 customers, monthly re-screening requires 20,000 screenings. Daily re-screening requires 600,000 screenings per 30-day month. The required screening volume can change which pricing model is cheaper.

5. Audit Trail for Regulators and Banking Partners

Sooner or later, an examiner asks how a specific transaction was screened: a state money transmitter license examiner, an IRS BSA examiner on behalf of FinCEN, your independent AML reviewer, or the sponsor bank holding your account. Examiners want the record of each individual screening, not a summary report. The stored API response is that record, so it must include the screening timestamp or list sync time, result, confidence score, and match reasons. The response should also echo your own customer or transaction reference, so the record maps to your database. If a field is missing, the screening cannot be proven from the stored response alone.

6. Non-Latin Name Matching

Retail users sign up from everywhere. A customer may enter a name in Cyrillic, Arabic, or Chinese while OFAC sanctions records list the same person in Latin script. Arabic names can also have several accepted Latin spellings, such as Mohammed, Muhammad, and Mohamed. The API must accept non-Latin input and match it against Latin entries, including aliases and AKAs. The API should also normalize diacritics, name order, and honorifics before scoring. Without this capability, a listed person can pass screening under a different spelling or appear as multiple separate matches.

7. Volume Spikes

Payment peaks can push screening volume far above normal within hours. Screening sits in the payment path, so a vendor that returns 429 errors at the rate limit or hard-stops at the monthly quota is blocking transfers, not just requests. The API must keep serving requests above the quota and bill the overage, and a plan upgrade must take effect immediately rather than at the next billing cycle.

8. Crypto Wallet Screening

Only relevant if the transmitter supports crypto deposits or withdrawals. OFAC, the US sanctions authority, lists specific wallet addresses on the SDN List, its primary sanctions list. A customer whose name is clean can still send funds to or receive funds from a listed address, creating sanctions exposure. The API must screen the wallet address itself, not only the customer, and cover the address types OFAC publishes, including BTC, ETH, USDT, and XMR. Direct wallet screening is a list match against SDN addresses, not blockchain analytics. Exposure scoring through intermediary wallets is a separate product. Wallet matches must come back in the same response structure as name screening. A wallet must also count as a standard subject in pricing rather than a separate product.

Best Sanctions Screening APIs

Each review below scores the API against the same 8 requirements, with pros and cons drawn from public documentation.

1. SanctionsLookup

SanctionsLookup is an OFAC screening API for money transmitters and payment companies that need transaction-level screening without a broader compliance platform.

SanctionsLookup documents a typical API response time of under 200 ms, supporting synchronous sender and recipient screening during transaction processing.

SanctionsLookup's strongest differentiator is its false-positive control. Each screening query supports a custom match-score threshold that controls matching sensitivity.

Screening queries can include hard identifiers such as national IDs and registration numbers, plus soft attributes such as date of birth, country, and address.

Additional attributes give the matching engine context to distinguish a legitimate customer from a sanctions-list match.

Every screening returns a match confidence score and a human-readable explanation of which attributes matched.

Individuals, entities, vessels, aircraft, and crypto wallets can all be screened through the same endpoint, with different subject types submitted together in a single request or screened separately. For example, a single batch can contain an individual, a company, and a crypto wallet. Results include the applicable OFAC sanctions programs and measures for each match.

For existing customers, scheduled batch screening supports re-screening, with sanctions data synced every 15 minutes. The API also returns the customer’s own reference, timestamp, score, match reasons, and sanctions data, making it easy to link each screening result back to the corresponding customer or transaction.

If screening volume exceeds the plan, requests continue to be processed and the additional usage is billed as overage. Plan upgrades take effect immediately. Wallet addresses use the same response structure as name screening and count as standard screening subjects.

The main limitation is scope: SanctionsLookup currently covers US OFAC sanctions, with EU and UK on the roadmap, and does not offer a managed ongoing-monitoring product.

SanctionsLookup lists monthly pricing at $49 for 5,000 screenings, $109 for 15,000, and $329 for 50,000, with 100 free screenings and no annual contract.

2. sanctions.io

sanctions.io is an AML screening platform best suited to higher volumes with account management.

sanctions.io documents an average API response time of about 350 ms, with sanctions data refreshed every 60 minutes across 75+ lists and 30+ jurisdictions.

The API supports individuals and entities. When a recipient is only a name and country, its name-matching model handles transliteration, aliases, spelling variations, and out-of-order names, while returning confidence scores with configurable thresholds.

A batch endpoint supports up to 10,000 records per request, while Continuous Monitoring can re-screen customers and send real-time alerts. The consumption model matters for transaction screening: screening both sides of each transaction means a 5,000-screening plan covers 2,500 transfers.

Crypto wallet addresses are supported as identifiers, but we could not find them documented as a standalone screening subject.

As of September 2026, sanctions.io’s pricing calculator shows 5,000 screenings/year at $1,299, 10,000 at $1,999, and 50,000 at $4,299. The calculator defaults to a two-year term, while selecting one year requires contacting sales.

3. ComplyAdvantage

ComplyAdvantage is a broader financial crime platform built for financial institutions and fintechs that want sanctions, PEP, adverse media, transaction monitoring, payment screening, and case management from one vendor.

In a money transmitter workflow, payment screening runs synchronously, but a hit is routed into a case and the decision comes back through a webhook rather than as a simple screening response.

ComplyAdvantage screens individuals, companies, and other entity types such as vessels and aircraft, and can screen payment-message elements. Its documentation says it can detect sanctioned entities within one hour of major list updates, while ongoing monitoring runs within the same platform.

API access requires onboarding and credentials delivered by email, rather than a self-serve API key. Pricing starts around $99/month but is based on monitored entities rather than individual screenings, so per-transaction counterparty screening doesn’t map directly to the pricing model.

4. Sanction Scanner

Sanction Scanner is a broader AML platform built for financial institutions, fintechs, and money transfer companies that want screening, transaction monitoring, fraud detection, KYB, risk assessment, and case management in one system.

Its REST API supports name and transaction screening with webhooks for two-way data exchange. Its database covers 1,000+ sanctions, PEP, and wanted lists across 200+ countries. The platform includes automated daily ongoing monitoring and a case management interface for compliance teams.

It also provides a free crypto address checker, although we could not find public documentation confirming crypto addresses as an API screening subject.

Public documentation does not provide a response-time figure, confidence-score fields, batch limits, or rate limits. Pricing is not public; Sanction Scanner uses per-query packages and sells through a sales call, with third-party sources reporting entry pricing around €990/month.

5. Castellum.AI

Castellum.AI is a risk-data provider that builds and enriches its own risk database in-house, founded by a former US Treasury OFAC official and aimed at institutions that treat data quality as the buying criterion. In a money transmitter workflow, it can screen individuals and entities and parse unstructured payment messages to extract names, locations, and IDs before screening them. Real-time monitoring and five-minute data updates support re-screening, while alert decisions are logged with source references and readable narratives. Pricing is not public and is sold through a demo.

6. Sumsub

Sumsub is an identity verification and compliance platform built for businesses that want KYC, AML screening, and monitoring in one onboarding flow. Screening covers applicants and counterparties, with LLM-based matching and human review for difficult cases. Ongoing monitoring is available on its Compliance tier, while transaction-counterparty screening sits inside its broader transaction monitoring product. Its AML data comes from ComplyAdvantage, Quantifind, and World-Check One, per Sumsub’s documentation. AML screening is included from the Compliance tier: $1.85 per verification with a $299 monthly minimum.

7. LSEG World-Check

LSEG World-Check is a long-established risk intelligence database used by financial institutions, compliance teams, and sponsor banks. Its analyst-curated database has run for 25 years, and World-Check One provides case management, full audit trails, and ongoing screening. Secondary identifiers help reduce false positives, while Zero Footprint Screening supports stateless individual checks and World-Check Verify targets real-time onboarding and payment flows. Latency, sync, quota, and wallet-screening details are not publicly specified. Pricing uses usage-based packages, with larger volumes handled through sales.

8. Dow Jones R&C

Dow Jones Risk & Compliance is an enterprise risk-data business from Dow Jones, backed by the same editorial infrastructure as The Wall Street Journal and Factiva. Its Watchlist data covers sanctions, PEP/RCA, and SIP subjects, alongside deep beneficial-ownership and state-owned-company data. Screening and Monitoring APIs support individual and entity screening with ongoing alerts and decision logs, while its multilingual analyst team adds depth to the data. Technical API parameters are not publicly specified, and it is often consumed through a separate screening engine. Pricing is sales-led.

Which One to Pick

• Your obligation is OFAC and you want to start screening this week on a monthly plan: SanctionsLookup.
• You screen higher volumes and want account management with annual contracts: sanctions.io.
• You want sanctions, PEP, adverse media, and transaction monitoring in one platform: ComplyAdvantage.
• Your compliance team wants a case management UI around the screening workflow: Sanction Scanner.
• You want the fastest data updates and enriched in-house data, with an enterprise sales budget: Castellum.AI.
• You are onboarding customers with full KYC anyway and want AML screening in the same flow: Sumsub.
• Your sponsor bank or partner explicitly asks for a recognized risk database: LSEG World-Check.
• You need deep beneficial-ownership data for 50% rule analysis: Dow Jones Risk & Compliance.

FAQ

Do Money Transmitters Have to Screen Every Transaction Against OFAC?

OFAC sanctions generally operate under strict liability: a money transmitter can violate the rules by processing a transaction involving a sanctioned party even if it did not identify the party beforehand. No OFAC regulation specifically requires a particular screening technology or says that every transaction must be screened against the SDN List. In practice, transaction screening is a standard control for US money transmitters, and sponsor banks and examiners may expect an MSB’s AML program to demonstrate how senders and recipients are screened.

Is OFAC Screening Enough for a US Money Transmitter, or Do I Need EU and UN Lists Too?

OFAC sanctions are the core sanctions obligation for a US money transmitter, but additional lists can become relevant depending on where you operate and your banking or payout relationships. EU and UK sanctions matter when you operate in those jurisdictions or deal with counterparties subject to their rules. UN sanctions can also be relevant depending on the jurisdictions and regulatory framework involved. If you operate only in the US, ask your sponsor bank and legal counsel whether broader coverage is actually required before paying for it.

How Much Does Sanctions Screening Cost per Transaction?

SanctionsLookup’s public monthly pricing starts at around $0.01 per screening, which is about $0.02 per transfer when both sender and recipient are screened. Annual consumption packages from larger vendors work out to roughly $0.09 to $0.26 per screening at entry volumes, while Sumsub charges $1.85 or more per verified subject when AML screening is included. Enterprise risk databases are generally licensed through sales with no public pricing.

How Often Do OFAC Sanctions Lists Update?

OFAC publishes sanctions changes whenever designations and other list actions occur, sometimes several times a month and sometimes multiple times in a week. For an API, the more useful number is how quickly the vendor syncs after OFAC publishes a change. The vendors in this comparison range from five-minute data updates to roughly one hour, while some other screening tools may update less frequently.

What Happens if a Customer Matches a Sanctions List After Onboarding?

If a customer is later designated by OFAC, the sanctions obligations apply from the time of the designation, not from when your screening system discovers it. A confirmed SDN match can require blocking or rejecting a transaction, depending on the circumstances, and OFAC generally requires blocking and reject reports within 10 business days when reporting is required. This is why ongoing monitoring or scheduled re-screening after list updates matters.

Can I Screen a Recipient with Only a Name and Country?

Yes. Screening APIs accept a name alone or a name combined with country, which may be all a money transmitter knows about a recipient. Fewer identifying attributes increase the number of potential matches, so confidence scoring and the review threshold determine which results require manual investigation. Adding a date of birth, nationality, address, or ID number when available can reduce false positives.

Does OFAC Screening Cover Crypto Wallet Addresses?

Yes. OFAC has added specific digital currency addresses to SDN entries, so a listed wallet address can be screened directly against the sanctions data. This is different from blockchain analytics, which evaluates exposure through intermediary wallets and transaction history. Direct OFAC wallet screening checks whether the address itself appears on the sanctions list; it does not by itself provide a broader blockchain risk assessment.