Fair play & cheating prevention

Both players commit entry-fee value (Competition Credits) to escrow before the match goes active. Escrow is competition hold, not a bank account or custodial balance. The pot is real on-platform before you queue, which reduces last-minute payment gamesmanship.

Challenges and accepts are tied to the real match on the supported platform: live game links, linked operator accounts, and any other fields that title requires. Depending on the integration, we may use a browser extension, official APIs, or both so players and match context line up with the wager before funds settle on automation.

When you link an account for a supported title, WagerMe applies that integration’s quality rules using public signals the platform exposes, commonly minimum account age and a minimum amount of on-platform play. Exact numbers differ by game and can change as we tune risk. That keeps brand-new throwaways out of money matches and gives each operator time to collect history, run its own integrity checks, and enforce standing or fair-play policies. We do not replace those systems; we add a floor so their tools have room to work.

Self-serve linking may ask you to prove control of a public profile when the platform exposes the right signals to us, for example a short, time-bound phrase you place in public profile text and then remove after success. Where that style of proof is not available from the API, linking relies on username validation plus that title’s quality rules; use support for access issues or edge cases. A given platform identity can only be linked to one WagerMe account per title, and swapping a saved link from the dashboard is intentionally limited. Contact support when a change is warranted. If you join a wager that already specifies your in-game identity for that title, we may record the link at accept time without repeating an extra proof step.

Titles that ship with our browser extension can observe the official match surface in your session. Results are derived from what the platform shows as finished, not from a self-typed score, and are sent to WagerMe with supporting context (including screenshots where we capture them) for verification and dispute review. Other integrations use whatever official read path that game supports; the principle is the same: settlement follows platform-visible outcomes, not vibes.

When the game state is unambiguous and matches the wager, we move toward automatic verification so winners get paid quickly. When something does not line up, the wager can be held for review instead of silently paying the wrong side.

If players disagree on the result, WagerMe provides a dispute flow where both sides can submit evidence. Our team can review timelines, submissions, and game metadata to reach a resolution. That is your backstop when automation alone is not enough.

We apply jurisdiction checks where wagering is offered, enforce platform rules, and use identity verification where required for payouts and risk. That stack supports fair outcomes and reduces abuse of the financial layer, alongside the technical checks above.