> 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/integration-guides/integration-checklist.md).

# Integration Checklist

Use this checklist to ensure a smooth and complete integration of Codapay into your system. Following these steps will help you avoid common pitfalls and ensure that all necessary configurations are in place for a successful launch.

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

### 1. Review Documentation and Plan Integration

#### Review Integration Types

* Understand the differences between Hosted Payment Page and Backend API integrations.
* Decide which integration type suits your business needs (refer to "[Choosing the Right Type of Integration](/codapay/integration-guides/choosing-the-right-type-of-integration.md)" for guidance).
* Decide which Codapay API version to use (refer to "[Codapay API Versions](/codapay/integration-guides/codapay-api-versions.md)" for guidance).

#### Technical Resource Availability

* Ensure you have the necessary technical resources available to implement and maintain the chosen integration type.

### 2. Setup and Configuration

Follow the [Getting Started](/codapay/getting-started.md) guide for detailed steps on setting up API credentials, configuring redirect URLs, activating payment channels, and environment configuration.

### 3. Integration

Refer to the [Getting Started](/codapay/getting-started.md) guide and the rest of the API documentation for detailed instructions on implementing the [Hosted Payment Page](/codapay/hosted-payment-page-integration.md) and [Backend API](/codapay/direct-api-integration.md).

### 4. Testing

#### Merchant Account Status

* Verify that your merchant account is in "Testing" status during sandbox testing.
* Upon successful completion of sandbox tests, request Codapay Support Team to change your account status to "Active".

#### Sandbox Testing

* Conduct thorough testing in Coda’s Sandbox Environment.
* Test all possible scenarios, including successful transactions, failures, and edge cases.

### 5. Pre-Launch Preparation

#### E-Annex Approval

* Inform Coda’s Partner Business Team once testing is complete in the sandbox environment.
* Complete the payment channel E-Annex approval process.

#### Production Configuration

* Configure the redirect and callback URLs for the production environment
* Please inform the Codapay Support Team once you have completed the configuration. Additionally, kindly provide the following information:

- [x] The request currency (USD or local currency)
- [x] The request payType (0 or payment channel ID)
- [x] Are you using [InquiryPaymentResult](/codapay/hosted-payment-page-integration/check-a-transaction-status.md) endpoint?
- [x] Integration methods (Webview / External Browser / PC Client)

#### Production Environment Testing

* After activating E-Annex, conduct tests in the production environment.
* Ensure the payments function correctly with real transactions
* If you require assistance from Coda for testing, please share the following details:
  * APK **or** Top-up Website URL
  * Game account ID **or** app login ID and password
  * Denomination (Lowest available denomination)

{% hint style="info" %}
Codapay Support Team operates from **9AM to 6PM SGT, Monday - Friday**. Please provide ***1 business day prior notice*** to allocate resources and manpower accordingly.
{% endhint %}

#### Final Checks

* Ensure all front-end implementations adhere to Coda’s Brand Guidelines.

### 6. Launch

Contact Codapay Support Team to confirm all integrated channels are ready for launch, including those requiring pre-approval and inform them of your launch date so that they can help monitor.

### Who to contact for help

<table><thead><tr><th width="188.33333333333331">Team</th><th width="202">Email</th><th>Responsibilities</th></tr></thead><tbody><tr><td>Technical Support Team (24/7)</td><td>partnersupport@coda.co </td><td><ol><li>Transaction check</li><li>Refund request</li><li>Payment channel outage</li><li>Failed to login Publisher Portal</li></ol></td></tr><tr><td>Partner Business Team</td><td>publisher_team@coda.co</td><td><ol><li>Transaction conversation rate</li><li>New channels available</li><li>Financial inquiries</li><li>Create new Publisher Portal account</li><li>Issues related with VAT</li></ol></td></tr><tr><td>Codapay Support Team</td><td>codapay_integration@coda.co</td><td><ol><li>Production Testing request</li><li>Resetting Publisher Portal account</li><li>FTP/S or SFTP report</li><li>Renotify Codapay transaction</li><li>Error codes not listed in this document</li></ol></td></tr></tbody></table>


---

# 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/integration-guides/integration-checklist.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.