Someone reviewing a payment sees a mixer-related label or hears that a bridge was involved. The next message says the customer must have concealed the source of funds. That conclusion skips several questions: what the report actually labels, which subject was checked, whether the connection was direct and what evidence supports the customer's role. Start with those questions before deciding how to describe the finding.
Use the category the report actually gives
A2 Route's sample appendix defines Mixer / money laundering as a service associated with obscuring transaction provenance or laundering flows. It also says categories describe recorded exposure labels, not a conclusion about a person or transaction. Keep both statements together. A label identifies the concern being reviewed; it does not establish the customer's intent.
Read the data-sources definitions and the direct and indirect exposure guide. Do not replace a specific reported category with a broader accusation. “The report records mixer-related exposure” and “the customer laundered this payment” are different claims, and the first does not establish the second.
The current sample appendix does not list a separate Bridge risk category. Do not invent one in your notes or claim that every bridge reference is a mixer finding. If a counterparty describes a bridge in their sending arrangement, record that as their explanation unless the report independently supports a more specific statement. This guide does not promise automatic cross-network reconstruction by A2 Route.
Separate a path from control of a wallet
The synthetic report describes direct exposure as a direct transfer from a flagged entity or sanctions-list address. It describes indirect exposure as reaching a flagged entity through intermediaries, at two or more hops. Read the path description with the checked subject and direction. Do not treat the same words as an ownership finding.
For a fictional staff exercise, use FAKE_UPSTREAM_NOT_A_WALLET, FAKE_INTERMEDIARY_NOT_A_WALLET and FAKE_CUSTOMER_NOT_A_WALLET. These are deliberately invalid synthetic labels. A path between those labels illustrates the distinction between relationships; it is not evidence that one person controlled every step or chose every upstream service.
Indirect exposure can justify a focused review without proving guilt. Ask what the path concerns, why it is relevant to this payment and which information is missing. Equally, do not dismiss a finding simply because an intermediary appears. Keep the recorded relationship intact while deciding what additional evidence your business needs.
Do not merge different kinds of findings
A provider-associated exposure label is not the same as a direct sanctions-list match. The synthetic REVIEW report demonstrates that distinction: indirect provider-flagged exposure appears while sanctions-list rows show no match. Preserve the individual rows and the explanation instead of writing “sanctions hit” as a catch-all summary.
The risk-score guide explains another common shortcut. A number does not tell you the probability that a customer acted unlawfully. Read it with the explanation, source shares, top exposure and coverage. Serious-sounding categories still require a careful description of what the screening result actually records.
Keep percentages within their stated scope
Before using a share, read the mode explanation. The outgoing sample's address-mode shares concern the destination wallet's traced incoming funds. They do not state that the same fraction of a proposed outgoing payment has that origin. Do not carry a percentage from one wallet or network into another payment merely because the commercial story links them.
If the customer supplies separate references for a sending arrangement involving different networks, retain those references separately and assess the supported subjects independently. A2 Route's public scope covers address and USDT/USDC transaction screening on TRON and Ethereum. That scope is not a claim that separate results prove a single continuous cross-network path. The PDF walkthrough helps distinguish the report's evidence from your own case narrative.
Ask about the arrangement without an accusation
Ask which service handled the transfer, which sending wallet was expected and how the provided references relate to the invoice. Record the reply as customer-provided information. If the explanation cannot be reconciled with the checked subject, keep the discrepancy open rather than inventing a connection that the report does not show.
The sample limitations say beneficial ownership, off-chain identity and purpose of payment are not verified. Keep those limits in the review note. Labels can change, so retain the screening time and original result. For reduced coverage, the public FAQ recommends a re-check; a later result should not erase the first.
If payment is paused, follow the flagged-counterparty checklist. For a separate supplier payment, consult the A2vanta business payment blog. Explore A2 Route screening or read the API documentation. The report is informational, not legal advice, proof of guilt, a clean-funds guarantee or a promise of regulatory compliance.