> 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/refund-a-payment/supported-payment-channel.md).

# Supported Payment Channel

The Codapay Refund API universally supports all payment channels available in Codapay. Merchants can submit a standard API request for any eligible transaction.

Depending on the specific capabilities of the original payment channel, Codapay processes the refund using one of the following methods:

* Direct Channel Refund: If the payment channel natively supports refunds, the transaction is processed automatically, and the funds are credited directly back to the customer's original payment method.
* Manual Bank Transfer Fallback: If the payment channel does not natively support direct refunds, Codapay automatically initiates a manual fallback process. In this scenario, Codapay contacts the customer directly to securely collect their bank account details and completes the transfer.

This underlying execution logic is entirely abstracted from the merchant. The API integration, request payload, and expected responses remain identical across all payment channels.

### Payment Channel ID Mapping

{% hint style="info" %}
Please note that in the referenced page, the `payType` parameter corresponds directly to the Payment Channel ID used in the Refund API.
{% endhint %}

For a comprehensive list of Codapay payment channels and their corresponding numeric IDs required for API requests, please refer to this page: [Hosted Payment Page](/codapay/integration-guides/payment-channel-info/hosted-payment-page.md)


---

# 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/refund-a-payment/supported-payment-channel.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.