> 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.md).

# Unity SDK Internal Beta Testing Introduction

Hello there, first of all thank you for participating in this internal beta testing program to improve our Unity SDK DevEx. This internal beta testing (dogfooding) event is aim to get feedback on how we can improve our integration flow and documentations.

**Here's the things that we want you to do:**

1. Setup the development environment: [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)
2. Clone our sample Unity base project from [here](https://bitbucket.org/codapayments/unity-sdk-base-integration/src/main/)
3. Open the project
   * In **Unity Hub**:
     1. Click **Add → Add project from disk**
     2. Navigate to the cloned sample app folder
     3. Select the project and open it in the installed Unity version
   * **Verification**: The project should be loaded with the **Default View** as shown in below image, 

     * If you see some different view or  `"Rebuilding Library because the asset database could not be found!"` message in the console, complete the project setup as shown following:

       * From the top menu bar, Go to **Tools -> Project Setup -> Check Setup Status** to check the setup status
       * Once it gives `"[ProjectSetup] Setup Status - Done: True, In Progress: False, Running: False, Project Opened: True"`  message in the console, Go to **Tools -> Project Setup -> Reset Setup Flags** to reset the project setup flags and Run Force Setup.
       * Running Reset Setup Flags should show `"[ProjectSetup] Setup flags have been reset."`  message in the console
       * Now Go to **Tools -> Project Setup -> Force Setup Now** and wait till setup process gets completed. You should be able to see the default view required for verification. 

       **Default View :**

     <figure><img src="/files/HvjgHF8O8DXhzt6f9Sn3" alt=""><figcaption></figcaption></figure>
4. Integration with our Unity SDK
   1. Follow [Get Started](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/get-started.md) using credentials shared with you separately
   2. Testing on QA environment by following [Test on QA for Internal Beta Testing](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/test-on-qa-for-internal-beta-testing.md)
   3. Test both **hosted payment page** and **card form** on an emulator or a physical device
   4. Save the screenshots or videos of the successful transactions
5. Give us the feedback on developer experience [here](https://docs.google.com/forms/d/1WcvYPPRcD0BhzV_8YbE8c7NGqTYskrvwXFir0daxzGs)


---

# 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.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.