> 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/integration-guide/test-on-qa-for-internal-beta-testing.md).

# Test on QA for Internal Beta Testing

Once you complete integration in the given sample Unity base project, you can Test the following payment flow with the given test details:

1. **Testing Card Form Flow:** 

   For testing card form flow set TestCodaSDKHandler,

   ```
   Country Code: Coda.CountryCode.US,
   Currency Code: Coda.CurrencyCode.USD
   ```

   and hit <img src="/files/Hapa9E065q4nuTXqGwto" alt="" data-size="line"> button to test inside Unity Editor or follow [Create Android Build](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/create-android-build.md) steps to create a build and test on physical device or android emulator. Use Test card details as following at the time of testing the card payment flow in the game window: &#x20;

   ```
   Card Number: 3400 000000 01098
   Expiry: Any valid future date
   CVC/CVV: Any 4-digit
   OTP: 1234
   ```

   <figure><img src="/files/f7QT5vEAwa5U3m2H2mxb" alt=""><figcaption></figcaption></figure>
2. **Testing Hosted Payment Page Flow:**&#x20;

   For testing hosted payment page flow set TestCodaSDKHandler,&#x20;

   ```
   Country Code: Coda.CountryCode.ID,
   Currency Code: Coda.CurrencyCode.IDR
   ```

   and hit <img src="/files/Hapa9E065q4nuTXqGwto" alt="" data-size="line"> button to test inside Unity Editor or follow [Create Android Build](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/create-android-build.md) steps to create a build and test on physical device or android emulator. Use Test details as following for testing "Tri Indonesia" payment channel: &#x20;

   ```
   Phone Number: 089643927109
   OTP: 7777777
   ```

   <figure><img src="/files/3Vu2itrqxPhogj7WIQL6" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The complete hosted payment page flow will work with physical device or android emulator. Inside Unity Editor, the flow will work till you complete the transaction and see the Payment Successful screen only. The flow to return back to the origin after clicking "Back to Unity Test/ Kembali ke Unity Test" will work with physical device or android emulator, not inside Unity Editor.
{% 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/integration-guide/test-on-qa-for-internal-beta-testing.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.