What happens to a swap when the receiving wallet is a custodial service that rejects the deposit

05 September 2026

The swap fails and your funds are either returned to the originating wallet or stuck in limbo, depending on the exchange's policies and the blockchain involved. This happens because a custodial service - an exchange, wallet provider, or trading platform that holds private keys for its users - has its own internal compliance rules and address screening.

When you initiate a swap, the exchange sends cryptocurrency to the address you provided. That address belongs to a custodial service, not to your personal wallet. The custodial service's software automatically checks incoming deposits against its internal rules. Common reasons for rejection include:

• The deposit address is flagged as high-risk or associated with suspicious activity.
• The amount sent triggers anti-money laundering thresholds.
• The cryptocurrency or token is not supported or is restricted in the user's jurisdiction.
• The address has been inactive for a long period and requires manual review.
• The deposit originates from a known mixing service or privacy protocol.

The custodial service does not broadcast these reasons publicly. It simply rejects the transaction. On the blockchain, the rejection looks like a normal incoming transaction that is then reversed or ignored. The swap provider sees the deposit confirmation on-chain, but the custodial service never credits the user's account.

What happens next depends on the swap provider's refund mechanism. Some exchanges automatically detect the rejection and initiate a refund to the swap's source address. This refund may take hours or days. Others require you to open a support ticket. A few providers treat the deposit as completed because the blockchain confirmed it, leaving you to resolve the issue with the custodial service directly.

The critical problem: you have no control over the custodial service's decision. You cannot force it to accept a deposit it has rejected. The only way to avoid this scenario is to verify the receiving address before you send.

This is why the hub page "Swapping crypto safely" emphasizes checking that the destination address belongs to a wallet you control - one where you hold the private keys, or at minimum one where you have confirmed the service will accept deposits from swap providers. If you are sending to a custodial exchange, test the address with a tiny amount first, as covered in the sibling page "How to test a swap address with a tiny amount before sending the full deposit." That test will reveal whether the deposit is rejected or credited, saving you the full loss.

If a rejection does happen, gather the transaction ID, the swap provider's order ID, and a screenshot of the custodial service's error message (if any). Contact the swap provider’s support with these details. Expect a slow resolution - some exchanges process refunds manually once per week. The custodial service will almost never reverse a rejected deposit to a third party; your only recourse is through the swap provider.

Bottom line: a custodial rejection turns a simple swap into a customer service problem. The only reliable prevention is to send to an address you fully control, or to test first. The hub page walks through that entire process step by step.

Back to portfolio