The Bitcoin you already sent toward a YBEX swap is still sitting at 0 confirmations, so the order has not credited. To speed up a stuck bitcoin swap deposit with RBF, open the send-side TxID on a Bitcoin explorer, compare its fee rate with today’s mempool, then raise the fee in the same sending wallet on the same deposit address. Do not broadcast a second independent payment.
Summary: A 0-confirmation Bitcoin swap deposit is a sending-wallet fee problem, not a second order. Compare sat/vB with a live mempool estimate, then use Replace-by-Fee on the same YBEX address and amount. A centralized-exchange withdrawal usually cannot be bumped by you. Save any new TxID on the same Request Number.
YBEX is an instant crypto exchange. Homepage “instant” is marketing, not a miner clock. The Terms of Use (clause 6.5) allow 30 minutes to 72 hours of processing after a visible deposit. YBEX is not a custodian and cannot re-sign a Bitcoin send it did not broadcast.
Replace-by-Fee (RBF) lets the sender publish a new version of an unconfirmed payment with a higher fee, using the same coins: extra postage on a parcel still in the sorting room. The mempool is that waiting room. 0 confirmations means the send is not in a block yet. sat/vB (satoshis per virtual byte) is the price per unit of space. Miners pick higher sat/vB first.
Confirm the send is still at 0 confirmations on a Bitcoin explorer
Do prove the coins are waiting in the mempool on the live YBEX order. Don’t guess from a wallet “pending” badge. Copy the Request Number (Order ID) and confirm the deposit address is the one you paid. Status help: checking your exchange application status. Don’t create a second swap.
Paste the send-side TxID into mempool.space or another Bitcoin explorer. Confirm the transaction exists, the recipient is the YBEX deposit address, the amount matches, and confirmations = 0. If any fail, RBF is the wrong tool.
| What you see | What it means | Do / don’t |
|---|---|---|
| Tx exists, 0 conf, fee looks low | Mempool-pending send | Compare sat/vB, then bump if you control the wallet. Don’t pay twice. |
| Explorer shows 1+ confirmation | Already in a block; RBF is closed | Wait on the same order inside Terms 6.5. Refresh F5. Don’t bump a confirmed tx. |
| Wrong address, no TxID, cancelled form, KYC | Not a low-fee Bitcoin problem | Official chat with the Request Number. See the stuck swap order status checklist. Don’t RBF. |
YBEX does not publish a public Bitcoin confirmation count. Don’t copy “1–3” from another site as a YBEX rule. The 15-minute unused-form timer is for creating the order, not for confirmations. If you sent after auto-cancel, use site chat with the TxHash. Low Ethereum gas is a different job, as is waiting after a send is already in a block.
Compare the fee rate with live mempool estimates before you bump
Do read the explorer fee rate, then open a live dashboard the same day. On 21 September 2026, mempool.space recommended fees showed fastestFee 2 sat/vB and slower bands at 1 sat/vB. That is a quiet-mempool example, not a standing YBEX fee.
If the send is already in today’s High / next-block band, waiting a few blocks can be cheaper than another bump. Blocks are often described as roughly 10 minutes apart; that is an average, not a clock. If sat/vB sits clearly below the priority band, bump in a self-custody wallet. Do set the replacement clearly higher. Don’t add a tiny +1 sat.
Do this: Price the bump off today’s mempool High / next-block estimate. Don’t treat 1–2 sat/vB from a quiet day as always enough.
Choose self-custody Replace-by-Fee or accept that a CEX withdrawal cannot be bumped
Split the sender first. Self-custody means you hold the keys. A centralized exchange (CEX) withdrawal means that venue signed the send. YBEX does not mine blocks for you.
| How you sent | Can you RBF? | What to do |
|---|---|---|
| Self-custody wallet | Often yes, if Increase fee, Speed up, Bump fee, or Replace by fee: True is shown | Bump the original send. Keep the same YBEX address and amount. |
| Withdrawal from an exchange | Usually no. You did not sign it. | Wait, or ticket the sending exchange with their withdrawal TxID. Don’t ask YBEX to bump it. |
Verdict: If your wallet offers Increase fee / Speed up, bump that original send. If a CEX signed the withdrawal, you cannot Replace-by-Fee it yourself. Do not send a second independent Bitcoin payment to the YBEX address.
Examples: Trezor Suite Speed up → Replace transaction; Electrum History → Increase Fee when Replace by fee: True. A wallet can still hide the button if the original send was not marked replaceable. Don’t treat a missing button as a reason to send twice.
Child-pays-for-parent (CPFP) uses a later high-fee send to drag an earlier related one. On a YBEX deposit you usually cannot CPFP the received output. Sender-side CPFP only works if you still have unconfirmed change you control. Don’t Cancel (double-spend) if you still want this order credited.
Raise the fee on the same YBEX deposit, not with a second payment
Do replace the original unconfirmed send. Don’t build a new transfer from leftover coins to the same address. Two independent sends can both confirm; that is not RBF. Fixed locks at create; Floating follows the market until completion.
Workflow:
Order ID + deposit address → explorer 0 conf + sat/vB vs live mempool → self-custody RBF or CEX cannot bump → same address/amount replacement → save new TxID → wait 1+ conf on the same YBEX order → never a second payment
- Copy the Request Number and deposit address from the live YBEX order.
- Paste the send-side TxID into a Bitcoin explorer; confirm recipient, amount, and 0 confirmations.
- Compare that sat/vB with today’s mempool High / next-block estimate.
- If a CEX signed the withdrawal, stop: wait or ticket that exchange. If you hold the keys, open Increase fee / Speed up / Bump fee on that same send.
- Set a new fee in the current priority band. Confirm the same YBEX address and deposit amount. Extra fee comes from change or spare Bitcoin, not a second payment.
- Sign and broadcast. Do not tap Cancel or return-to-self if you still want this order credited.
- Copy the new TxID if the hash changed. Keep the old hash under the same Request Number.
- Wait for 1+ confirmation on the replacement, then refresh the YBEX order with F5. Do not open a new swap for the new hash.
If there is no Speed up control, don’t invent a second send. Wait, use optional CPFP only on change you control, or write the sending venue.
Save the new TxID and match the replacement to the same YBEX order
Do expect the hash to change. A replacement spends the same inputs, so explorers often show a new TxID. Save both and match them to the same Request Number. Don’t open a new order “under the new TxID.” After credit, check the receive-side with the payout explorer checklist. Don’t keep bumping a send that already has 1+ confirmation.
Refresh the order (F5) after the replacement confirms. If Bitcoin confirmed after auto-cancel, use website chat with the application number and TxHash. Follow Bitcoin confirmed after application cancellation. A KYC pause is not an RBF job. Write official YBEX support or [email protected] with the Request Number, both TxIDs, amount, and deposit address. Ignore first-contact DMs offering a paid “accelerator.” They cannot rewrite a signed fee and never need a seed. Official Telegram: t.me/ybex_io.
Turn on RBF before the next Bitcoin swap deposit
Do fix the next send before broadcast. Enable Replace-by-Fee. Pick a competitive sat/vB from the live mempool that day. Send one deposit to the new order’s address. Don’t open a second order or reuse an old deposit address.
When this order is finished, create the next swap on ybex.io: You send / You receive, Bitcoin as the send asset, recipient address, Fixed or Floating, accept Terms / AML / Privacy, then Exchange. The service is not available to persons in the EU/EEA.
- Turn RBF on in the sending wallet before you broadcast the next Bitcoin deposit.
- Read today’s mempool estimate and choose a competitive sat/vB.
- Copy the deposit address from the new YBEX order only, then send once.
- Save the Request Number and the send-side TxID in one note.
- If that send sticks at 0 confirmations, bump the same transaction. Never add a second independent payment.
Frequently asked questions
Can I RBF a Bitcoin withdrawal from an exchange to YBEX?
Usually no. The exchange signed the transaction. Open that exchange’s withdrawal support with their TxID, or wait. Do not send a second deposit to the YBEX address. YBEX cannot bump a transaction it did not broadcast.
Does replace-by-fee change the deposit TxID?
It can. The replacement is a new transaction spending the same inputs. Save the new hash and keep it on the same YBEX order. Different nodes may show the old hash until they drop it.
Should I send a second BTC payment if the first is stuck at 0 confirmations?
No. Two independent sends can both confirm. Use the sending wallet’s Increase fee or Speed up on the original, or wait. A second payment is not Replace-by-Fee.
The explorer already shows 1 confirmation. Can I still RBF?
No. Once a transaction is in a block, Replace-by-Fee does not apply. Wait inside Terms 6.5. YBEX does not publish a public Bitcoin confirmation count. Then use the order page or official chat if needed.
Someone offers a paid accelerator or Telegram helper to unstick my swap. What should I do?
Stop. Do not share a seed. An accelerator cannot rewrite your signed fee. Official channels are the order page, ybex.io/support, and site chat.
Disclaimer: The material in this article is not financial or investment advice. Everything stated here reflects the author's personal view and should not be treated as a recommendation to trade or invest. We make no warranties regarding the accuracy, reliability or completeness of the information presented. Cryptocurrency markets are highly volatile and can move unpredictably. Before committing any funds, every investor, trader or crypto user should study several independent sources and check the regulations that apply in their own jurisdiction.