Skip to main content
To launch the checkout, follow these steps:
  1. From your server, call the Create Checkout Session API to create a checkout session.
    • When calling the Create Checkout Session API, don’t pass the redirectUrl parameter. The SDK already handles the redirect automatically using the configuration file.
    • Call the API from your server to ensure session integrity and security. Never invoke this endpoint from your client-side code.
  2. After receiving the API response on your server, extract the values from the session object:
  3. Use the values returned in the Create Checkout Session API response to open the checkout on the client, and pass your player’s customerId. The SDK uses this ID with the session purchaseId to validate the order if the player closes the browser during checkout and later returns to the game. It also identifies the correct player when multiple players share the same device.
    The session response values must be passed exactly as received. Modifying them may result in the checkout failing to load.
  4. You can also configure how the checkout page is opened (optional):
    • External browser
      Open the checkout in the device’s default browser. This flow will use the redirectUrl provided in the initialization to return back to the app.
      Running the checkout in an external browser may cause inconsistent behavior across devices, incomplete transactions, or app unexpected lifecycle behavior.
    • Non-external browser (default)
      The checkout opens in the device’s internal browser or SFSafariViewController. This flow will use the url scheme provided in the plist file to return back to the app. For more information, see Sell Outside IAP.