When Platforms Ask for Documents Again: Handling Re-Verification Calmly

A re-verification request usually arrives as an ordinary-looking email or an in-app notice: a platform that verified your account months or years ago wants documents again. The wording is calm and bureaucratic — please confirm your identity, or we need to update our records — but the effect is not calm at all. Your first thought is that something has gone wrong, and your second is that your money, your clients or your trading positions might be frozen while you sort it out.

In most cases nothing has gone wrong. Platforms re-check accounts as a matter of routine: rules change, documents expire, risk systems flag a pattern, or a regulator asks the platform to refresh its records. A re-verification request is not an accusation, and it is not the same as a suspension. But how you respond in the first hours matters: a careful, complete reply usually ends the matter in days, while a rushed or incomplete one can turn a routine check into a weeks-long restriction.

This guide walks through the process in order: why platforms ask again, what they typically request, how to read the request properly before sending anything, how to prepare documents that pass on the first attempt, what to do while you wait, and what your options are if the answer comes back no.

The most common trigger is time. Identity documents expire, proof-of-address documents go stale, and the information a platform holds about you ages. Many platforms run periodic refreshes — every year or two — and ask account holders to confirm that the details on file are still current. If you have changed address, changed your name, or renewed your passport since you first verified, a refresh is likely, and it is not personal.

The second trigger is a change in the account itself. A new device, a login from a new country, a sudden change in transaction volume, a new payment method, or a change to the account's name or business details can all prompt a fresh check. Platforms compare current behaviour with the pattern they have on record, and a sharp break is exactly what their review systems are built to notice. The guide at /blog/what-a-clean-account-history-looks-like-to-a-risk-team explains what a healthy account history looks like from a platform's point of view — and a history that changes gradually is far less likely to trigger a re-check than one that changes all at once.

The third trigger sits outside your account entirely: rules change. Regulators update what platforms must collect, a platform launches in a new country, or a new type of risk — a fraud pattern, a sanctions update — forces every account in a category to be re-checked. When that happens the request will often mention a policy update or a regulatory requirement, and every account in the same group gets the same message at roughly the same time. There is nothing you did wrong, and there is usually nothing you could have done to avoid it.

A re-verification request normally asks for the same categories of document you supplied the first time: a government-issued photo ID, a proof of address dated within the last few months, and sometimes a selfie or a short video to confirm the ID belongs to the person holding the account. Business accounts may also be asked for a company registration document, a tax identification number, or evidence of who controls the business. The request should name each document it wants, and it should say what it will accept.

What a genuine request does not ask for is just as important. A platform will not ask for your password, your two-factor codes, your full card number, or your seed phrase — and it will not ask you to send documents to a personal email address or through a chat app. If a message asks for any of those, treat it as a phishing attempt, not a re-verification: go to the platform's official site or app yourself and check whether a notice is waiting there. The first-hour guide at /blog/what-to-do-in-the-first-hour-after-a-security-alert covers how to tell a genuine security notice from a fake one, and the same checks apply here.

Requests also vary in scope. Sometimes only one document is needed — a fresh proof of address because the old one is out of date. Sometimes the platform wants the full set again. The scope tells you something about the reason: a single-document request is usually a routine refresh, while a full re-check suggests a bigger trigger, such as a significant change in the account or a new regulatory requirement. Either way, the right response is the same — read the request, gather exactly what was asked for, and send it through the platform's own channel.

Before you upload anything, read the request twice — once for what it wants and once for what it implies. Note the deadline, because re-verification requests almost always carry one, and missing it is the easiest way to turn a routine check into a restriction. Note which documents are accepted and which are not: some platforms accept a utility bill but not a bank statement, or a passport but not a national ID card, and sending the wrong type wastes a review cycle.

Check whether the notice is actually from the platform. Open the platform's app or website directly — do not click links in the email — and look for a notification, banner or message in your account. A genuine request will be visible there. If nothing appears in your account, contact support through the official channel and ask whether a re-verification is open on your account. That single check protects you from the most common scam in this area: a fake re-verification email designed to harvest identity documents.

Finally, read the request for what it says about your account while the review runs. Some platforms keep everything working normally; others limit withdrawals, new transactions or changes to account details until the review is complete. Knowing the limits in advance lets you plan around them — finish time-sensitive transactions first if you are allowed to, warn clients or counterparties about a short delay, and avoid starting anything new that depends on the account until the review closes.

Most re-verification delays are not caused by the platform being slow; they are caused by documents that fail the first check and have to be re-submitted. The common failures are mundane: a photo that is cropped, blurry or taken in poor light; a document that has expired; a proof of address older than the platform's limit; a name spelled differently from the name on the account; an address that does not match the address on file. Each failed attempt adds days, so it is worth spending ten careful minutes on each document before you send it.

Photograph or scan each document flat, in good light, with all four corners visible and no glare across the text. Check that the name, date of birth and document number are legible in the image you are about to send — if you cannot read them on your own screen, the reviewer's system cannot either. For proof of address, use a recent document that shows your full name and current address exactly as they appear on the account; if you have moved since you first verified, update the address on the account first and then submit proof for the new one.

Keep the files you send, and keep a note of what you sent and when. A simple record — the document type, the date sent, the reference number the platform gave you — is enough, and it is the same habit the register guide recommends at /blog/building-a-simple-account-register-your-future-self-will-thank-you-for. If the platform later says a document is missing, you will be able to say precisely what was sent and when, instead of guessing. And never send documents through any channel other than the platform's own upload form or verified support channel.

Once the documents are in, the review usually takes a few days, though it can stretch longer if the platform is handling a large batch of re-checks at once. The worst thing you can do during that window is to keep changing things: logging in from new devices, adding new payment methods, or making unusually large transactions while a review is open can trigger a second look and extend the process. Keep your activity normal and steady until the review closes.

Watch for the platform's messages, and answer them promptly. Reviewers sometimes come back with a follow-up question — a clearer photo of one page, a different document for the same category — and a quick reply keeps the file moving. If you have login alerts switched on, keep them on: the guide at /blog/keeping-login-alerts-useful-instead-of-ignoring-them explains how to keep them useful rather than ignoring them, and a review period is exactly when an unexpected alert matters most.

If the review passes its stated timeframe with no word, contact support once, through the official channel, with your reference number and the date you submitted. One clear message is more effective than several, and it creates a record. Avoid the temptation to open duplicate tickets or to re-submit the same documents unprompted — duplicates slow the queue for everyone, including you.

A rejection is not necessarily final, but it is a message worth reading carefully. The platform should say why the documents were not accepted — an expired ID, an address mismatch, a document type it cannot use — and the reason tells you what to fix. If the reason is clear, fix it and re-submit: a new, valid document that addresses the stated problem is usually accepted. If the reason is vague, ask support to specify it before you send anything else, because guessing wastes another review cycle.

There is usually a limit to how many times you can try. Repeated rejections with the same documents rarely change the outcome, and each attempt can add a restriction to the account. If two attempts have failed for the same reason, stop and get the underlying problem fixed first — renew the document, correct the name or address on the account, or get a document in a format the platform accepts — before trying again.

In a small number of cases the answer stays no even after a clean submission. That usually means the platform has decided it cannot keep the account under its current rules, and no further document will change that. At that point the practical steps are to withdraw any funds the platform allows you to withdraw, keep copies of every message and submission for your records, and move your activity to a platform whose requirements you can meet. It is a frustrating outcome, but it is better than spending months in a loop of rejections.

This article is educational and does not constitute financial, legal or tax advice. Verification rules, document requirements and review procedures differ between platforms and change over time, so always check the current guidance on the platform you use, and take professional advice where a decision affects your business, your money or your legal obligations.