A new customer has supplied a wallet and wants an account opened today. The sales team has a company name, an invoice and a reassuring explanation. None of those tells the reviewer what the proposed wallet check actually found. Treat screening as one part of onboarding: identify the subject, read the evidence and leave a record that another colleague can understand without repeating the whole conversation.
Establish which wallet you are reviewing
Ask the customer for the proposed sending address and network through your agreed onboarding channel. Record who supplied the details, when they arrived and which customer file they belong to. Confirm whether the customer expects to send personally or through a service. That answer is customer-provided information, not something an address result establishes by itself.
A2 Route's public scope covers addresses and USDT/USDC transactions on TRON and Ethereum. Pick the supported network that matches the proposed payment. Do not turn support for those checks into a claim about other assets or chains. The incoming USDT checklist explains the later receiving stage.
For staff training, use a deliberately invalid synthetic label such as FAKE_ONBOARDING_WALLET_NOT_AN_ADDRESS. It is not an address to submit. Keep real customer identifiers in the private onboarding file, not in public examples or a presentation circulated outside the review team.
Read the finding, not only the verdict
Start with the checked subject and screening time. A result for an old wallet, a different network or another customer's file cannot support this onboarding decision. Record whether the subject was an address or an existing transaction. A preliminary address check is not evidence about a payment that has not happened yet.
The published A2 Route report description includes a verdict and score, source shares, top exposure, sanctions lists and a risk-categories appendix. Review those parts together. A score is not a probability that the prospective customer committed wrongdoing. Use the risk-score guide when explaining the number to someone who did not run the check.
Keep list results separate from exposure descriptions. The synthetic REVIEW sample records provider-flagged indirect exposure while its sanctions-list rows show no match. That is not a direct finding that the customer appears on a sanctions list. Copy the actual finding into the file rather than compressing different types of evidence into a single alarming sentence.
Write down the unanswered questions
An address report does not replace your customer information. The sample's limitations say beneficial ownership, off-chain counterparty identity and purpose of payment are not verified. If those questions matter to onboarding, obtain and assess the relevant information separately. Do not claim that the report checked a company document merely because the document sits beside it in your archive.
Ask questions tied to the evidence. If the sending arrangement involves an intermediary, ask which party will initiate the payment and how that relates to the commercial relationship. If a reported path raises concern, ask for an explanation of that specific path. Preserve the customer's answer as their statement, not as a correction to the screening data.
Coverage belongs in the decision note. A2 Route's public FAQ says a partial result means reduced coverage and recommends a re-check. State what remains uncertain and who will resolve it. Do not approve the relationship by quietly replacing “partial” with “checked.”
Keep a small, readable onboarding packet
Save the original result, the proposed network and wallet, the customer reference and the date of review. Paid A2 Route checks can include a PDF report. The report walkthrough explains the sample fields before you build an archive around them. Keep supporting documents and correspondence in your own case file, with access appropriate to their contents.
Add a short reviewer note: what was checked, which finding needed attention, what explanation arrived and what decision followed. Name the reviewer and any person who approved an exception. “Checked, okay” is too thin to explain why an onboarding decision was reasonable on the evidence available at the time.
Suppose a synthetic training file records an indirect exposure and an unresolved sending arrangement. A useful note says onboarding remains pending while the reviewer confirms that arrangement. It does not say the customer is guilty, and it does not say the funds are clean. Keep the result and the business action as separate statements.
Make the first payment a separate checkpoint
Onboarding acceptance does not approve every future transfer. Compare the actual first payment with the agreed sender, network and invoice, then follow your receiving workflow. If the customer changes wallets, record the change and review the new subject instead of attaching the original wallet result to it.
For a flagged result, use the counterparty review steps. For an eventual supplier-payment leg, read the A2vanta business payment blog separately. Start a supported A2 Route check or consult the API documentation. Screening is an informational tool, not legal advice, a clean-funds certificate or a promise of regulatory compliance.