> 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/api-basics/changelog.md).

# Changelog

## November 13, 2026

**Binance order ID on payouts.** Binance Pay payouts return `binanceOrderId`, the Order ID that Binance assigns to the transfer and that the recipient sees in their Binance app, so you can quote it as the payment reference. It is returned by [Reading payout](https://docs.txn.io/payouts/reading-payout.md), [Listing payouts](https://docs.txn.io/payouts/listing-payouts.md) and the [payout webhooks](https://docs.txn.io/payouts/payout-webhooks.md). It can be set some time after the payout's `status` changes to `completed`, so the `completed` webhook may carry `null`; use [Reading payout](https://docs.txn.io/payouts/reading-payout.md) to get it. It is `null` for `on_chain` payouts.

## October 22, 2026

**Company-wide transaction list.** `GET /api/public/v1/transactions` returns the transactions of all your accounts in one paginated list, with the same filters and the same shape as the per-account listing. See [Listing transactions](https://docs.txn.io/transactions/listing-transactions.md).

**Faster transaction listings.** The running `balance` in transaction listings is now computed backwards from the account's current available funds, so long account histories return in milliseconds.

## October 6, 2026

**Tron addresses must be Base58.** Payout destinations on Tron networks (`trx`, `trx:usdt`) must be a Base58 address starting with `T` with a valid checksum. A `0x` Ethereum-style or `41` hex form now returns `422 invalid_address` from [Validate address](https://docs.txn.io/payouts/validating-addresses.md), [Create payout](https://docs.txn.io/payouts/creating-payout.md) and [Draft payout](https://docs.txn.io/payouts/drafting-payout-optional.md) instead of being paid to the re-encoded Tron address.

## August 31, 2026

**Balances are available funds.** `balance` on accounts, and `totalBalance` on master accounts, now report the funds available to you: pending payouts and bank withdrawals are deducted as soon as they are created, and deposits count once they complete. The running `balance` in transaction listings follows the same rule. See [Accounts concept](https://docs.txn.io/accounts/accounts-concept.md).

**Channel currency pairs.** [Listing channel currency pairs](https://docs.txn.io/channels/listing-channel-currency-pairs.md) returns `payCurrency` and `targetCurrency` relationships. `localCurrency` is kept for compatibility: it points at the target currency and is flagged `"meta": {"deprecated": true}`.

**Reference on manual transactions.** Balance adjustments made by Txn (`transactionType` `ManualTransaction`) can carry a `reference`, returned in the API and in CSV reports.

## August 24, 2026

**Channel deposits under review are visible.** A channel deposit held for compliance screening now appears with status `on_hold` in [Listing channel deposits](https://docs.txn.io/channels/listing-channel-deposits.md) and in account transaction listings while the review is in progress, instead of only once it is released or rejected. See [Channels deposit flow](https://docs.txn.io/channels/channels-deposit-flow.md).

## August 10, 2026

**Source-address screening on crypto deposits.** The `riskScore`, `clusterCategory` and `clusterName` fields introduced for channel deposits on July 11 are now returned on crypto deposits too: on the `coinDeposits` entities of invoice responses and invoice webhooks, and on [Listing crypto deposits](https://docs.txn.io/transactions/listing-crypto-deposits.md) and [Reading crypto deposit](https://docs.txn.io/transactions/reading-crypto-deposit.md).

**IP whitelist on API keys.** The IP whitelist of an API key can be edited on an existing key from the dashboard, without re-issuing the key or changing its permissions. Requests from an IP address outside the list are rejected with `401`. See [Creating your API keys](https://docs.txn.io/getting-setup/creating-your-api-keys.md).

## July 23, 2026

**USD trading pairs.** Exchange quotes can be created against USD for BCH, BTC, LINK, LTC, TRX and XRP. See [Listing exchange currency pairs](https://docs.txn.io/exchange/listing-exchange-currency-pairs.md) for the pairs and limits available to your account.

## July 11, 2026

Channel deposits now return additional detail on each deposit. The new attributes appear in the [Read channel deposit](https://docs.txn.io/channels/reading-channel-deposit.md) and [List channel deposits](https://docs.txn.io/channels/listing-channel-deposits.md) responses, and in the [channel webhook](https://docs.txn.io/channels/channel-webhooks.md) payload.

**Network fee breakdown**

The on-chain network fee incurred by the deposit is now reported, expressed in three currencies:

* **networkFee** and **networkFeeCurrency** — the network fee and its currency (the network's native asset, e.g. `TRX`).
* **networkFeePayAmount** — the network fee expressed in the deposit's `payCurrency`.
* **networkFeeLocalAmount** — the network fee expressed in the `localCurrency`.
* **payToLocalCurrencyRate** — the `payCurrency` to `localCurrency` exchange rate.

**Source-address screening**

Deposits now carry the result of on-chain analytics screening of the sender:

* **riskScore** — a risk score for the deposit's source address, when a score is available.
* **clusterCategory** and **clusterName** — the category and name of the entity the source address is attributed to (e.g. `Exchange` / `Binance`).

These fields are additive and require no changes to existing integrations. The screening fields are populated once a deposit reaches `completed`.

## June 11, 2026

**Minimum invoice fee.** The invoice processing fee, `transactionFee` on the `invoiceTransactions` entity, is subject to a minimum fee configured for your account: on a small invoice the fee is the minimum rather than the percentage.

## May 13, 2026

Added support for USDT and USDC on the Solana network.

| Name       | Code | Network |
| ---------- | ---- | ------- |
| Tether USD | USDT | Solana  |
| USD Coin   | USDC | Solana  |

Refer to the [Supported Currencies](https://docs.txn.io/api-basics/supported-currencies.md) page for more detail.

## May 12, 2026

**Source addresses on deposits.** Crypto deposits and channel deposits return `sourceAddresses`, the wallet address(es) the funds were sent from, in API responses and webhook payloads. The array usually has one entry; UTXO-based networks such as Bitcoin can list several.

## April 15, 2026

**Network and address on crypto deposits.** [Listing crypto deposits](https://docs.txn.io/transactions/listing-crypto-deposits.md) and [Reading crypto deposit](https://docs.txn.io/transactions/reading-crypto-deposit.md) return the `network` and `addresses` entities of each deposit in `included[]`.

**Reference on transactions.** Every transaction returned by the transaction listings carries the `reference` of the record behind it, such as the reference you set on an invoice, payout or bank withdrawal, so ledger entries can be matched to your own records.

## April 6, 2026

**Crypto deposit endpoints.** Direct deposits to your account addresses can be listed and read through the API: [Listing crypto deposits](https://docs.txn.io/transactions/listing-crypto-deposits.md) and [Reading crypto deposit](https://docs.txn.io/transactions/reading-crypto-deposit.md), with the same date filters as the other listings.

## March 30, 2026

**Payout preview and confirmation.** Draft a payout to see the amounts, fees and exchange rate before committing to it, then confirm it: [Drafting payout](https://docs.txn.io/payouts/drafting-payout-optional.md) and [Confirming payout draft](https://docs.txn.io/payouts/confirming-payout-draft-optional.md). A draft expires after 30 seconds.

**Payment link validity capped at 30 days.** `expires_at` on [Creating payment link](https://docs.txn.io/payment-links/creating-payment-link.md) may be at most 30 days ahead; later values are rejected with `expires_at_too_long`.

## March 17, 2026

**Invoice reference on crypto deposits.** A crypto deposit that paid an invoice carries the invoice `reference`, in API responses, webhooks and CSV reports.

## March 3, 2026

**Total balance.** Accounts return `totalBalance`: for a master account, the balance across the master account and its subaccounts. See [Reading account](https://docs.txn.io/accounts/reading-account.md).

## February 25, 2026

**Bank details for funding fiat accounts.** Accounts return `bankDepositAvailable` and, when it is `true`, the `txnBankCredentials` entity with the beneficiary name, IBAN, BIC and bank to send a bank transfer to. See [Reading account](https://docs.txn.io/accounts/reading-account.md).

**Transfer availability.** Accounts return `transferAvailable`. It is `false` for a closed subaccount, which can no longer send or receive internal transfers.

## January 21, 2026

**Bank withdrawal availability.** Accounts return `bankWithdrawalAvailable`, `true` when a bank withdrawal can be initiated from the account. See [Reading account](https://docs.txn.io/accounts/reading-account.md).

## December 25, 2025

**Subaccounts in the API.** Subaccounts can be created and listed through the API, and funds moved between your accounts in the same currency: [Creating subaccount](https://docs.txn.io/accounts/creating-subaccount.md), [Listing subaccounts for master account](https://docs.txn.io/accounts/listing-subaccounts-for-master-account.md) and [Creating account transfer](https://docs.txn.io/accounts/creating-account-transfer.md). Invoices, payouts and quotes can target a specific account with `targetAccountId` on invoices, `accountChargedId` on payouts, and `accountChargedId` and `accountReceivedId` on quotes. Responses carry the matching `targetAccount`, `accountCharged` and `accountReceived` relationships, and every transaction carries `accountId`. See [Accounts concept](https://docs.txn.io/accounts/accounts-concept.md).

## December 19, 2025

**Bank reference per account.** `bankReference` moved from the company to the account: each account, including each subaccount, has its own reference to quote on incoming bank transfers.

## November 13, 2025

**Bulk exchange rates.** [Reading exchange rates in bulk](https://docs.txn.io/exchange/reading-exchange-rates-in-bulk.md) returns the rates of one currency against every other supported currency in a single call.

## November 1, 2025

**Bank deposit status.** Bank deposits return `simplifiedState`, the same status vocabulary as every other transaction. See [Bank deposit status flow](https://docs.txn.io/fiat-settlements/bank-deposit-status-flow.md).

## October 24, 2025

**Approvals.** Payouts, bank withdrawals and payment links created while an approval rule applies return `approvalStatus` (`requested`, `approved`, `rejected` or `cancelled`; `null` when no rule applies). See the [Approvals feature guide](https://docs.txn.io/getting-setup/approvals-feature-guide.md).

## September 1, 2025

**Binance ID validation.** [Validating recipient's Binance ID](https://docs.txn.io/payouts/validating-recipients-binance-id.md) checks a Binance Pay recipient before you create the payout.

## August 20, 2025

**Binance Pay payouts.** Payouts can be sent to a Binance Pay account: set `paymentMethod` to `binance_pay` and pass `receiverBinanceId` on [Creating payout](https://docs.txn.io/payouts/creating-payout.md). The response reports the Binance side in `binanceStatus`.

## July 11, 2025

**API key on records.** Records created through the API return an `author` relationship with the `apiKeys` entity (`name`, `createdAt`) in `included[]`, so you can tell which key created an invoice, payout, quote or transaction.

## July 7, 2025

**Exchange currency pairs.** [Listing exchange currency pairs](https://docs.txn.io/exchange/listing-exchange-currency-pairs.md) returns the pairs, directions and minimum and maximum amounts available to your account.

## June 20, 2025

**Binance Pay for invoices.** Invoices can offer Binance Pay next to on-chain payment: pass `paymentMethods` including `binance_pay` on [Creating invoice](https://docs.txn.io/invoices/creating-invoice.md). The response carries a `binanceOrders` entity with the deep link, universal URL and QR code content to show the end user.

## May 27, 2025

**Quote endpoints.** Quotes can be listed and read: [Listing quotes](https://docs.txn.io/exchange/listing-quotes.md) and [Reading quote](https://docs.txn.io/exchange/reading-quote.md). Quote responses and exchange webhooks carry the exchange order and the two transactions it creates.

## March 25, 2025

Added support for new tokens.

| Name            | Code | Network |
| --------------- | ---- | ------- |
| Polygon Token   | POL  | Polygon |
| Native USD Coin | USDC | Polygon |

Refer to the [Supported Currencies](https://docs.txn.io/api-basics/supported-currencies.md) page for more detail.

## February 7, 2025

**Expiring payment links.** [Expiring payment link](https://docs.txn.io/payment-links/expiring-payment-link.md) immediately expires a `created` or `pending` link.

## February 1, 2025

Added support for Chinese Yuan (CNY), Brazilian Real (BRL), Chilean Peso (CLP) and Indian Rupee (INR) currencies.

The following currency pairs are available and supported in invoices, channels and payouts:

* crypto/CNY
* crypto/BRL
* crypto/CLP
* crypto/INR

When creating invoices, channels, and payouts with these currencies, you must also supply the account currency to process payments through (e.g. `EUR`).

## January 15, 2025

Merchants can now supply their preferred account currency when creating invoices, channels and payouts.

* For invoices, it's a new optional `targetCurrency` parameter which specifies the account that an invoice payment amount should be credited to.
* For channels, it's a new optional `localCurrency` parameter which specifies the currency code that a channel deposit amount should be denoted in.
* For payouts, it's a new optional `chargeCurrency` parameter which specifies the account that a payout amount should be debited from.
* For payment links, it's a new optional `accountCurrency` parameter which specifies the account that a payment amount should be credited/debited to/from.

## January 3, 2025

Added support for Canadian Dollar (CAD) and New Zealand Dollar (NZD) currencies.

The following currency pairs and directions are available and supported in exchanges, invoices, channels and payouts:

* crypto/CAD - buy and sell
* crypto/NZD - buy and sell
* EUR/CAD - buy and sell
* EUR/NZD - buy and sell

## December 14, 2024

The [Fiat Settlement API](https://docs.txn.io/fiat-settlements/listing-bank-accounts.md) endpoints are exposed in the public API, allowing platform clients to fetch data about bank accounts linked to their transaction accounts, as well as to receive webhook notifications related to bank deposits and withdrawals.

## December 5, 2024

Platform users can now request CSV transaction reports containing data on all currency account transactions via the UI and receive the files at their registered email addresses. Navigate to the Reports page from the left-hand menu in your Txn account.

## November 15, 2024

Added support for a new token.

| Name      | Code | Network          |
| --------- | ---- | ---------------- |
| Chainlink | LINK | Ethereum (ERC20) |

Refer to the [Supported Currencies](https://docs.txn.io/api-basics/supported-currencies.md) page for more detail.

## November 11, 2024

Added support for new cryptocurrencies and tokens.

| Name         | Code | Network          |
| ------------ | ---- | ---------------- |
| Bitcoin Cash | BCH  | Bitcoin Cash     |
| Litecoin     | LTC  | Litecoin         |
| Ether        | ETH  | Ethereum         |
| Tether USD   | USDT | Ethereum (ERC20) |
| USD Coin     | USDC | Ethereum (ERC20) |
| XRP          | XRP  | Ripple           |

Refer to the [Supported Currencies](https://docs.txn.io/api-basics/supported-currencies.md) page for more detail.

**CNH trading currency pairs delisted**

Txn no longer supports currency pairs and trading routes for buying and selling CNH. We are working on a comprehensive solution to support additional fiat currencies.

**Additional routes for crypto-crypto invoices and payouts**

Invoice Flow: USDT <- BTC, BCH, LTC, ETH, USDT, USDC, TRX, XRP. Users can pay with any of the supported cryptocurrencies or tokens, and merchants are settled in USDT.

Payout Flow: USDT -> BTC, BCH, LTC, ETH, USDT, USDC, TRX, XRP. Users can request payouts in any supported cryptocurrency or token, which will be processed from the merchant’s USDT balance.

**Endpoints for listing and creating account addresses**

Txn clients can now access API endpoints for [listing](https://docs.txn.io/accounts/listing-account-addresses.md) and [creating](https://docs.txn.io/accounts/creating-account-address.md) account addresses.

## October 10, 2024

Handling of invoice payment exception scenarios and automated invoice refunds are now available for Txn clients.

Merchants can now use automated by Txn payment refunds in scenarios where their end-users overpay, underpay, or make a payment after the invoice has expired. Txn issues a refund payment link, which can be embedded or emailed to the end-user. On the refund webpage, end-users are asked to provide their wallet address where they would like to receive their refund.

Please refer to the [Invoice Refunds](https://docs.txn.io/invoices/invoice-refunds.md) page for more information on how it works for both merchants and their end-users.

## October 8, 2024

The Channels related public API endpoints made available to Txn clients:

* [Create channel](https://docs.txn.io/channels/creating-channel.md)
* [Read channel](https://docs.txn.io/channels/reading-channel.md)
* [Update channel](https://docs.txn.io/channels/updating-channel.md)
* [List channels](https://docs.txn.io/channels/listing-channels.md)
* [List channel deposits by channel ID](https://docs.txn.io/channels/listing-channel-deposits.md)
* [Read channel deposit](https://docs.txn.io/channels/reading-channel-deposit.md)

## September 20, 2024

Added support for Offshore Renminbi (CNH) currency.

The following currency pairs and directions are available and supported in exchanges, invoices, channels and payouts:

* USDT/CNH - buy and sell
* BTC/CNH - buy and sell

## September 16, 2024

Webhook messages are now available in both Production and Sandbox environments.

For more information, please refer to the [Webhooks](https://docs.txn.io/api-basics/webhooks.md) page.

## August 21, 2024

**Invoices**

The following optional parameters are now supported in the [Create Invoice](https://docs.txn.io/invoices/creating-invoice.md) API call:

* **successRedirectUrl**: Specifies the URL to which your customer will be redirected after a successful invoice completion
* **unsuccessRedirectUrl**: Specifies the URL to redirect your customer if the invoice expires, is canceled, or is rejected

Additionally, invoices now come with hosted web pages provided by Txn. You can either embed these hosted pages within your UI or redirect your customers to them. The API response for each invoice now includes the **hostedPageUrl** attribute, which contains the URL of the hosted page.

**Payouts**

The following optional parameter is now supported in the [Create Payout](https://docs.txn.io/payouts/creating-payout.md) API call:

* **absorbFees**: If true, both service and network fees are deducted from the transaction amount. If false, both fees are deducted from your account balance.

## July 23, 2024

The [Validate Address](https://docs.txn.io/payouts/validating-addresses.md) endpoint made available for Txn Public API users. This new feature enhances the security and reliability of your crypto payout transactions by providing address validation capabilities.

Key Features:

* **Address Format Validation:** Ensures that the provided address adheres to the correct format
* **Address Risk Profile Assessment:** Evaluates the risk associated with the address, helping to mitigate fraudulent transactions

**Usage Recommendation:** We strongly recommend that Txn merchants utilize this endpoint to validate destination wallet addresses before initiating crypto payouts via the [Create Payout](https://docs.txn.io/payouts/creating-payout.md) endpoint. By doing so, you can prevent potential issues arising from invalid address formats or high-risk addresses.

## July 12, 2024

The Invoices and Payouts related public API endpoints made available to Txn clients:

**Invoices**

* [Create invoice](https://docs.txn.io/invoices/creating-invoice.md)
* [Read invoice](https://docs.txn.io/invoices/reading-invoice.md)
* [List invoices](https://docs.txn.io/invoices/listing-invoices.md)

**Payouts**

* [Create payout](https://docs.txn.io/payouts/creating-payout.md)
* [Read payout](https://docs.txn.io/payouts/reading-payout.md)
* [List payouts](https://docs.txn.io/payouts/listing-payouts.md)

## July 2, 2024

The Accounts and Exchange related public API endpoints made available to Txn clients:

**Accounts**

* [List accounts](https://docs.txn.io/accounts/listing-accounts.md)
* [Read account](https://docs.txn.io/accounts/reading-account.md)
* [List account transactions](https://docs.txn.io/accounts/listing-account-transactions.md)
* [Read account transaction](https://docs.txn.io/accounts/reading-account-transaction.md)

**Exchange**

* [Read exchange rate](https://docs.txn.io/exchange/reading-exchange-rates.md)
* [Create quote](https://docs.txn.io/exchange/creating-quote.md)
* [Confirm quote](https://docs.txn.io/exchange/confirming-quote.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 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/api-basics/changelog.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.
