KYC and AML Policy Overview for Canada
Stake’s Know Your Customer (KYC) and Anti-Money Laundering (AML) Policy outlines the verification and compliance standards applied to all account holders in Canada. The policy supports adherence to applicable regulatory requirements, helps prevent fraud, and confirms user identity before withdrawals or certain transactions are processed. It reflects a continued commitment to user safety, account protection, and transparency across the platform, in line with Canadian financial compliance obligations.
Purpose of KYC and AML Compliance
KYC and AML procedures exist to protect the platform and its users from financial crime, including money laundering, terrorist financing, and identity fraud. These procedures allow Stake to confirm the identity of each account holder, verify the legitimacy of funds, and detect unusual account activity before it becomes a compliance issue. For users in Canada, this framework supports adherence to federal AML legislation, including obligations under the Proceeds of Crime (Money Laundering) and Terrorist Financing Act (PCMLTFA). Fraud prevention, regulatory compliance, and platform security remain the core objectives of this verification framework.
Identity Verification Requirements (KYC Process)
Account holders in Canada may be asked to complete an identity check at various stages of platform use, including before the first withdrawal, when account activity triggers a compliance review, or when updated regulatory requirements apply. Document submission is typically requested through the account verification centre and reviewed within a standard processing window.
Accepted documents for ID verification include:
- Valid passport;
- National identity card;
- Provincial or territorial driver’s licence;
- Proof of address, such as a utility bill or bank statement issued within the last three months;
- A selfie photograph holding the submitted identification, where requested.
Verification requests are communicated directly through the account holder’s registered contact details.
AML Monitoring and Risk Controls
Transaction monitoring forms part of the ongoing compliance framework applied to accounts in Canada. Deposits, withdrawals, and betting patterns are reviewed against established risk indicators to detect suspicious activity, including unusual transaction volumes, rapid fund movement, or patterns inconsistent with typical account use.
Where a transaction or account activity raises concern, additional verification may be requested, and access to certain account functions may be limited pending review. Stake maintains reporting obligations to relevant Canadian authorities, including FINTRAC, where suspicious activity meets the threshold for disclosure under applicable AML legislation. These controls support fair play and platform integrity for all users.
User Responsibilities Under KYC/AML Rules
Account holders in Canada share responsibility for maintaining compliance with KYC and AML standards. Cooperation with verification requests supports faster review times and uninterrupted account access.
Responsibilities include:
- Accurate and current personal data must be provided at registration and whenever account details change;
- Valid, unaltered documents must be submitted when a verification request is issued;
- Identity check requests must be answered within the specified timeframe;
- Another person’s identity, payment method, or account credentials must not be used;
- Unauthorized account access must be reported without delay.
Failure to meet these obligations may result in withdrawal delays, account restrictions, or closure.
Data Protection and Document Security
Personal data and documents submitted during identity verification are handled under strict security measures designed to protect account holders in Canada. Information is stored on encrypted servers, with access limited to authorized compliance personnel who require the data to complete verification or reporting obligations. Documents are retained only for the period required under applicable regulatory requirements and are not shared with third parties beyond what is necessary for compliance, fraud prevention, or legal disclosure. These practices support account protection, user safety, and continued trust in the verification process.
Updated: