Compliance program overview

1. Know Your Customer (KYC) and identity verification

• Provider and method: Identity verification is performed using Stripe Identity with government-issued document capture and a matching selfie (liveness / presentation attack resistance as provided by that product).
• Prerequisites: Users must have a verified email address before starting a verification session, so we can bind outcomes and notices to the correct account.
• When verification is required:
  • Winnings withdrawals: Identity verification must reach an approved outcome before any Winnings withdrawal is processed for payout. In practice, review can add on the order of hours up to about two days. This filters high-risk accounts and aligns with chargeback prevention.
  • Deposits in certain regions: Where regional rules flag KYC as required for your location, approved verification is required before you can add funds from that location.
  • Match actions: Creating or accepting wagers and joining matchmaking use your coordinates to enforce enabled regions and maximum stake rules. Those flows do not repeat the deposit-time KYC check on every action; if your region requires KYC to deposit, you must complete verification before you can fund and then stake from that location.
• Outcomes: Submissions are stored with a status (for example pending, processing, approved, rejected). Automated updates are applied from the identity provider where configured; administrators may perform additional review where appropriate. Users receive notices when practical after approval or rejection.
• Accuracy: You must provide truthful information and may not use another person's identity or documents.

2. Anti–money laundering (AML) and financial crime controls

WagerMe operates a risk-based approach to financial crime prevention, scaled to its products and partnerships.

• Payments partner: Deposits and withdrawals are processed through a qualified payment processor (and its applicable programs). Card and bank movements are subject to the processor's own compliance, fraud screening, and regulatory obligations.
• Ledger and records: User-facing balances are represented on an internal double-entry style ledger (deposits, withdrawals, escrow holds and releases, payouts, fees). Records support reconciliation, dispute handling, and lawful requests.
• Monitoring and review: We apply technical and operational controls (including velocity limits on sensitive actions, login history signals, and manual review workflows for disputes and abuse) to detect unusual activity. Accounts or withdrawals may be delayed or blocked while risk or legal review runs, consistent with the Terms.
• Reporting: Where the law requires reports to authorities (for example suspicious activity reporting in applicable jurisdictions), WagerMe or its partners will make filings as required. We cooperate with lawful requests from regulators and law enforcement.
• Prohibited use: You may not use the Platform to launder proceeds of crime, structure transactions to evade reporting thresholds, or conceal beneficial ownership.

3. Age verification

• Minimum age: The Terms require users to be at least 18 years old (or higher where we state a stricter floor for your jurisdiction).
• How age is supported: Government ID submitted through Stripe Identity is used to confirm identity, which typically includes date of birth verification as returned by the identity product.
• Regional configuration: Internal region rules can record jurisdiction-specific minimum ages (for example 21 where applicable). Those values inform policy and operations; continued access is conditioned on meeting eligibility in the Terms and any in-product notices.

4. Geofencing and location eligibility

• United States focus: Wagering features are intended only for users physically located in the United States within states or regions the Platform has enabled for play.
• How location is checked: The client supplies coordinates at key moments (for example creating or accepting a wager, joining matchmaking, and funding flows). The server resolves coordinates against US state boundaries and applies per-region rules (enabled flag, maximum stake size, KYC flag, and documented minimum age).
• No continuous tracking: We do not continuously track your device in the background for geofence purposes; checks occur when you perform an action that sends location. See the Privacy Policy for how location data is handled.
• Circumvention: VPNs, spoofed coordinates, or other attempts to defeat location checks violate the Terms and may result in closure, forfeiture where permitted, and referral to partners for fraud.

5. Payouts, withdrawals, and fund segregation (product model)

• Not a bank: Balances are ledger-based competition value, not bank deposits. See the Terms for the entry-fee model.
• Competition Credits vs Winnings: Deposits credit as Competition Credits for staking. After settlement, winning value moves to a separate Winnings Balance. A platform fee applies on payouts as disclosed in the app.
• Playthrough: Entry-fee amounts are subject to skill-competition playthrough before related value becomes withdrawable as Winnings, as shown in the product.
• Withdrawal rail: Withdrawals are sent through our payment processor to a linked card or bank method. The name on your WagerMe account should match the payout method holder. Network and processor fees are shown at submission time where available.
• Holds: Disputes, fraud review, chargebacks, or risk holds may delay or block withdrawals until resolved through in-app flows, support, or the dispute process described in the Terms.

6. Fraud protection and withdrawal timing

Withdrawal timing is designed around fraud prevention and chargeback defense, not around delaying access to money for its own sake. Exact clocks and limits are shown in the product and Terms; the bullets below describe the policy intent.

• Anti-fraud hold after deposit: Where a withdrawal would draw on funds whose source deposit is newer than about seven days, we may keep the request in a pending state for roughly 24 to 72 hours. This is standard industry practice: it gives card networks and our risk tools time to surface fraud and defines a practical chargeback defense window.
• KYC before payout movement: No Winnings withdrawal is processed for payout until identity verification is approved. That gate typically adds from near-zero up to about 48 hours depending on volume and manual review, and it screens out many bad actors who would otherwise drive chargebacks.
• Processing windows and batching: Outbound transfers may be batched (for example one to two times per day) rather than streamed in real time, so analysts can flag patterns such as deposit then immediate withdrawal (card testing, layering, or stolen-instrument abuse). Large regulated consumer platforms often quote on the order of one to five business days; we are not an outlier by explaining multi-step timing up front.
• Tiered rails by funding age and source: Value tied to deposits older than about thirty days or credited from won competition (as opposed to freshly deposited entry-fee value) may qualify for faster settlement rails where we offer them. Fresh deposit-related withdrawal paths use the standard anti-fraud hold. The design rewards engaged play and dampens "fund and immediately cash out" behavior.
• Caps for new accounts: For roughly the first thirty days on the platform (or another onboarding window we disclose in the app), daily and weekly withdrawal caps may apply, often scaled to a multiple of the largest single deposit we have seen on the account. That limits loss exposure during the highest-risk onboarding window.

7. Other relevant controls

• Email verification: Required for certain flows (including starting KYC) to reduce account takeover and misdirected notices.
• Rate limiting: Sensitive endpoints use rate limits to reduce abuse and credential stuffing risk.
• Session security: Authenticated sessions use signed tokens; refresh token rotation and revocation support logout and compromise response.
• Disputes and fair play: Structured dispute and evidence flows, plus admin resolution where the product provides it. See Fair Play.
• Responsible gaming: See Responsible Gaming for self-help and limits messaging.

8. Contact

Questions about this overview or accessibility of policies: use Support or the contact options listed on the site.