> 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/direct-api-integration/direct-api-integration-for-alternative-payment-methods.md).

# Direct API Integration for Alternative Payment Methods

This integration lets you connect directly to Codapay’s APIs to support local and alternative payment methods (e.g., wallets, bank transfers). By using a direct API call, you keep the payment flow inside your own app or website, while Codapay handles the processing behind the scenes.

To get started, you’ll need to:

* Use your Codapay **API Keys**, which uniquely identify your app or platform.
* Send requests to the correct **Endpoint URLs** for Sandbox (testing) or Production (live) environments.

The following sections provide the details you need for API Keys and Endpoint URLs.

## API Keys

Each game or platform integrated by partners is assigned a unique set of API keys. All Codapay API keys can be accessed via the **Publisher Portal** under: **Integration → Codapay → API Keys tab**

If a partner requires a new API key for a different country, they must:

* Create a new Codapay title. \
  ***OR***
* Add a new country to an existing Codapay title.

🔗 **Direct Access:** <https://portal.coda.co/#/integration/codapay/publisher-settings>

## Endpoint URLs

The only way for the publisher to integrate with Coda is to send the JSON request to the following URL:

Refer to our sample messages for examples.

### Sandbox

<table><thead><tr><th width="197">Version</th><th>Base URL</th></tr></thead><tbody><tr><td>v2.0</td><td><a href="https://sandbox.codapayments.com/airtime/offline/charge/v3">https://sandbox.codapayments.com/airtime/offline/charge/v3</a></td></tr><tr><td>v1.0</td><td><a href="https://sandbox.codapayments.com/airtime/offline/charge/v2">https://sandbox.codapayments.com/airtime/offline/charge/v2</a></td></tr></tbody></table>

### Production

<table><thead><tr><th width="196">Version</th><th>Base URL</th></tr></thead><tbody><tr><td>v2.0</td><td><a href="https://airtime.codapayments.com/airtime/offline/charge/v3

"><https://airtime.codapayments.com/airtime/offline/charge/v3> </a></td></tr><tr><td>v1.0</td><td><a href="https://airtime.codapayments.com/airtime/offline/charge/v2"><https://airtime.codapayments.com/airtime/offline/charge/v2></a></td></tr></tbody></table>

{% hint style="warning" %} <mark style="color:orange;">**Please ensure that requests to Codapay API must be sent over**</mark>

1. HTTPS
2. TLS 1.2 or higher
   {% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coda.co/codapay/direct-api-integration/direct-api-integration-for-alternative-payment-methods.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.