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.
Collect the fields required by the transaction in front of the teller—not an indiscriminate form dump.
What it supports
The available rules are Canada/CAD-oriented branch rules, not a selectable global rule library. The business remains responsible for local KYC obligations.
Keep the people, purpose, and parties connected to a transaction in one operational record.
What it supports
The compact beneficiary record links to an existing customer but does not duplicate every KYC field. Staff remain responsible for reviewing the linked records.
Reduce retyping while keeping document review and final acceptance with trained staff.
What it supports
Barcode parsing reads supplied data; it does not authenticate a document or establish identity by itself.
Review parsed fields before use without creating new raw barcode-payload records from the active scanner flow.
What it supports
The current scanner does not transmit or persist new raw payloads. Historical raw-scan fields and access-restricted legacy logs still exist; parsed fields remain subject to retention controls.
Record phone-verification status and send a customer review message from the transaction workflow.
What it supports
Contact verification is an operational marker, not proof that the person controls an identity.
Screen customer names against maintained sanctions and internal decision lists before the transaction proceeds.
What it supports
A name match is a review signal, not proof of identity. Automated beneficiary blocking is not included in the available-now claim.
Check destination addresses against internal decisions, with an optional public abuse-report lookup.
What it supports
External public-report lookup is integration-dependent. Any report or third-party label is an indicator, not proof of ownership or wrongdoing.
Apply Canada/CAD-oriented transaction bands and rolling customer-volume checks to supported exchange directions.
What it supports
These rules are hard-coded, not a selectable global profile, and no crypto-to-crypto KYC rule is defined. The rolling volume check is not a claim of cross-session regulatory-report aggregation.
Keep unresolved controls visible in the teller workflow and enforce specific completion-time gates on the server.
What it supports
Server enforcement covers specific gates, not the entire dynamic KYC field matrix. Authorized humans remain responsible for the decision and rationale.
Surface repeat activity and fragmented customer histories for focused staff review.
What it supports
The current score is a bounded rules-based aid—not machine learning or complete fraud prediction. Profile merging is an operator tool, not a formal approval workflow.
Let staff flag a transaction, preserve its context, and route it into a human compliance queue.
What it supports
A flag records concern; qualified staff decide whether the legal reporting criteria are met.
Require the operational record to reconcile before a transaction is marked complete.
What it supports
Integrity checks validate recorded state; they do not independently validate the economic purpose of a trade.
Run a separate operational audit of transaction values and repository movements.
What it supports
This reconciliation service is separate from the unfinished Compliance > Audit screen. Its records are not claimed to be immutable or tamper-proof.
Turn completed transaction records into a reviewable Canadian reporting work queue.
What it supports
Candidate generation groups completed orders by customer within each closed session; it is not verified as cross-session regulatory 24-hour aggregation. The workspace does not file reports or prove regulator acceptance.
Keep review context beside the transaction and export the fields compliance staff actually need.
What it supports
Those separate records are not all included in the order export. Exports remain subject to access, retention, and disclosure controls; activity and access records are selective, not a complete or immutable ledger.
Give managers and administrators a defined sign-off step while keeping unresolved compliance events visible.
What it supports
These are stored operational records, not an immutable or tamper-proof audit ledger.
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 the counter. Designed for review.
