Client Acknowledgement (Consume)

This flow does not involve server-to-server communication. After a player completes a purchase, the publisher manually updates the player's balance in the game server and sends an acknowledgment to AppCharge.

In-Game Checkout Flow Explanation:

1. Player clicks to purchase:
   The player initiates a purchase by clicking on an offer in the in-game store. This action triggers the in-game checkout SDK to begin the payment process.
2. Create Checkout Session:
   The game server uses the SDK to request from AppCharge’s backend a session that contains all the details needed for opening the checkout. This session setup involves localization, tax calculations, and payment method preparation, all managed through server-to-server API calls.
3. Checkout Response:
   The SDK receives a response from the backend confirming that a checkout session has been successfully created. This response includes all the necessary information to proceed with the payment.
4. Consume:
   Once the player completes the purchase, the application sends an acknowledgment via the SDK to the AppCharge server. This indicates that the payment has been processed successfully. The game server will then need to acknowledge the order success by sending a confirmation back to AppCharge’s backend.
5. Balance Update:
   After the acknowledgment, the game server updates the player’s balance in the game.