Open the SafeReceive pilot
Run the controlled ALLOW, REVIEW and BLOCK scenarios and generate a comprehensive report.
Incoming check
Setdirection to incoming. Cardinal treats from_address as the source of funds and to_address as the receiving wallet.
Response requirements
SafeReceive keeps the normal risk response and adds:screening.directionto confirm incoming evaluationscreening.subject_addressto identify the screened sourcescreening.provider_modeto distinguish local, external-ready, and degraded resultsscreening.evidencewith category, severity, confidence, source, and freshnesspolicy.matched_rulesto explain the final action
Investor-demo scenarios
The reserved BLOCK scenario demonstrates three synthetic evidence categories: stolen-funds exposure, sanctions-list exposure, and illicit-service association. Each record includes a Cardinal demonstration reference, confidence, severity, and observation time. Do not represent this controlled fixture as a claim about a real person, business, bank account, or wallet.
Comprehensive Risk Report
After a payment check, an authorised partner can generate a separately metered, immutable report linked to the originalrequest_id.
- the screened source wallet and incoming-payment details
- the original decision, risk score, and check time
- findings and matched policy rules
- named evidence sources, confidence, freshness, and references
- a source-of-funds and exposure-path summary when the approved evidence supports one
- attributed exchange, custodian, service, or institution details with role, jurisdiction, verification state, address, and supporting reference
- provider coverage and transaction-effects mode
- methodology and limitations
Institution and bank-origin evidence
Blockchain activity does not normally reveal a customer’s bank account or bank name. Cardinal must not infer one from a wallet address alone. The report may display a named exchange, custodian, payment service, financial institution, or other entity only when an approved source supports the attribution. Suitable sources can include licensed intelligence, verified counterparty data, Travel Rule data, customer-supplied source-of-funds documents, or a confirmed business record. Each attribution should show:- entity name and type
- role in the payment path, such as origin, intermediary, exchange, custodian, or destination
- verification status and confidence
- jurisdiction and identifiers when the source permits them
- attributed blockchain address or transaction reference
- evidence source, reference, observation time, and freshness

