This is a different problem than not seeing a transfer option at all. Here, the balance was Available, the transfer was actually started — and it came back declined or failed instead of going through. That points to something specific going wrong on the bank or card side, not a pending-funds issue.
This isn't the same as "I can't withdraw at all"
If there's no transfer button showing in the first place, that's almost always pending funds or unverified payment details — covered in full here. A declined transfer means the button worked, you submitted it, and the destination account or card rejected it. The fixes are different, so it's worth confirming which situation actually applies before troubleshooting.
1. The linked bank account was closed or changed
If the account on file was closed, or the routing/account number was mistyped when it was added, the receiving bank rejects the deposit and Depop reports it back as declined. Double-check the account details in Settings → Payments against a current statement, not from memory.
2. Name mismatch between Depop and the bank account
Some banks reject incoming transfers when the name on the Depop account doesn't closely match the name on the receiving account — common after a legal name change that wasn't updated in one place or the other. This is a quieter cause than sellers expect, since nothing else about the account looks wrong.
3. The instant transfer card was declined
For instant transfers specifically, the destination is a debit card, not a bank account — the usual card-decline reasons apply: expired card, card frozen or replaced, or the issuing bank flagging the transaction as unusual activity. Switching to a standard bank transfer sidesteps this entirely, at the cost of the 1-3 day wait instead of an instant one. The full cost-versus-speed tradeoff between the two methods is broken down here.
4. A fraud check triggered after submission
Occasionally a transfer clears Depop's side but gets flagged by the receiving bank's own fraud systems, especially for a first-time transfer to a newly linked account or an unusually large amount relative to your history. This typically resolves by retrying after the bank's hold clears, or contacting the bank directly to confirm the transaction is legitimate.
5. A stale session or app bug
Rare, but a transfer submitted during a poor connection or right after an app update can come back as a false decline with no real cause on the bank side. Force-closing and retrying, or submitting from a browser instead of the app, resolves this more often than it should.
What to do first
Re-verify the linked account details before retrying — a mistyped digit is the single most common real cause. If the details are correct and it declines again, try a standard transfer if you were using instant, since that removes card-specific decline reasons from the equation entirely.
Avoiding the confusion at scale
A declined transfer is more disruptive for a shop that's actively relying on that cash to restock — and harder to untangle when the in-app balance doesn't match what's actually landed anywhere yet. DepopAutomation.com's profit tracker keeps an independent running total of what's actually been earned per sale, so a declined transfer is an isolated banking issue to fix — not a moment where the numbers themselves come into question. It runs alongside the AI listing tool, bulk lister, and automatic relisting that keep revenue flowing in the first place.
Conclusion
A declined transfer almost always traces back to the receiving bank account or card — closed accounts, name mismatches, or card issues — not a problem with Depop's balance itself. Verify the destination details first, and keep an independent record of real earnings with DepopAutomation.com so a banking hiccup never looks like a bigger problem than it is.