Source-backed platform inventory
This inventory describes behavior found in current Trading Tool source paths—not roadmap language. Every capability includes the boundary buyers and compliance teams need to know.
YS-0184 · Synthetic case
This fictional trace shows how available Trading Tool controls can connect during a review. It is an explanatory sequence, not a claim that every jurisdiction or workflow uses the same configuration.
Direction, current value, and rolling 24-hour volume determine which customer information the workflow requires.
Customer-screening signals, sanctions and blacklist results, wallet indicators, and stored beneficiary context are brought into view. That context does not imply active automated beneficiary screening or blocking.
The workflow surfaces incomplete requirements. Server-enforced blocking flags and specific completion checks prevent completion until an authorized person resolves them.
Transaction identifiers, notes, reviewer comments, and exportable records support later review and report preparation.
Collect the fields required for the transaction in progress—not an indiscriminate form dump.
Keep the people, purpose, and parties connected to a transaction in one operational record.
Reduce retyping while keeping document review and final acceptance with trained staff.
Review parsed fields before use without creating new raw barcode-payload records from the active scanner flow.
Record phone-verification status and send a customer review message from the transaction workflow.
Screen customer names against maintained sanctions and internal decision lists before the transaction proceeds.
Check destination addresses against internal decisions, with an optional public abuse-report lookup.
Apply Canada/CAD-oriented transaction bands and rolling customer-volume checks to supported exchange directions.
Keep unresolved controls visible in the transaction workflow and enforce specific completion-time gates on the server.
Surface repeat activity and fragmented customer histories for focused staff review.
Let staff flag a transaction, preserve its context, and route it into a human compliance queue.
Require the operational record to reconcile before a transaction is marked complete.
Run a separate operational audit of transaction values and repository movements.
Turn completed transaction records into a reviewable Canadian reporting work queue.
Keep review context beside the transaction and export the fields compliance staff actually need.
Give managers and administrators a defined sign-off step while keeping unresolved compliance events visible.
Current Canada/CAD-oriented rules
Trading Tool currently applies hard-coded Canada/CAD-oriented branch rules to fiat-to-fiat, fiat-to-crypto, and crypto-to-fiat flows, using transaction bands and rolling 24-hour customer-volume checks. No crypto-to-crypto KYC rule is currently defined. These controls support operations; they are not a selectable jurisdiction library and do not transfer legal responsibility away from the reporting entity.
Official guidance referenced for these Canada/CAD-oriented rules
Thresholds and duties can change. Qualified local compliance staff must confirm the rules that apply at implementation and filing time.
Built for high-stakes transfers. Designed for review.
