A transfer can be cheap for the customer and still require expensive attention from the provider. That is the commercial issue behind Banca d'Italia's latest reminder on sanctions screening: a small payment cannot simply disappear below a software threshold when the relevant controls apply.
The September 7 communication addresses supervised intermediaries and the implementation of restrictive measures. It is best understood as an operational clarification of existing obligations. Calling it a new restriction on every blockchain transaction would obscure both its timing and its scope.
The reminder points to a software setting
The Italian original says the relevant EBA guidelines have applied since December 30, 2025. It specifically asks intermediaries to check that systems, including third-party solutions, do not exclude transfers from screening through minimum-amount thresholds. The concern reaches the configuration of the service, rather than stopping at a policy document.
The EBA's announcement of the guidelines independently identifies that application date and explains their relationship with wider governance and risk controls. The September reminder therefore should not be modeled as if every compliant provider suddenly acquires an entirely new cost base.
The legal foundation is also broader than a particular screening vendor. Article 23 of Regulation 2023/1113 requires payment and crypto-asset service providers to maintain internal policies, procedures and controls for restrictive measures when performing transfers under the regulation. Buying software is an input into that process; it does not, by itself, demonstrate that the process works.
Screening costs follow transactions, not just their value
For an in-scope service, the economics can depend on the number of transfers and the effort required to resolve questionable matches. A small transfer and a large transfer may both need a screening decision. If revenue is mainly proportional to payment value while part of the control cost is per transaction, low-value payments can face a different margin constraint from large ones.
That is a conditional business-model inference, not a measured cost estimate for Italian crypto companies. Automated checks may be inexpensive when data is clean and no match occurs. The more difficult case is an ambiguous result that needs additional information, review or a decision before the payment proceeds. A provider's cost depends on that workflow, not merely on the price of an automated lookup.
A hypothetical service could increase throughput substantially while seeing the review queue grow faster than staffing capacity. In that case, customer delays would become the visible symptom of an internal control bottleneck. Another provider with better data and effective automation might accommodate the same transfer growth with little incremental friction. The communication does not reveal which firms are in either position.
This also changes how supplier revenue should be interpreted. Greater demand for screening tools could benefit vendors, but a new contract is not evidence that the customer's risk has fallen. The purchaser still needs a system suited to its payment flows. A cheap license paired with costly manual exception handling can be economically worse than a more expensive tool that produces useful, reviewable results.
An instant bank payment has a different control design
The Italian document explicitly distinguishes instant bank transfers. It describes customer screening at least daily and when new restrictive measures appear, instead of applying the same transaction-by-transaction party checks. It also identifies an option for qualifying low-risk providers handling domestic Italy-to-Italy funds transfers. These exceptions should not be casually imported into a crypto service's operating assumptions.
There is a separate boundary in the underlying regulation: person-to-person crypto transfers without a crypto-asset service provider fall outside its scope. That exclusion does not establish a general exemption from sanctions law. It simply means this particular provider-focused transfer regime cannot accurately be described as a universal check on all blockchain activity.
For investors, those distinctions make product mix important. Two firms with similar reported payment volumes may operate under different control arrangements and incur different costs. Comparing them solely on volume growth or a headline transaction fee could therefore miss a material operational difference. A useful comparison would identify what transfers are actually in scope and how exceptions are legally supported.
The useful metric is a resolved alert
The Italian supervisor asks for calibration that balances detecting designated parties with limiting false positives. That balance is not captured by counting alerts alone. More alerts might reflect better detection, worse data, overly broad matching or a genuine change in exposure. Fewer could reflect improvement or missed cases. Neither direction is automatically reassuring.
A stronger operating assessment would examine whether known test cases are detected, whether ambiguous cases receive timely decisions and whether system changes preserve the required coverage. These are analytical evaluation criteria, not a claim that the communication mandates a particular public reporting dashboard. The practical question is whether the provider can explain its decisions and keep legitimate payments moving.
The strongest limiting argument is that well-prepared firms may already do this effectively. For them, the reminder may produce a configuration review rather than a material earnings hit. Evidence of compliant coverage with stable service quality would weaken the cost-pressure thesis. Persistent review backlogs or unsupported exclusions would strengthen it. The financial consequence depends on execution, not on the dramatic wording of a crypto headline.