Why Depop Keeps Saying Wrong OTP? Quick Fix

There’s nothing quite like the rage of watching a six-digit code you know is right get slapped back with a wrong OTP error. You triple-check the numbers. You copy-paste instead of typing. Still rejected. The kicker? The code looks perfect, arrived seconds ago, and your phone is right there in your hand. So why is Depop being so difficult?

This guide breaks down every reason that error pops up and gives you a clear, no-nonsense path to fixing it without pulling your hair out (or racking up a massive phone bill on failed SMS attempts).

Whether you’re a seasoned seller trying to re-verify your account, a new user stuck at the signup screen, a developer poking at SMS verification flows, or just someone who’s wasted half an hour on a problem that should take two minutes, you’re in the right place. If your code has failed three or more times already, or you suspect your personal number might have been flagged by Depop’s risk engine, jump straight to the checklist in H2 #12 and work backward from there.

Quick Answer

• Depop’s wrong OTP error is almost always a timing or session issue, an expired code, a resend loop, or a device timezone mismatch, not a typo.
• Failed 3+ times? Stop. Seriously. Give it 30–60 minutes. Hammering the resend button only makes Depop’s anti-fraud lockout stretch longer.
• Depop’s risk engine might silently flag your personal number because of its history. A fresh temp number backed by a physical SIM often solves this instantly.
• For long-term sellers, rental numbers (1–30 days) are a lifesaver. They prevent re-verification friction and, bonus, keep your private number out of Depop’s marketing systems.

Why Does Depop Keeps Saying Wrong OTP Even When the Code Looks Right?

Here’s the thing: that error message isn’t always a verdict on your typing skills. Most of the time, wrong OTP means the code you punched in was already dead on arrival, expired, never actually delivered, or tied to a different session entirely.

OTPs are single-use and time-bound. They’re usually valid for ten minutes or less. So a code that looks flawless can still be rejected if you took too long to enter it or if your phone’s auto-fill swooped in with an older, outdated one. It’s a session or timing problem, not a you problem.

• Server-side timestamps rule everything. The code’s expiry time is calculated on Depop’s server, not your phone. If you copy it after the window closes, it’s dead, even if it hit your inbox seconds ago.
• Carrier delays are real. SMS can be delayed by 5–15 minutes depending on your network. If you request a new code while the old one is still in transit, you set yourself up for a new code that says an incorrect loop.
• Session-locked codes. Request a code on the web app? It won’t work on the mobile app, and vice versa. The code is tied to the specific session where you requested it.
• Auto-fill is a double-edged sword. Android and iOS auto-fill often grab the wrong (older) code if you have multiple SMS messages with PINs. Sometimes, typing it manually fixes it.
• Depop plays it close to the vest. They don’t publish an official OTP expiry window, but in practice, codes expire fast, usually well under 10 minutes.

The takeaway? That error message doesn’t always mean you typed digits wrong. It means Depop’s server rejected the code for some reason. Once you wrap your head around that distinction, you’re halfway to fixing it.

The 5 Most Common Depop OTP Incorrect Message Triggers and How to Spot Them

Let’s break down the usual suspects behind that infuriating error. There are five main culprits: an expired code, a new code overwriting the old one, copy-paste errors with stray spaces, using a number that’s been previously banned, or a carrier that’s quietly filtering Depop’s SMS messages.

The good news? Each trigger has a distinct pattern. Spotting which one you’re dealing with tells you exactly what to do next.

• Expired code: The error appears after a delay. Check the timestamp on the SMS. Fix: request a new code and enter it immediately, like, now.
• Overwritten code: You hit resend, so the old code is void. Only the most recent message matters. Full stop.
• Copy-paste error: Spaces or extra characters sneak in. The depop wrong code error appears instantly on submit. Fix: use Tap to fill or type it manually.
• Blocked/non-VoIP number: Depop rejects certain number ranges outright. If you used a VoIP or recycled number, the error is systemic and won’t clear no matter how many times you retry.
• Carrier filtering: Some mobile providers flag Depop’s SMS shortcodes as spam, delaying delivery until the code is uselessly expired.

Spotting the trigger is half the battle. Instant error? It’s almost certainly input-related space, a hyphen, or auto-fill grabbing a stale code. Error after a few seconds? Likely expiry or session mismatch. And if it happens every single time no matter what you do, your number itself might be the problem.

Step 1: The 60-Second Fix Check Your Time Zone and Auto-Fill Settings.

Here’s a sneaky one: your phone’s time zone. If it’s off by even a few minutes, Depop’s OTP server will reject your code as expired because validation is timestamp-based. That’s a hard pass from the server before you even get a chance.

Also, those helpful auto-fill bars on iOS and Android? They often pluck the wrong code from your thread, usually an older, invalid one. Fixing the depop otp not accepted troubleshooting saga often starts with clearing that suggestion bar and double-checking your clock.

• Set your device time to Automatic in Settings > General (iOS) or Settings > System > Date & Time (Android). Manual time zones cause silent, infuriating mismatches.
• Temporarily disable iMessage/Android Messages OTP auto-fill. That suggestion bar can show a stale, invalid code from a previous request.
• Restart your messaging app after requesting a new code. Some clients don’t refresh the notification shade in real time, leaving you staring at ghost notifications.
• VPN users, listen up. If you’re running a VPN that routes through another country, turn it off. Depop may compare your IP to the number’s country code, flag the mismatch, and silently kill the code.

This step takes under a minute and resolves a surprising number of wrong OTP reports. Seriously. A clock off by five minutes can trigger a validation failure because the server calculates expiry from its own timestamp, not yours. And VPN-related mismatches are more common than you’d think Depop’s risk engine sees a different country IP and gets suspicious.

Step 2: What to Do When Depop Verification Code Not Working After Multiple Attempts

Okay, so you’ve tried 3+ codes, and every single one came back invalid. Stop. Put the phone down. Do not request another code.

Here’s the deal: your account is now in a lockout window, and continued attempts extend the cooldown. Depop’s anti-fraud system (like most verification platforms) scores failed OTP attempts against your account’s risk profile. Hit a threshold, and you get a temporary block. The fix is frustratingly simple: patience.

• Wait 15–30 minutes. Then request exactly one new code. Enter it within 60 seconds. That’s the whole plan.
• Depop and its verification vendors enforce rate limits. After 3 failures, the next code is often blanked entirely, you’ll get nothing.
• A lockout doesn’t mean a ban. It’s a rolling timer. Wait a full 30 minutes before even thinking about trying again.
• Do NOT, under any circumstances, use Resend Code more than once per session. Each resend invalidates the prior code and resets the timer. You’re just shooting yourself in the foot.
• On a VPN? Turn it off during the final attempt. IP rotation is a classic trigger for repeated wrong OTP errors.
• Check if your number is international. Depop sometimes has delivery gaps for non-US carriers, and the code may never arrive.

The hardest part of this step is doing nothing. Your instinct screams to keep requesting codes, to keep trying. But every failed attempt digs the hole deeper. Depop’s risk engine scores your account based on recent verification behavior, and repeated failures look like automated bot activity. Wait out the cooldown, then make one clean, careful attempt.

Step 3: The Resend Code Trap Why Depop Wrong OTP After Resending Code Happens

This trap catches more people than any other single issue. Let’s walk through it.

You request a code. You wait 30 seconds. You get impatient. You hit Resend Code. Depop kills the previous code and issues a new one. But then, two minutes later, the original text finally lands because your carrier was holding onto it. Now you have two codes in your inbox, and only the latest one is valid. Which one do you enter? If you’re like most people, you grab the first one you see which is the wrong one.

Every time you hit Resend Code, Depop nukes the previous code and issues a new one. If the original text finally lands after a carrier delay, you’ve got two codes, and only one is live. The rule is simple: always use the last message that arrived, never the first.

• SMS carriers can hold a message for several minutes. If you resend after 30 seconds, the old code may arrive 2 minutes later and confuse everything.
• This wrong OTP after resending code error is almost always a user-input issue, not a system bug. Check the newest timestamp in your SMS app and use that one.
• Does Depop offer an alternative delivery method? Sometimes email OTP is available. Use it. It sidesteps SMS carrier delays entirely.
• Resend more than twice in a row, and you’re flirting with Depop’s risk engine flagging you as bot-like. It may intentionally send a code that fails to mess with you.
• Digital SMS platforms like PVAPins deliver codes instantly without carrier throttling, which eliminates the resend trap altogether. Check out our SMS service for instant delivery.

The resend trap is a silent killer. You request a code, wait, get impatient, hit resend, and then the original text finally lands. Now you’re racing the clock on the wrong code. The fix is simple: always check the timestamp and use the most recent message.

Step 4: Carrier and SIM-Level Issues Why the Depop Wrong Code Error Isn’t Your Fault

Sometimes, you’ve done everything right, and it’s still broken. That’s when you have to look at the carrier. The problem might not be your input it could be your carrier silently blocking Depop’s shortcode, or your SIM having a history of ported numbers that trigger Depop’s risk flags.

T-Mobile, Verizon, and many MVNOs filter shortcodes from unknown senders. If your number was previously used for spam, the code may never arrive, or it may arrive blank. If you’ve ruled out input errors, test with a different number before you assume your account is cursed.

• Shortcode blocking is common with prepaid plans and MVNOs (like Mint, Visible, or Google Fi). Depop uses shortcodes for US numbers, and these networks sometimes throttle them.
• You can call your carrier to unblock shortcodes for Depop’s sender, but brace yourself it’s a slow process, often 24–48 hours.
• Ported numbers can be a nightmare. If your number was ported from a different carrier, SMS routing may point to the old network, causing permanent non-delivery.
• A quick test: try verifying on a different platform (like WhatsApp) with the same number. If that works, the issue is Depop-specific, not a carrier-wide problem.
• The Depop wrong code error appearing instantly with valid input and no delay almost always points to a software/versioning glitch, not your SIM.

Carrier-side blocking is frustrating because it’s entirely outside your control. You can’t fix a network that’s silently dropping Depop’s shortcodes, and you can’t force a ported number to route correctly if the old carrier is holding onto the SMS. But you can test around it. And if your number is the problem, the solution is a fresh one.

Step 5: Clear App Cache and Reinstall The Nuclear Option That Actually Works

If you’ve verified your clock, auto-fill, and code freshness, and you’re still stuck, it’s time to get aggressive. Clear the Depop app’s cache. It often holds a corrupted session token that makes every OTP attempt fail.

A simple cache clear works in about 60% of cases. A full reinstall fixes the remaining issues by resetting the device-to-server session link. After reinstalling, request a brand-new code. Don’t reuse any previous ones; they’re all dead.

• Android: Settings > Apps > Depop > Storage > Clear Cache (do NOT clear data yet; that wipes your login session).
• iOS: You can’t selectively clear cache. You must offload the app (Settings > General > iPhone Storage > Offload App) and reinstall from the App Store.
• After reinstall, log in with your email/password, not Continue with Google/Apple, to avoid stale token confusion.
• Update the app to the latest version. Old builds have known bugs where the new code says incorrect error persists despite valid input.
• If the error persists after a clean reinstall, the issue is on Depop’s server side. Move to H2 #9 to contact support properly.

It’s called the nuclear option for a reason it nukes the local session state that might be corrupted. Depop’s app stores a session token on your device. If that token gets out of sync with the server, every OTP attempt can fail even with a valid code. A fresh install resets that link and gives you a clean slate.

Why Your Real SIM Number Might Be the Problem and How Privacy Tools Help

This is the part nobody wants to hear, but it’s increasingly the reality: your personal number carries history. Data breaches. Spam report sporting records. Depop’s risk engine can silently block it for OTP delivery without telling you.

If you’ve tried everything and still get wrong OTP, the verification system might be rejecting the number itself, not your code input. Your typing isn’t the problem. Your number is.

• Risk engines score numbers by activation date, abuse history, and carrier type. Old numbers with public breach records may be deprioritized.
• A virtual SMS number from PVAPins has a clean history and is delivered instantly via real SIM infrastructure, reducing carrier filtering.
• Critical note: Depop prohibits VoIP numbers. So use a physical-SIM-based virtual number provider, not Google Voice or TextNow. This is a hard rule.
• Virtual numbers are also useful for one-time verification if you want to keep your private number off Depop’s marketing lists. Privacy wins.
• If you’ve accidentally burned your personal number on too many failed attempts, a fresh number resets the risk score entirely.

PVAPins is not affiliated with any app or website. Please follow each app’s terms and local regulations.

The idea that your own phone number could be the problem feels counterintuitive, but it’s becoming more common. Data breaches have exposed billions of phone numbers, and risk engines now score numbers based on that exposure. A fresh number with clean history bypasses that baggage entirely.

When to Stop Troubleshooting: How to Contact Depop Support the Right Way

You’ve tried every fix in this guide. Depop still says the wrong OTP. At this point, the issue is likely a permanent flag on your number or a known backend bug. Time to escalate to Depop’s support team.

Contacting them correctly speeds up resolution. Give them all the context they need upfront: your device model, app version, the exact error text, and the timestamp of the last failed attempt. Do not send screenshots of your SMS messages. Depop support will never ask for a code, and sharing it is a phishing risk.

• Use Depop’s in-app help portal (Settings > Help) to create a ticket. Include a short video screen recording showing the incorrect OTP error. It’s compelling evidence.
• Mention you’ve already completed the basics: time sync, auto-fill disable, cache clear, and reinstall. This proves you’re not a bot and saves a round-trip.
• Ask support to reset the OTP session counter specifically. This is a known fix for accounts stuck in a lockout loop.
• Expect a 24–72 hour turnaround. Depop outsources verification to a third party, and support staff must escalate to that vendor.
• If Depop support confirms your number is not eligible, that’s permanent. Your only fix is a different phone number.

Escalating to support is the right move when you’ve exhausted every user-side fix, but do it smart. Provide all the context they need in the first message so you don’t spend days going back and forth. And never, ever share your actual verification codes with anyone claiming to be supporting legitimate teams won’t ask.

If Depop confirms your number is not eligible, don’t burn a week fighting it. Get a fresh virtual SMS number with a clean verification history and complete your Depop signup in under two minutes.

What If You Need a Number That Lasts? Using Rental Numbers for Repeated Depop OTPs

A one-time code isn’t enough for everyone. If you’re selling on Depop regularly and need to re-verify your account monthly, or if you’re testing multiple accounts for business purposes, you need a rental number that can receive OTPs over days or weeks.

Rental numbers provide long-form SMS verification without exposing your personal SIM. They keep the same number active so future codes work without re-verification friction. This is the practical solution for users who need ongoing, reliable access.

• PVAPins offers rental numbers for 1, 3, 7, and 30-day windowsideal for Depop sellers who need to re-verify after a password reset or device change.
• Rental numbers are tied to physical SIM infrastructure, not VoIP, so they pass Depop’s verification filters.
• If your personal number is permanently blocked by Depop, a rental number gives you a clean identity for legitimate selling.
• Rentals also solve the code expiry problem: you control when you receive the SMS so that you can enter it instantly.
• Compliance note: Use rentals for your own accounts only. Creating duplicate accounts in violation of Depop’s terms is not supported.

Rental numbers fill a specific gap. They’re for users who need ongoing verification, not one-time signups. If you’re a regular seller who hits verification prompts every few weeks, a rental number eliminates the headache of re-verifying with a personal SIM that may or may not cooperate.

The Developer Angle: Testing Depop OTP Flows in Your Own App

If you’re a developer building a marketplace that needs OTP verification, Depop’s wrong OTP issue is a masterclass in what not to do. The common failure patterns expired timestamps, session mismatches, and resend loops are bugs you can architect against from day one.

PVAPins offers a developer API that lets you request numbers and poll OTP status programmatically. You can test SMS flows across 200+ countries without burning your real SIM. It’s a game-changer for QA testing.

• Building the latest code wins logic. Never store multiple OTPs for one phone number. Always overwrite with the most recent request. This kills the resend trap at the source.
• Use a 10-minute expiry window server-side, validated against the user’s local time, not your server’s UTC offset. Timezone mismatches are a silent killer.
• Rate-limit resend requests to 1 per 60 seconds, max 3 per 10 minutes. This prevents the lockout trap entirely.
• Log the wrong OTP event with the full timestamp and device ID. This is the data you need to debug carrier delays when things go wrong.
• Test against a reliable SMS API that returns delivery status webhooks. Then you’ll know when to prompt the user for input, not just hope.

The developer angle matters because the wrong OTP problem isn’t unique to Depopit’s systemic SMS verification. If you’re building your own marketplace, you’ll face the same challenges. Solving them at the architecture level saves your users the same frustration. Depop’s approach includes rate limiting and session-bound codes, but the UX still suffers when carriers fail.

The 10-Minute Quick-Start Checklist to Resolve Depop OTP Error

This is the fast path for anyone who doesn’t want to read the whole guide. Follow these eight steps in order, and you’ll resolve 90% of wrong OTP issues in under 10 minutes. If you hit step 5 and it’s still broken, skip to step 7 for the nuclear option.

The checklist is designed to eliminate the most common causes first (which are all user-side) before you waste time contacting support.

• Force-quit the Depop app and reopen it (clears in-memory session state).
• Set your phone clock to Automatic in system settings.
• Turn off OTP auto-fill in your message settings temporarily.
• Request ONE new code and type it manually don’t copy-paste.
• If it fails, wait 15 minutes (lockout window) without requesting another code.
• Clear Depop’s cache (Android) or offload the app (iOS) and reinstall.
• If it fails again, try using a different phone number, ideally a virtual SMS number from PVAPins.
• If a new number works, your old number is flagged contact Depop support to confirm.

Follow these steps in order, and don’t skip ahead. Each step eliminates a specific cause, and jumping around makes it impossible to know what actually fixed the problem. The checklist is ordered by likelihood, so the most common fixes come first.

Want to skip the carrier delay entirely? Test with a free or low-cost temporary number to see if the problem is Depop’s code or your SIM. Grab a number for under $0.10 and verify instantly.

Preventing Future Depop OTP Repeated Errors: Pro Habits for a Clean Verification

The wrong OTP message is almost always preventable if you follow a few simple rules. Never request a new code before entering the current one. Always enter codes within 2 minutes of arrival. And never reuse a number that has failed three times in a row.

Building these habits reduces your risk of triggering Depop’s anti-fraud lockout, which is the real culprit behind any Depop verification code not working issue. Prevention is easier than the fix.

• Keep your SMS inbox clean. Delete old OTP messages after use so auto-fill never suggests a stale code.
• Use a dedicated number for verification for business/developer testing. Don’t use your personal number for trial and error.
• Log out of Depop on old devices. If you’re verifying on a new device, log out on the old one first. Dual active sessions can cause verification token conflicts.
• Update the Depop app monthly. Security patches frequently change how OTP validation behaves on the backend.
• Enable 2FA. After successful verification, save your confirmation email and enable in-app 2FA (if available) to reduce future OTP dependencies.

Prevention comes down to treating OTP codes with the same care you’d treat a password. They’re single-use, time-bound, and session-specific. When you respect those constraints, the wrong OTP error all but disappears.

Key Takeaways

• Depop’s wrong OTP error is rarely a typo; it’s an expired code, a resend conflict, or a number-level flag.
• The fastest fixes are checking your device clock, turning off auto-fill, and waiting out lockout windows instead of hammering resend.
• Your personal number’s history can work against you; a fresh virtual SMS number with a physical SIM resets the risk score.
• For ongoing needs, rental numbers prevent repeated verification failures and keep your private number private.
• If you’ve exhausted every user-side fix, Depop support can reset your OTP session counter but expect 24–72 hours.

FAQ

Is it legal to use a temporary number for Depop verification?

Yes, using a temporary number for basic account verification is legal, as long as you’re not evading a ban or violating Depop’s terms. If you use a temp number to create a second seller account to bypass a suspension, that violates Depop’s anti-fraud policies.

Why does Depop keep saying the OTP is wrong when I just got the text?

The most common reason is that the code has already expired Depop’s OTPs are valid for a very short window, typically under 10 minutes. Carrier delay means the SMS lands after the code is dead. If you pressed Resend at any point, only the latest code works; older ones are instantly invalidated.

What’s the difference between a one-time number and a rental number for Depop?

A one-time number is for a single verification and is discarded afterward it solves the I’ll never need this again case. A rental number stays active for 1–30 days, letting you receive multiple OTPs over time. For repeat Depop use, rent a number.

What should I NOT use a temporary number for?

Never use temp numbers for financial services (banks, PayPal, crypto exchanges), healthcare portals, or government accounts that require a real, active number for regulatory and security reasons. Also, never use temp numbers for fraud, spam, or creating duplicate Depop accounts to evade a ban.

How long does Depop’s OTP lockout last after multiple wrong codes?

There’s no official public figure, but community testing suggests a 30–60 minute cooldown after three failed attempts. Don’t keep trying during the lockout; it can extend the timer. Wait a full hour, then request exactly one new code and enter it immediately.

Can a VPN cause Depop to say the wrong OTP?

Yes. If your VPN IP doesn’t match the country code of the phone number you’re verifying, Depop’s risk engine may flag the session and silently invalidate codes. Disable the VPN during verification, or set your VPN location to match the number’s country.

Compliance Note: PVAPins is not affiliated with any app or website. Please follow each app’s terms and local regulations.

Also Helpful: The same privacy-friendly tricks work across platforms see our guide on EasyPay Keeps Saying Wrong OTP if you use multiple inboxes.