Skip to content
← Back to blog
Workplace·November 17, 2026·8 min read

Does an agency have to screen its offshore subcontractors against OFAC sanctions lists? What the Tango Card settlement says about screening the people you pay

Tango Card screened its customers but not the people it paid, and settled with OFAC. What that means for an agency paying offshore developers.

Most agencies that run a know-your-customer check run it on the client. Someone looks at who is paying the invoice. Almost nobody runs it on the other side of the ledger, the offshore developer or small firm the agency pays every month. The US Treasury's sanctions office has already settled a case over exactly that gap, and the company involved did have screening in place. It had pointed it the wrong way.

This post reads that case and OFAC's own compliance guidance and turns them into a short onboarding check for a subcontractor. It is general information, not legal advice. Have counsel confirm what applies to you.

What happened in the Tango Card case?

On 30 September 2022 the Office of Foreign Assets Control (OFAC), part of the US Treasury, announced that Tango Card, Inc., a Seattle company that distributes electronic rewards, agreed to pay $116,048.60 to settle apparent violations of several sanctions programs. OFAC's enforcement release says that between September 2016 and September 2021 Tango Card sent 27,720 merchant gift cards and promotional debit cards, totaling $386,828.65, to people with email or IP addresses associated with Cuba, Iran, Syria, North Korea or the Crimea region of Ukraine.

The detail that matters for an agency is in the next paragraph of the release. OFAC wrote that Tango Card "used geolocation tools to identify transactions involving countries at high risk for suspected fraud and had OFAC screening and Know Your Business mechanisms around its direct customers," but "did not use those controls to identify whether recipients of rewards, as opposed to senders of rewards, might involve sanctioned jurisdictions."

Read that as an agency owner. Tango Card screened the party that paid it. It did not screen the party it paid. You probably do the same thing, because the paying side is where your contract, your credit risk and your instinct all point.

OFAC treated the case as non-egregious and voluntarily self-disclosed, which is why the settlement was smaller than the base penalty of $193,414.33 it calculated. Self-disclosure and cooperation were listed as mitigating factors. The failure to use IP and email-domain data the company already held was listed as aggravating.

Does that mean an agency must screen every subcontractor?

OFAC did not say that, and I would not claim it. The Tango Card release is about a company moving stored value to recipients. An agency wiring a monthly invoice payment to a developer is a different business. What the release does give you is OFAC's stated view of the control gap, and what its published guidance says an organization should look at.

OFAC's 2019 document, A Framework for OFAC Compliance Commitments, says a sanctions compliance program should rest on five components: management commitment, risk assessment, internal controls, testing and auditing, and training. On risk assessment it says an organization should look at its "customers, supply chain, intermediaries, and counter-parties" and at the geographic locations of each. A subcontractor you pay is a supply-chain party and a counterparty. A payment platform between you and them is an intermediary.

I could not find OFAC guidance written specifically for software agencies paying overseas contractors, and I am not a sanctions lawyer. My own view is narrower than a legal rule: the check costs minutes, the exposure is a federal sanctions program, and OFAC's own enforcement language treats ignoring data you already hold as a worse fact pattern than missing something you could not have known.

What does the Tango Card lesson look like for an agency?

Picture a 14-person agency that brings on a three-person firm overseas for a client's web build. The contract is signed, the first invoice arrives, and the agency's finance person pays it through a business payment platform. The agency has checked the client against its internal list of who it will work with. Nobody has checked the subcontractor's country, ownership or where its developers log in from.

Now apply the Tango Card pattern. The agency already holds data: the subcontractor's registered address, the domain of its email, the country of its bank account, and the location its developers connect from when they push code. Tango Card held IP addresses and email domains that pointed to sanctioned places and did not use them. The agency's equivalent is data sitting in its own invoicing system, repository access logs and payment records.

OFAC's release also makes a second point that bears on contracts. It says that "while contractually obligating customers to comply with sanctions regulations can help mitigate risk, it does not obviate the need to impose other sanctions compliance controls when appropriate on a risk basis." A clause in your subcontract saying the sub will comply with all sanctions laws helps. It does not replace looking.

What should the onboarding check include?

A reasonable version fits on one page and runs once at onboarding, then again when something changes:

  1. 1.Identify the legal entity and its owners. Get the name of the firm, its registered address, and who owns it. OFAC's 50 Percent Rule, as stated in its FAQ 401, treats the property of entities owned 50 percent or more in the aggregate by one or more blocked persons as blocked, and OFAC urges "appropriate due diligence on entities that are party to or involved with the transaction" to determine ownership stakes.
  2. 2.Screen the entity and the named owners against OFAC's lists. OFAC publishes a free Sanctions List Search tool on its website. Screen at onboarding and keep a dated record of the result.
  3. 3.Check where the work and the money actually are. Compare the country on the contract with the country of the bank account, the email domain and the locations developers connect from. A mismatch is a question to ask, not proof of anything.
  4. 4.Know the comprehensively sanctioned places. The Tango Card release names Cuba, Iran, Syria, North Korea and the Crimea region of Ukraine. OFAC's program pages are the place to confirm the current list, which changes.
  5. 5.Put a change clause in the subcontract. The sub tells you if its ownership changes or if work moves to a new location, and you can suspend payment while you check.
  6. 6.Re-screen on a schedule. Tango Card's own remedial step was a monthly report of IP addresses and domains tied to sanctioned places. An agency's version can be a quarterly re-screen of the people it pays.

One caution on item 1. OFAC's FAQ 398 says the 50 Percent Rule "speaks only to ownership and not to control," so an entity controlled but not 50 percent owned by a blocked person is not automatically blocked, though OFAC urges caution and can designate it separately. Do not read a clean ownership screen as the end of the question.

When is a formal sanctions check the wrong answer?

If your subcontractor is a US-based firm paid through a US bank and every developer works from the US, a heavy cross-border process is more than you need, and a name screen at onboarding is enough. If you pay a very large, established outsourcing company with its own published sanctions program, review its policy rather than rebuilding the check yourself. And if your actual question is whether a specific payment is legal, that is a question for a sanctions lawyer, not a blog post. What this post covers is the routine screening step, not a legal opinion on a particular country or person.

How this fits with the rest of your subcontractor paperwork

Sanctions screening sits next to the checks you probably already run. The tax paperwork for a foreign contractor is covered in our guide to 1099 and W-8BEN forms for offshore contractors. The data-handling side of an offshore bench is in our reading of the DOJ data security rule for agencies. And the exit side is in how to offboard a subcontractor and rotate the secrets they could read. Run together, they make one onboarding packet.

If you want overflow capacity from a partner whose paperwork you can ask to see before the first invoice, see how our agency partner arrangement works, and ask any partner you consider, including us, to walk you through how they handle screening. If you have a scope in mind, tell us about it.

Sources

Written by Zain Ali

Frequently asked questions.

OFAC has not published a rule specific to software agencies. Its 2019 Framework for OFAC Compliance Commitments says a sanctions compliance program should assess "customers, supply chain, intermediaries, and counter-parties" and their locations. A subcontractor you pay is a supply-chain party, so a documented screen at onboarding is a reasonable risk-based step; confirm the details with counsel.

In an enforcement release dated 30 September 2022, OFAC said Tango Card sent 27,720 gift cards and promotional debit cards between September 2016 and September 2021 to people with email or IP addresses tied to Cuba, Iran, Syria, North Korea or the Crimea region of Ukraine. OFAC noted the company screened its direct customers but did not use its controls to check who received the rewards.

It helps but does not replace other controls. OFAC's Tango Card release of 30 September 2022 says that contractually obligating customers to comply with sanctions regulations "can help mitigate risk" but "does not obviate the need to impose other sanctions compliance controls when appropriate on a risk basis."

OFAC's FAQ 401 states that entities owned 50 percent or more in the aggregate, directly or indirectly, by one or more blocked persons are considered blocked. OFAC urges due diligence on the parties to a transaction to determine ownership. Per FAQ 398, the rule covers ownership and not control, so a clean ownership result is not the end of the analysis.

Identify the legal entity and its owners, screen both against OFAC's published list search, and compare the contract country with the bank, email domain and developer connection locations. Keep a dated record, add a change-notification clause to the subcontract, and re-screen on a schedule. This is a routine check, not legal advice; consult counsel for a specific payment.