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

# Integration Guide

Once you have the setup done on Publisher Portal, all the required credentials and Prerequisites of Unity Project ready you can follow this step-by-step Integration Guide to quick start your In-App payments journey with Coda.

## Integration with the SDK

Here is the simple step-by-step process for completing SDK Integration and get the working android build ready for the testing:

1. [Install SDK](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/install-sdk.md)
2. [Configure SDK](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/configure-sdk.md)
3. [Setup for SDK Initialization](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/setup-for-sdk-initialization.md)
4. [Register Callback Events](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/register-callback-events.md)
5. [Initiate Payment](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/initiate-payment.md)
6. [Customize UI](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/integration-guide/customize-ui.md)
7. [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)

Follow the steps given at [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) page to test the Card form flow and HPP payment flow.

You can checkout our [Troubleshooting](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/troubleshooting.md) page if you bump into few common issues.

You can also check out our [Demo Project](/codapay/in-app-payments/unity-sdk-internal-beta-testing-unity-native-integration/unity-sdk-internal-beta-testing-introduction/demo-project.md) to get more insights around how our SDK works.


---

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