> 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/codapay-integration-faq/hosted-payment-page-api/pre-integration.md).
# Pre-Integration
1. **Where is the API Key?**
Publisher Portal -> Integration -> Codapay -> API Keys
New merchants:
* You will get Global API keys, which can only be used with Codapay v2.0 APIs. Please refer to [Codapay API Versions](/codapay/integration-guides/codapay-api-versions.md) for details.
Existing merchants:
* Each game or platform that you integrate (known as a "title") will have one set of API keys, and each country's API key is separate.
* If you need to open a new account in a different country, please inform Coda Business to create a new API Key for that country.
* Current API keys can only be used for Codapay v1.0 APIs. If you want to use Global API keys for simplified integration effort and key management, please reach out to Coda. This would require a simple migration to Codapay v2.0 APIs where the core structure is unchanged from v1.0 APIs.
New merchants' view
Existing merchants' view
***
#### 2. Is the API Key used in the sandbox and the production environment the same?
New merchants, using Global API key: No, sandbox and production have different API keys.
Existing merchants: Yes, the API key is the same in both environments.
***
#### 3. What currency can I use?
Merchants can choose to use Local Currency or US dollars. If US dollars are requested, the Coda System will automatically convert and display the local currency to the user on the payment page.
* For more details on US dollars, please refer to [Initiate USD Transactions](/codapay/hosted-payment-page-integration/initiate-usd-transactions.md)
***
#### 4. Where is the Payment Channel Price List and each payment expiration time?
* Price Limits: Check them [here](/codapay/integration-guides/price-limits.md)
***
#### 5. Will `items.code` in `initRequest` be included in the callback (PaymentNotification)?
No. This value will not be returned in the callback. For further information, please refer to [Get notified of a transaction status change](/codapay/hosted-payment-page-integration/get-notified-of-a-transaction-status-change.md)
***
#### 6. If I pass custom parameters (e.g., `game_id`) in the request, will they be recorded or returned?
No. Any extra or custom parameters will not be recorded or included in the callback or Coda system.
***
#### 7. I don't have a local wallet/account, any testing credentials I can use in the Sandbox environment?
Some payment channels support simulations with a virtual wallet, mobile phone number, or card number or using Coda's simulator to complete the Sandbox test.
However, some channels are "**NOT**" supported by sandbox testing, merchants just need to ensure that the payment page can be successfully pulled in the sandbox environment. [Payment Channel Sandbox Guide](/codapay/integration-guides/testing-guide/payment-channel-testing-instructions.md)
***
#### 8. Why did I receive error code 225?
The payment channel has not been activated.
* If legal approval is done, log in to `Coda portal` > `Payment methods` > `Approve` to activate the channel.
* For new merchants, ensure the contract process is fully completed.
* If unsure, contact Coda Tech to assist with checking the setup.
***
#### 9. Why did I receive error code 233?
* Make sure your requested payType value is correct
* Missing configuration, please proceed to `Coda portal` > `Sandbox/Production Configuration` > `Coda payment page configuration` > Select the channel that you would like to integrate
---
# 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/codapay-integration-faq/hosted-payment-page-api/pre-integration.md?ask=&goal=
```
`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.