# Automatic channel payment enrollment

\
When you create a channel, you set a currency pair for it, meaning you get to choose the currency that the user sends and the currency that will be credited to your account. But occasionally a user can make a mistake and send some third currency e.g. when USDT via TRC-20 is sent instead of TRX via TRC-20 etc.\
Channel payments with incorrect coin (but correct network) are credited automatically as channel payments (with Custom ID of the original channel), and [callbacks](https://developers.cryptopay.me/guides/channels/callbacks) are sent. 

\
**Important points:**\
\
• The feature is only available if the user has sent incorrect coin via the correct network. If the network or both network and coin are incorrect, you can check the possibility of recovery [here](https://help.cryptopay.me/en/articles/5747828-recovery-of-incorrectly-sent-crypto-transactions).

• The feature is only available for channels; it isn’t supported for invoices.

• In such cases (when the end-user used an incorrect currency), **paid\_currency** for channel payment (in the callback) will differ from **pay\_currency** of the channel itself for those incorrect coin payments (it will match the actual currency that was sent and received on our side, as long as it’s supported by us). To ensure that such payments are credited correctly on your side, please check whether your integration would supports such a mismatch between the channel data and the callback;

• The **received\_currency** (from the callback) will be the same as the **receiver\_currency** of the original channel, so if the end-user expected to get e.g. EUR as a result, this is the currency they’ll be credited with;

• Even if the channel initially has **pay\_currency** = **receiver\_currency** (crediting payments with no exchange), with an incorrect coin there will be an exchange to **receiver\_currency** (so the current exchange rates would apply);\ <br>


---

# Agent Instructions: 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:

```
GET https://developers.cryptopay.me/guides/channels/automatic-channel-payment-enrollment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.