Rapid Transfer
What is Rapid Transfer
Rapid Transfer is LTP's proprietary solution designed for fast capital turnover. When you move funds from one trading account to another and the conditions below are met, the transfer completes within seconds instead of waiting for block confirmations.
The funds never go on chain. Rapid Transfer draws on LTP's own liquidity pool at the receiving venue and credits the account there immediately.
Scope
Rapid Transfer applies to transfers between two trading accounts. Throughout this page, trading account means a RapidX Portfolio or a DMA sub-account on one of the supported venues.
| Operation | Rapid Transfer |
|---|---|
| Transfer — trading account ↔ trading account | ✓ |
| Transfer — Funding Account ↔ trading account | — |
| Deposit — external address → trading account | — |
| Withdrawal — trading account → external address | — |
Everything marked — is processed as a standard on-chain transaction.
Eligibility
Rapid Transfer applies when all of the following conditions are met:
| Criteria | Requirement |
|---|---|
| Supported asset | USDT (more assets will be supported in the future) |
| Route | Trading account ↔ trading account |
| Amount | 20 USDT, up to the receiving venue's maximum below |
Transfers that fall outside these criteria are processed as standard on-chain transactions.
Supported venues and pools
Each venue is served by its own pool. What makes a transfer instant is that the pool at the receiving venue pays out to the destination account — so the limit that applies is the receiving venue's, and it is the receiving venue's pool you want to check quota on. The sending venue's limit does not constrain the transfer, because on that side the funds move into the pool.
A single transfer can draw at most 80% of the pool's size — so on a 400,000 USDT pool the ceiling is 320,000, even when the pool is completely untouched. Query Rapid Pool Quota returns this already capped: available is the amount you can actually move right now, with the 80% rule applied. Compare your transfer amount against it directly — no further discount.
| Receiving venue | pool value | Pool size | Maximum per transfer |
|---|---|---|---|
| Binance | Binance | 400,000 USDT | 320,000 USDT |
| RapidX-Binance | RapidX-Binance | 400,000 USDT | 320,000 USDT |
| Bybit | Bybit | 400,000 USDT | 320,000 USDT |
| OKX | OKX | 300,000 USDT | 240,000 USDT |
| RapidX-OKX | RapidX-OKX | 300,000 USDT | 240,000 USDT |
| Gate | Gate | 300,000 USDT | 240,000 USDT |
| Bitget | Bitget | 200,000 USDT | 160,000 USDT |
| Deribit | Deribit | 200,000 USDT | 160,000 USDT |
| Coinbase | Coinbase | 100,000 USDT | 80,000 USDT |
A RapidX Portfolio is served by a separate pool per underlying exchange, so it has two pool values — pass the one matching the exchange the destination Portfolio sits on.
The limit is therefore not symmetric. 300,000 USDT from Bitget to Binance is eligible, because Binance is receiving and its maximum is 320,000; the same amount in the opposite direction is not, because Bitget's maximum is 160,000.
Quota is shared, and it is checked at execution time
The Maximum per transfer column is a hard cap, not capacity you can count on. Whether a given request goes instant also depends on the pool's available balance at the moment it executes, and pools are shared across all LTP clients.
Query Rapid Pool Quota gives you that number in real time, but treat it as a snapshot rather than a reservation. Quota is consumed when the transfer executes, not when you check it, so there is a small window in which another client can take the room you just measured. A request that looked eligible a moment earlier can still find the pool short.
This is not an error case you need to handle. When the pool cannot cover the amount, the request continues through the standard transfer flow instead — it is not rejected, and you do not need to retry. Read the rapidTransfer field on the resulting record (Transfer History) to see which route was actually used.
Using Rapid Transfer via the API
Rapid Transfer is not a separate endpoint — you opt in with a flag on the regular transfer call.
| Opt in | Set rapidTransfer: true on Transfer. Defaults to false |
| Fallback | Setting true prioritizes the Rapid Transfer fund pool. If the pool does not have enough available quota — or the request falls outside the criteria above — the request automatically continues through the standard transfer flow. The call does not fail |
| Check quota | Query Rapid Pool Quota returns how much you can move into a venue right now, with the 80% cap already applied. Query the receiving venue's pool — that is the one paying out |
There are no fees for using Rapid Transfer. Because the funds never touch the chain, there is no network fee either.
Changes in the 26 Aug 25th release
If you integrated against Rapid Transfer before this release, three things changed:
pool=Unifiedpoolno longer exists. The Funding Account pool has been retired. Query Rapid Pool Quota no longer accepts that value, and transfers to or from your Funding Account are no longer eligible for Rapid Transfer — they run as standard on-chain transactions.- Four new
poolvalues:RapidX-Binance,RapidX-OKX,DeribitandBitget. Note that RapidX is split by underlying exchange — there is no plainRapidXvalue. rapidTransferon Withdraw has no effect. Withdrawals are outside the scope of Rapid Transfer. The field is still accepted so existing integrations keep working, but setting it totruechanges nothing — the withdrawal goes on chain either way.
In the history endpoints (Transfer History, Withdrawal History, Deposit History) the rapidTransfer response field is unchanged, and still reports true on older records that did use Rapid Transfer. From this release on, only trading-account-to-trading-account transfers can return true.
Updated 19 days ago