Concepts

Guild

A Guild represents your platform or game within GamerSafer. When you onboard with GamerSafer, a Guild is created for your organization. All players who verify their identity through your platform become members of your Guild.

Your Guild Token (used for API authentication) is scoped to your Guild — it can only operate on members and data within your organization.

Player and Guild Member

A Player is a GamerSafer account — a real, verified human identity. A Guild Member is the relationship between a Player and a specific Guild. The same person can be a member of multiple guilds (e.g., across different games that integrate GamerSafer).

When a player joins your guild, GamerSafer returns a guildMemberId — a unique identifier for that player within your guild. This is the ID you use in all subsequent API calls for that player: ban requests, re-authentication requests, report submissions.

Guild Invite

A Guild Invite is how a player joins your guild. Your backend creates an invite via the API (POST /guilds/invites), which returns a URL and a QR code. The player is redirected to that URL and completes the identity verification flow inside the GamerSafer app — document upload, facial scan, and liveness check.

Once the player completes the flow, GamerSafer sends a guildInvite webhook to your backend with the guildMemberId and the player's age group.

See Player Verification for the full flow.

Document Verification

Document verification confirms that a player has submitted and had a government-issued ID approved (e.g., RG, CNH, passport). This serves two purposes: identity confirmation and date of birth validation for age-gated features.

A player's document status is included in the guildInvite webhook payload and notified separately via the documentValidated / documentRejected webhooks. Once a document is verified, the status is stored — you do not need to re-verify a player's document on each session.

See Player Verification for the full flow.

Player Re-authentication

Re-authentication confirms that the person currently using the account is the same person who originally verified it. It uses a real-time facial liveness check triggered via a push notification to the player's mobile device.

Unlike document verification (which happens once during onboarding), re-authentication can be triggered at any time your platform requires it — before a withdrawal, before a high-stakes match, after a suspicious login.

Re-authentication does not require re-uploading documents. It checks the player's face against the one already on file.

See Player Re-authentication for the full flow.

Anti-Alt-Account (Identity Continuity)

GamerSafer's core value proposition is identity continuity: because verification is tied to biometric data (face + document), not just an account, it is not possible for a player to evade a ban by creating a new account. A banned identity cannot re-verify as a new player within your guild.

This also means that reputation reports submitted to GamerSafer survive account deletion requests. GamerSafer is legally required to delete accounts upon request, but retains enforcement records — so your platform's ban history is not lost if a player deletes their GamerSafer account.

See Report and Banning for how to submit bans and reports.