Overview

AppCharge offers a comprehensive Player Authentication system, supporting all the major login methods you already use in your game, making them available in the AppCharge web store as well.

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

Supported Authentication Methods:

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

Authentication Flow:

1. The player chooses an auth method (FB, Apple ID, Google ID, etc.) and authenticates themselves. Appcharge uses the provided App ID (FB), clientId (Apple), and client_id (Google), etc., on its frontend to get the client token. We also support internal user token, user name, and password authentications.
2. Appcharge supports FB, Google, and Apple logins with both response type codes and idtoken functionalities.
   Note: Appcharge uses, by default, the response type code for Apple login. In order to use idtoken, please let us know.
3. The webhook URL is configured in Appcharge’s management dashboard.
4. The App ID per auth method is configured in the dashboard.
5. The auth details are sent to the game server.
6. A response is returned containing the following player details:
   1. Valid player or not.
   2. Publisher Player Id.
   3. Player Name.
   4. External Profile Picture.
      v.List of currencies and their balance.

Reference to FB, Apple, and Google Auth Documentation:

1. FB FE, FB BE.
2. Apple.
3. Google.

📘

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