Payment Sanctions Screening for Wires

Payment sanctions screening is the check you run on a payment or wire before it leaves your hands. You compare every party and every meaningful field in the message against sanctions lists, hold anything that looks like a match, and release only what's clear. Done well, it stops a prohibited transfer before money moves. Done badly, it either lets one through or buries your team in false alerts.

Customer screening at onboarding isn't enough on its own. A clean customer can still send money to a designated beneficiary, route it through a blocked bank, or pay for cargo on a listed vessel. Here's what to check in each payment, when to check it, and what OFAC expects when a hit turns out to be real.

Why payments need their own screening

When you onboard a customer, you screen one party once. A payment brings new names every time: the person being paid, their bank, intermediary banks, and whatever someone typed into the remittance field. None of them went through your onboarding checks.

OFAC regulations apply to the transaction itself. If a U.S. person processes a transfer in which a blocked person has an interest, the funds generally have to be blocked, whether or not your own customer is clean. That's why banks, payment companies, money transmitters and many marketplaces run a separate screen on outgoing and incoming payments. Our payment screening for wires and transfers is built around that moment, between instruction and release.

Which parties and fields to screen

The most common gap isn't a weak matching engine. It's a field nobody screens. Use this table as a starting checklist for wires, ACH, card payouts and similar transfers.

Field or party	What to screen	Why it matters
Originator	Name, address, country, account holder	Incoming funds from a blocked person must be blocked too
Beneficiary	Name, address, country, account details	The most frequent source of true hits on outgoing wires
Ordering and beneficiary banks	Bank name, BIC, city, country	Designated banks appear on the SDN list and under sectoral programs
Intermediary and correspondent banks	Name and BIC of every bank in the chain	A clean sender and receiver can still route through a listed bank
Free text	Remittance information, purpose of payment, references	Names of vessels, goods, cities and companies often appear only here
Vessels	Vessel names and IMO numbers mentioned in the payment	OFAC lists vessels with identifiers, common in shipping and commodity trades
Crypto addresses	Wallet addresses for deposits, withdrawals and payouts	OFAC includes specific digital currency addresses in some SDN entries
Geography	Countries and cities across all fields	Comprehensively sanctioned jurisdictions can make a payment prohibited even without a listed name

Two practical notes. First, screen the free text, not only the structured fields. A beneficiary called "Trading LLC" can carry the real counterparty's name in the reference line. Second, match names with fuzzy logic that handles aliases and transliteration, and match identifiers such as BIC codes, IMO numbers and wallet addresses exactly. An identifier hit is far stronger evidence than a name that sounds similar.

Don't forget the ownership angle either. A beneficiary owned 50 percent or more by blocked persons is blocked even when its name is on no list, which we cover in detail in our guide to the OFAC 50 percent rule.

Screen in real time, before release

Screening after the money has gone is a record of a problem, not a control. The check has to sit in the payment flow, after the instruction is complete and before funds are released or the message is sent onward.

That means the screen has to be fast and it has to give a clear answer. A typical setup works like this:

The payment system sends the full payment, with all parties and fields, to the screening service.
The service returns clear, or a list of potential matches with scores and the field that triggered each one.
Clear payments continue automatically.
Payments with potential matches go on hold and land in a review queue.
An analyst reviews the hold and decides to release, block or reject, with the reasoning saved.

If you connect your own payment flow, a sanctions screening API with signed webhooks lets your system receive the result and the later review decision without polling. The lists also change often, so screening against yesterday's version isn't good enough for a payment released today.

Holds and how to review them

A hold is a pause, not a verdict. Most holds are false positives, such as a common surname or a city that shares a name with a listed entity. Your team needs enough context to clear them quickly and enough discipline to escalate the ones that aren't.

For each hold, the reviewer should check:

Which field matched. A match in the beneficiary name means something different from a match on a word in the remittance text.
Secondary identifiers. Date of birth, nationality, address, BIC, IMO number or wallet address. Do they agree with the list entry or contradict it?
The listing details. Program, aliases and remarks on the entry.
The customer relationship. Does this payment fit what you know about the sender?

Write down why you cleared or escalated a hold. A good evidence record captures the payment, the list version, the match, the reviewer and the decision. Results from any tool support that decision, and the decision stays with your team.

Blocked versus rejected transactions

When a hit is real, OFAC regulations draw a line between two outcomes, and the difference matters.

Blocked. If a blocked person, or a party blocked under the 50 percent rule, has an interest in the payment, you generally must block the funds. You don't send them back. You hold them, usually in a separate interest-bearing blocked account, until OFAC authorizes their release through a license or the person is delisted.

Rejected. Some payments are prohibited but not blockable. A common example is a transfer tied to a comprehensively sanctioned jurisdiction where no blocked person has an interest. In that case you don't process the payment and you return or decline it instead of holding the funds.

Getting this wrong cuts both ways. Returning funds that should have been blocked hands money back to a sanctioned party. Blocking funds that should have been rejected creates an unnecessary frozen balance and a reporting obligation you didn't need. When the program or the ownership picture is unclear, take legal advice before you act.

Reporting to OFAC within 10 business days

Both outcomes come with reporting duties under the Reporting, Procedures and Penalties Regulations in 31 CFR part 501.

Situation	What to file	Deadline
Funds blocked	Initial blocked property report (31 CFR 501.603)	Within 10 business days of blocking
Funds still blocked as of June 30	Annual report of blocked property	By September 30 each year
Payment rejected	Rejected transaction report (31 CFR 501.604)	Within 10 business days of rejection

OFAC accepts these reports through its online reporting system. Keep copies of what you file. Recordkeeping under 31 CFR 501.601 now runs for 10 years, after OFAC extended it from 5 years in 2025 to match the longer statute of limitations for sanctions violations. Check the current text of the regulation and any program-specific rules that apply to you.

A short checklist

Screen originator, beneficiary, every bank and BIC, free text, vessels and crypto addresses.
Run the screen before release, against current lists.
Hold potential matches and review them with secondary identifiers.
Decide block, reject or release, and record why.
File blocked and rejected reports within 10 business days.
Keep the evidence for 10 years.

Common questions

Do incoming payments need screening too

Yes. If funds come from a blocked person, or are meant for one, they generally have to be blocked. Screening only outgoing payments leaves half the risk open.

How fast does payment screening have to be

Fast enough not to delay clean payments. The goal is an automatic decision for clear payments and a quick, well documented review for holds.

Can I screen payments in bulk

For batch payouts such as payroll or marketplace settlements, a batch file screen before release works well. Live wires belong in a real time check. If you want to see how holds, reviews and evidence fit together, look at how OfacScanner screens payments before release.

Want to see a result before anything else? Screen one name now with the OFAC search on our home page and look at the matches, scores and list date it returns.