What sanctions screening is
A sanction is a restriction imposed by a government or an international body that prohibits dealing with a named target — an individual, a company, a vessel, or sometimes an entire jurisdiction. Those targets are published in sanctions lists, the best known being the lists maintained by national authorities and supranational bodies. The lists change as targets are added and removed. Screening is the act of comparing the people and entities you are about to transact with against the current versions of those lists, so that a prohibited party is caught before money moves rather than after.
Screening is not a single yes-or-no lookup; it is a recurring control with a few moving parts. It happens at onboarding, when a business establishes who a new counterparty is, and it continues over time, because lists are updated and a previously clear party can later become a designated target. It has to account for imperfect data — names are spelled differently, transliterated, or deliberately altered — so screening systems look for close matches, not just exact ones, and a potential hit is reviewed by a person before any conclusion is drawn. A match that turns out to be the wrong person is a false positive; missing a real target is the failure the control exists to prevent.
It is worth being precise about what sanctions screening is not. It is not a certification or a licence a business can hold and display — it is an obligation a business satisfies continuously, transaction by transaction and party by party. It is not the whole of an anti-money-laundering programme; it sits alongside customer due diligence, transaction monitoring, and record-keeping rather than replacing them. And it is not a guarantee that nothing prohibited can ever slip through — it is a risk-reduction control whose job is to make prohibited dealings visible and avoidable, on the basis of the data and lists available at the time.
Why it matters for crypto payments
Crypto payments carry the same prohibition as any other way of moving value — you cannot transact with a sanctioned party — but the mechanics of screening are shaped by how blockchains work. A transfer is tied to an address rather than directly to a named person, so screening in this context extends to the address itself: authorities and analytics providers publish blockchain addresses associated with sanctioned targets, and a business screens counterparty addresses against those alongside the names and entities it already checks. The public, permanent nature of on-chain records helps here — a flow can be traced — but addresses can be created freely and value can move between chains, which is exactly what address screening and ongoing monitoring exist to keep track of.
Because the obligation follows the value and not the rail, a business accepting crypto is not exempt from sanctions requirements simply because the payment is on-chain. What exactly applies — which lists, which thresholds, what you must record, how you must respond to a hit — depends on your jurisdiction and your activity, and those are legal and compliance questions that turn on facts about your business. A general explanation, including this one, describes the concept; it does not determine your obligations. The right place to settle which sanctions rules apply to you, and how to operationalise them, is your own counsel and your compliance process, not a marketing page or an API setting.
Sanctions screening and halfin
halfin is digital-asset payment infrastructure, and it treats sanctions screening the way it treats compliance generally — as a process it supports operationally, never as a certification or licence it holds. The platform's compliance surface is concrete: businesses are verified at onboarding through a know-your-business (KYB) process before any money moves, the actions that move funds run through scoped API keys and operator approval, and movement is recorded on-chain — deposits credited reorg-aware against per-chain confirmation thresholds — so activity can be reviewed. That verified identity at the gate and that accurate record are the operational foundations screening-related obligations sit on top of, but supporting that foundation is not a regulatory claim, and halfin never describes itself as licensed or regulated as a status.
For a merchant, the practical takeaway is to keep the boundary clear. halfin runs the operational plumbing — KYB at onboarding, scoped permissions on the actions that move money, and a precise settlement record — while which sanctions lists apply to your transfers, how you screen counterparties, and how you respond to a potential hit remain yours to determine with your counsel and your own compliance programme. The questions that decide it — your jurisdiction, your activity, your role in each transaction — are the kind that get assessed in onboarding, where the specifics of your business can actually be evaluated, rather than answered by a general statement. Nothing here is legal or compliance advice; it is an explanation of the concept and of where halfin's responsibility starts and stops.
- Sanctions screening = checking parties and, in crypto, blockchain addresses against sanctions lists before and while you transact with them.
- It is an ongoing control — run at onboarding and repeated as lists change — that uses close matching and human review, not a single exact lookup.
- Crypto carries the same prohibition; screening extends to counterparty addresses because transfers are tied to addresses rather than names.
- It is one building block of an AML programme, not a certification a provider holds.
- halfin supports such obligations operationally through KYB onboarding, scoped permissions, and an on-chain record — but determining what applies is a legal and compliance question, not an API setting, and nothing here is legal advice.