OFAC Sanctions Screening for Canadian Exchange Houses

OFAC sanctions screening can no longer treat Canadian exchange houses as low-risk payment utilities. The November 6, 2026 designation of eight Canada-based money services businesses shows how Iranian digital asset exposure can reach importers, exporters, freight forwarders, and customs brokers through intermediaries that appear geographically removed from Iran.

What the Canadian Exchange House Designations Mean

OFAC added eight Canadian businesses to the Specially Designated Nationals and Blocked Persons List under E.O. 13902 for operating in the digital asset sector of the Iranian economy. The entities are located in Ontario, British Columbia, and Quebec, and each holds a Canadian money services business registration.

The action blocks property and interests in property that are within U.S. jurisdiction. U.S. persons are generally prohibited from engaging in transactions involving the designated entities unless an applicable authorization or exemption is available. Each listing also carries a secondary sanctions risk indicator under Section 2 of E.O. 13902, which is relevant to non-U.S. companies assessing whether continued dealings could create U.S. sanctions exposure.

The Eight Designated Businesses and Their Aliases

The designated entities include:

• 1380079 BC LTD, also known as Amin Exchange Vancouver and Sarafi Amin
• 2397639 Ontario Ltd, also known as Farah Exchange
• B Galaxy Inc, also known as C Exchange and Cryptoyal
• CCC Inc, also known as Ccurrency Exchange, Cryptoyal, Sarafi C, Parsis Exchange, Salam Exchange, and Sarafi Capital
• Darvish Exchange, also known as Kanata MD Inc and Canada Exchange
• Diverse Trade Inc, also known as Million Exchange and Millionex
• Nia Nations Currency Ltd, also known as Nia Exchange
• Top PC Technician Inc, also known as Amin Exchange Toronto and Aminex Toronto

Several of these names are generic enough to create false-positive risk, while numbered companies and overlapping aliases make false negatives equally possible. Screening only the primary legal name is therefore inadequate. Trade compliance teams should screen legal names, business names, payment instructions, wallet identifiers, addresses, telephone numbers, and other available identifiers.

A Canadian registration does not override a U.S. blocking designation. Registration status and sanctions status answer different compliance questions, and both must be evaluated independently.

Why Payment Intermediaries Create Hidden Sanctions Exposure

Importers and exporters often focus screening on the buyer, seller, manufacturer, consignee, and freight forwarder. That approach can miss a critical layer of transaction risk. An apparently legitimate customer may direct payment through an exchange house, money services business, over-the-counter digital asset broker, or unrelated third party.

Canadian exchange houses can appear operationally routine, particularly when they maintain local addresses, domestic bank relationships, or formal registrations. Those characteristics do not eliminate the possibility that the intermediary is settling transactions for sanctioned jurisdictions, blocked persons, or Iran-linked digital asset businesses.

Screening Must Extend Beyond the Commercial Counterparty

A defensible sanctions control framework generally screens every identifiable party that participates in the movement of goods, funds, or digital assets. Depending on the transaction, this can include:

• Banks and nonbank payment providers
• Exchange houses and money services businesses
• Digital asset exchanges and wallet operators
• Freight forwarders and customs brokers
• Notify parties and ultimate consignees
• Third-party payors and refund recipients
• Directors, owners, and controlling persons

The OFAC 50 percent ownership rule also matters when designated entities use affiliates, newly formed companies, or alternate operating names. An entity may generally be treated as blocked when one or more blocked persons own, directly or indirectly and in the aggregate, 50 percent or more of it, even if the entity does not appear by name on the SDN List.

Digital asset settlement adds another identification layer. Wallet addresses can be changed, reused, nested through services, or connected through intermediary wallets. Six TRON addresses were associated with four of the designated businesses, but screening should not be limited to those identifiers. A clean wallet result does not resolve the risk created by a name, ownership, contact detail, or payment instruction match.

Compliance teams should also treat unexplained changes in payment method as a red flag. Requests to substitute a Canadian exchange house, receive USDT, use an unrelated wallet, or split settlement among multiple parties warrant escalation before goods or funds move.

Immediate Compliance Actions for Trade Organizations

The first priority is to prevent new transactions involving the designated businesses. Screening systems, internal watchlists, payment controls, and escalation procedures should be updated with each legal name and known alias. Organizations using multiple screening tools should confirm that updates reached every production environment, including accounts payable, customer onboarding, logistics, and treasury workflows.

Automated list updates are necessary, but they do not replace operational validation. Compliance teams should test representative aliases such as Cryptoyal, Millionex, Amin Exchange Toronto, and Sarafi Capital to confirm that matching logic produces reviewable results without relying solely on exact spelling.

Conduct a Risk-Based Lookback Review

A retrospective review should generally cover recent transactions involving Canadian exchange houses, third-party payment instructions, Iran-linked counterparties, and digital asset settlement. The appropriate period depends on the organization’s risk profile, transaction volume, data quality, and legal guidance.

The review should examine more than completed payments. Relevant records can include:

1. Supplier and customer master data
2. Bank account change requests
3. Wire instructions and remittance details
4. Wallet addresses and blockchain transaction identifiers
5. Commercial invoices and purchase orders
6. Freight forwarding correspondence
7. Refunds, credits, commissions, and rebates
8. Rejected or canceled payment attempts

Potential matches should be placed on hold and escalated under documented procedures. An organization should not reject, return, release, or redirect funds solely as an improvised operational response. Blocking and rejection obligations can differ, and the correct treatment typically depends on the parties, payment path, jurisdiction, and financial institution involvement.

Strengthen Payment Change Controls

Sanctions screening should be integrated with controls for payment instruction changes. A customer or supplier request to replace its normal bank account with a money services business or digital asset wallet should require independent verification. Effective procedures commonly include callback verification, sanctions rescreening, ownership review, and approval by personnel outside the commercial relationship.

Training should reach treasury, accounts payable, accounts receivable, sales, procurement, and logistics. These teams often see the warning signs before compliance does. A sanctions program is only as effective as the organization’s ability to identify and stop an unusual transaction before execution.

Customs, Export, and Duty Drawback Considerations

OFAC blocking sanctions and U.S. customs laws serve different purposes. The designation of an exchange house does not, by itself, change tariff classification, customs valuation, country of origin, duty rates, or the statutory eligibility of merchandise for duty drawback. It can still prevent a transaction from proceeding when a blocked person is involved.

This distinction is important for customs brokers and importers. A shipment can be properly classified and entered while presenting an unacceptable sanctions risk through its buyer, seller, payment intermediary, beneficial owner, or ultimate consignee. Customs admissibility does not constitute sanctions clearance.

Duty Drawback Does Not Override Sanctions Restrictions

Duty drawback generally allows eligible duties, taxes, and fees to be recovered when statutory requirements are satisfied. An export used to support a drawback claim must still comply with applicable sanctions and export controls. Drawback eligibility does not authorize a prohibited dealing with a blocked person, and a potential refund should never be treated as permission to complete the underlying export.

Brokers handling drawback claims should consider whether designated parties appear in commercial invoices, bills of lading, export records, payment records, or documents supplied by the claimant. The exchange house may not appear as the importer, exporter, or consignee. It may instead appear only in remittance instructions or supporting financial records.

Separate Customs Controls From Sanctions Controls

Organizations should maintain distinct but connected review processes. Customs controls address matters such as classification, valuation, origin, entry accuracy, and drawback substantiation. Sanctions controls evaluate prohibited parties, blocked property, ownership, payment routing, and restricted conduct.

The two functions should exchange relevant data without assuming that one review satisfies the other. A customs broker may screen parties shown on entry documents, while the importer’s treasury team screens the actual payor and payment recipient. Clear allocation of responsibility helps prevent an intermediary from falling between organizational systems.

Records should document the screened parties, identifiers used, match disposition, reviewer, date, and rationale. This evidence is valuable when an organization must explain why it cleared, stopped, blocked, or escalated a transaction.

Frequently Asked Questions

Are All Canadian Money Services Businesses High Risk?

No. A Canadian money services business registration does not make an entity sanctioned, and most registered businesses are not blocked. However, registration should not be treated as a substitute for sanctions screening, beneficial ownership review, or transaction-specific due diligence.

Must U.S. Companies Stop Dealing With the Eight Entities?

U.S. persons are generally prohibited from dealing with designated entities when property or interests in property are involved, unless an authorization or exemption applies. Organizations should place potential transactions on hold and obtain qualified guidance before taking action.

Should Companies Screen Digital Asset Wallet Addresses?

Yes, when wallet information is available or digital assets are part of the transaction. Wallet screening should supplement, not replace, name, alias, ownership, address, and counterparty screening. Digital asset exposure can extend beyond addresses expressly associated with a designated entity.

Do These Designations Automatically Affect Duty Drawback Eligibility?

No direct tariff or drawback consequence arises solely from the designation. However, an import, export, payment, or refund involving a blocked person may create a separate sanctions problem. Drawback processing should therefore remain connected to broader counterparty screening controls.

What Should Happen After a Possible Name Match?

The transaction should typically be paused while reviewers compare identifiers such as address, jurisdiction, registration information, ownership, telephone number, and payment details. A generic name match alone may be insufficient, but a potential match should not be dismissed without documented analysis.

How Stable Software Can Help

Support Consistent Trade Compliance Workflows

The Canadian exchange house designations reinforce the need to screen more than buyers and sellers. Customs brokers, importers, and trade compliance teams should account for aliases, payment intermediaries, ownership relationships, and digital asset identifiers within their review processes.

Organizations evaluating technology for these controls can explore Stable Software’s denied party screening platform. For customs brokers that also manage drawback, Stable Software makes DrawbackAI, flat-license duty drawback software that brokers can white-label for importer clients and use to file under their own filer codes. Stable Software charges a flat software license and never takes a percentage of the refund. Together with documented internal procedures, appropriate technology can help firms build more consistent compliance operations as sanctions risks move deeper into payment and logistics networks.

Resources