> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/get-started.md).

# Get Started

## Compatibility <a href="#compatibility" id="compatibility"></a>

<table><thead><tr><th width="128.80859375"></th><th width="277.578125">Supported Range</th><th>Notes</th></tr></thead><tbody><tr><td><strong>Unity Editor Versions</strong></td><td>Unity 2020.3 LTS → Unity 6.0 LTS</td><td>Unity versions older than 2020.3 LTS are not yet supported</td></tr><tr><td><strong>Build Target Platforms</strong></td><td>Android</td><td>iOS, Desktop(Windows/Mac/Linux) support coming soon</td></tr><tr><td><strong>Screen Resolutions</strong></td><td>1280x720 → 2960x1440</td><td>All aspect ratios supported by Android</td></tr></tbody></table>

## Getting Started

Before integrating, complete the following setup steps

## Create Title & Set Up Payments (skipped for internal beta testing) <a href="#id-2.1-create-title-and-set-up-payments" id="id-2.1-create-title-and-set-up-payments"></a>

**Create Title** and **Set up payments** in the [Coda Publisher Portal](https://portal.coda.co/dashboard). This ensures your project has valid API credentials and is linked to the correct merchant account. Follow the steps mentioned [here](https://coda-payments.gitbook.io/coda-private-technical-documentation/~/changes/794/codapay/getting-started/set-up-payments).

## Configure Merchant URLs & Payment Channels (skipped for internal beta testing) <a href="#id-2.2-configure-merchant-urls-and-payment-channels" id="id-2.2-configure-merchant-urls-and-payment-channels"></a>

From the Coda Publisher Portal, complete [Sandbox Configuration](https://coda-payments.gitbook.io/coda-private-technical-documentation/~/changes/794/codapay/integration-guides/testing-guide/sandbox-configuration):

* **Merchant URLs** (landing page, notification, etc.)
* **Payment channels** you want to enable on the Coda Payment Page.

## Prerequisites of Unity Project (skipped for internal beta testing)

Before integrating the SDK, ensure your development environment meets the following requirements:

**Supported Platform**

* Unity (2020.3 or later)
* Android

**Android Build Support (via Unity Hub)**

* ✅ OpenJDK
* ✅ Android SDK & NDK Tools
* ✅ Minimum SDK version: 26

Once you are ready with all the Prerequisites, you can follow the [Integration Guide](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide.md) to integrate our Unity SDK with your Unity project.

{% hint style="info" %}
For the internal beta testing, you can skip this "Prerequisites of Unity Project" section as this part has been already covered by [Development Environment Setup Before Internal Beta Testing](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/development-environment-setup-before-internal-beta-testing.md) page.
{% endhint %}


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.coda.co/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/get-started.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.