> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/channels/channels-concept.md).

# Channels concept

A channel is a permanent deposit address assigned to one of your end users. Unlike an [invoice](https://docs.txn.io/invoices/invoices-concept.md), which is a one-off bill with a fixed amount and a 20-minute rate, a channel has no amount and no expiry: the end user can send any amount to it, as often as they like, and every transfer is credited to your account as a separate channel deposit.

{% hint style="warning" %}
Give each end user their own channel. Crypto transfers carry no reference, so a channel shared by several users leaves you unable to tell whose funds arrived.
{% endhint %}

### What a channel is made of

A channel pairs a **pay currency** on one network, what the end user sends (for example USDT on the Tron network, `trx:usdt`), with a **target currency**, what the deposit is credited in. The two can be the same, a crypto-to-crypto channel such as USDT to USDT, or different, a crypto-to-fiat channel such as USDT to EUR. An optional **local currency** adds a display currency the deposit is also expressed in, for example a `localAmount` in BRL for an end user who holds a BRL balance on your platform. [Listing channel currency pairs](https://docs.txn.io/channels/listing-channel-currency-pairs.md) returns the combinations available to you.

The channel carries your **reference**, typically your own user ID. It must be unique among your channels, and every deposit on the channel inherits it, so a webhook or a listing entry can be matched to the user without a lookup. The deposit address is assigned at creation and returned in the create response, ready to show to the user.

### How deposits are processed

Txn monitors the channel address continuously. Each transfer it detects becomes a channel deposit with its own `status`:

* `pending` while Txn waits for the on-chain confirmations and, on a crypto-to-fiat channel, converts the funds;
* `on_hold` if source-address screening flagged the transfer for review;
* `completed` once the funds are credited to the channel's target account;
* `rejected` if compliance declined the deposit or the on-chain transaction never confirmed.

See [Channels deposit flow](https://docs.txn.io/channels/channels-deposit-flow.md) for the transitions. Only `completed` deposits move the account balance.

On a crypto-to-fiat channel there is no rate lock: the conversion is priced at the spot rate with your spread at the moment the deposit is confirmed, so the `amount` credited depends on the market at that time. Each deposit reports the crypto received (`payAmount`), the amount credited after fees (`amount`), the Txn fee and consolidation fee, the network fee, the rates applied, and the result of source-address screening. [Reading channel deposit](https://docs.txn.io/channels/reading-channel-deposit.md) describes every field.

### Enabling and disabling

A channel is `enabled` or `disabled`. Deposits to a disabled channel are not processed or credited until you enable it again with [Updating channel](https://docs.txn.io/channels/updating-channel.md). Use it to pause a user without taking away their address.

### Keeping your platform in sync

Txn sends a [channel webhook](https://docs.txn.io/channels/channel-webhooks.md) on every status change of a deposit, with the full deposit in the payload, including `channelId` and your `reference`. Credit the end user on `completed`, and treat `rejected` as final. For reconciliation, [Listing channel deposits](https://docs.txn.io/channels/listing-channel-deposits.md) returns the deposits of one channel, and [Listing transactions](https://docs.txn.io/transactions/listing-transactions.md) shows them as `ChannelTransaction` entries across all your accounts.


---

# 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.txn.io/channels/channels-concept.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.
