> For the complete documentation index, see [llms.txt](https://docs.elixir.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elixir.app/dashboard/in-app-purchases/developer/client-integration.md).

# Client Integration

## Implement SDK

{% hint style="danger" %}
**The integration and utilization of the Elixir SDK Auth constitute mandatory prerequisites for engaging with the In-App Purchases system.** Eligibility for leveraging the In-App Purchases system is contingent upon the association of Elixir accounts with respective internal accounts.
{% endhint %}

Following the creation of a store for your game and the upload of several products, the next step involves implementing the system within your game.

Initially, it is imperative to ensure the integration of [Elixir SDK](/sdk/unity/authentication.md). Only games with the Elixir SDK integrated will be granted access to the In-App Purchases system. This mandates the linking of the in-game user account to their Elixir Account. 

The build uploaded to Elixir needs to disable the option to log out. This measure is crucial to guarantee the security and reliability of the In-App Purchases system.

Once the Elixir SDK, including the account linking, is seamlessly integrated into your game, you are primed to commence the specific [overlay integration following the SDK docs](broken://pages/uSmjnXlGXVYKjv8UifZj#overlay-actions).

## Test your in-app purchases

For testing the In-App Purchases system within your game, our [SDK Events simulator ](broken://pages/uSmjnXlGXVYKjv8UifZj#event-simulator)facilitates the replication of overlay communication with the game. This approach enables the game to respond appropriately to each event, enhancing the overall user experience.

<figure><img src="/files/GeSf3mUAIF0OMM2UzkFp" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.elixir.app/dashboard/in-app-purchases/developer/client-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.