Overview

Appcharge offers a comprehensive Player Authentication system that integrates seamlessly with the existing login methods in your game, as well as an OTP (One-Time Password) option. This unified approach allows players to authenticate securely and conveniently, enhancing their overall experience in the webstore.

Note: Configure Player Authentication via the Player Authentication Webhook in the API reference page.

Benefits

Appcharge supports a variety of secure authentication methods, including popular platforms like Facebook, Google, and Apple, as well as OTP, enabling players to log in with familiar options and adding an extra layer of security and convenience.

High-Level Configuration Flow

1. Decide on Authentication Methods

Start by identifying which authentication methods you want to offer from the following:

• Google
• Apple
• Facebook
• Username and Password
• Player ID
• OTP (One-Time Password)

2. Review Documentation for Each Method

Refer to the specific documentation for each chosen method to get step-by-step instructions on configuration. You will need to save certain information required for setup in the Appcharge dashboard.

• Configure Google SSO login
• Configure Apple SSO login
• Configure Facebook SSO login
• Configure Player ID login
• Configure Passwordless OTP login

3. Configure in the Dashboard

Navigate to the Authentication Page in the Publisher Admin Dashboard to start configuring the Player Authentication settings. There, you'll be able to select and enable the authentication methods you wish to support and add the relevant information you saved as instructed in the relevant methods configuration documentation.

• Access the Authentication Page documentation for the Publisher Admin Dashboard

4. Validade with Player Authentication Webhook

After setting up the authentication methods, link the entire process to the Player Authentication Webhook to enable secure handling of authentication data.

Authentication Flow:

1. Player Chooses an Authentication Method
   The player selects their preferred authentication method (e.g., Facebook, Apple, Google, Username/Password, OTP). Appcharge utilizes the corresponding App ID (for Facebook), client ID (for Apple), or client_id (for Google) on the frontend to obtain the client token.
2. Token Handling
   Appcharge supports both response type codes and id_token functionalities for Facebook, Google, and Apple logins.
   Note: The default configuration for Apple login uses the response type code. If you prefer to utilize the id_token functionality, please contact our support team for assistance.
3. Webhook URL Configuration
   Ensure that the webhook URL is correctly set up in the Appcharge management dashboard. This is critical for receiving authentication notifications.
4. Dashboard Configuration for App IDs
   Input the relevant App IDs for each authentication method in the dashboard settings. This allows Appcharge to validate and handle authentication requests appropriately.
5. Server Communication
   After successful authentication, the player's login details (including tokens) are sent to the game server for validation and processing.
6. Response and Player Data Retrieval
   Once the server processes the authentication, it returns a detailed response containing:
   • Whether the player is valid (authenticated).
   • Publisher Player ID: A unique identifier assigned to the player by the publisher.
   • Player Name: The name associated with the player's account.
   • External Profile Picture: A link to the player’s profile image.
   • List of currencies and their balances: Relevant financial data for in-game transactions.

Supported Authentication Methods:

• Facebook App
• Google App
• Apple App
• Username and Password
• One-Time Password (OTP)

Reference to FB, Apple, and Google Auth Documentation:

1. Facebook: Frontend guide | Backend Guide.
2. Apple: Guide for Token Generation and Validation.
3. Google: Guide to Verifying Google ID Tokens.

📘

For Password-less (OTP) player authentication method please visit: OTP Authentication