> 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/general-information/payment-directory/pay-types.md).

# Pay Types

Our supported payment channels include Carrier Billing, Bank Transfers, Debit/Credit Cards, Convenience Store Payments, Cash Cards/Vouchers, and E-Wallets. We support these payment methods based on regional & product availability.

{% hint style="info" %}
For Codapay, you can integrate each payment channel using the Hosted Payment Page Integration or Backend API Integration, depending on their availability.\
\
Hosted Payment Page Integration supports all payment channels. For the channels supported by Backend API Integration, please refer to the related column in [Payment Channel Directory](/general-information/payment-directory/codapay-channel-details.md).
{% endhint %}

## Payment Types <a href="#payment-types" id="payment-types"></a>

### <mark style="color:purple;">Carrier Billing</mark> <a href="#carrier-billing" id="carrier-billing"></a>

Carrier Billing allows customers to charge purchases to their mobile phone account. The payment is authenticated through an SMS sent to the customer's phone and is processed immediately.

### <mark style="color:purple;">Bank Transfer</mark> <a href="#bank-transfer" id="bank-transfer"></a>

Customers can pay by executing a bank transfer at an ATM, bank counter, or via online banking. Merchants receive a unique payment code, which the customer enters as part of the bank transfer details.

### <mark style="color:purple;">Card Payments</mark> <a href="#card-payments" id="card-payments"></a>

This method allows customers to complete payments using their credit or debit card. Customers are redirected to the partner's payment page to input their card details and complete the payment.

### <mark style="color:purple;">Convenience Store Payments</mark> <a href="#convenience-store-payments" id="convenience-store-payments"></a>

This method allows customers to complete payments at a convenience store. Customers receive a unique payment code from Codapay, which they present at the store.

### <mark style="color:purple;">Voucher (Cash Card)</mark> <a href="#voucher-cash-card" id="voucher-cash-card"></a>

Customers purchase a voucher from an issuer and enter it in Codapay's payment window to purchase digital content.

### <mark style="color:purple;">E-Wallet</mark> <a href="#e-wallet" id="e-wallet"></a>

E-wallets allow customers to have a digital payment account and top-up balance. Codapay supports many types of e-wallets for purchases.


---

# 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/general-information/payment-directory/pay-types.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.