← Back home

Verification guides

When a platform asks for a second ID: what to send and what to withhold

A second ID request is routine — but the wrong reply can put your identity at risk. Here is how to answer it calmly and send exactly what is needed.

Business owner reviewing identity documents beside a laptop showing a verification screen

The short version

A second ID request is normal — it usually follows a payout change, a new device, or a routine review. Send exactly the document asked for, through the platform's own portal. Never send card photos, passwords, codes, or a full Social Security number by email or chat. Before you send anything, log in directly and check the request is really waiting there.

Why platforms ask for a second ID

A second ID request almost never means you did something wrong. Platforms check identity in layers: the first confirms who you are, and a later one confirms the person using the account is still the same person, or that the business behind it is what it claims to be. That second layer can be triggered by something ordinary — a large payout, a login from a new device or location, a change to payout details, or a routine re-verification cycle.

It can also follow a purchase: when an account changes hands, the platform cannot know the new operator is legitimate until something is checked again. The right response is calm and precise — exactly what was asked for, in the channel it was asked for, and nothing extra.

The danger is not the request itself. It is over-sharing in response to it — sending full, unredacted documents, passwords, or sensitive numbers the platform never needed, through a channel the platform never offered. This guide draws the line: what to send, what to withhold, and how to tell a real request from a fake one.

What a second ID usually means

The phrase second ID covers three different requests. The first is a second photo ID: the platform already has one government-issued document on file and wants another — a driving licence when it already holds a passport, for example. Two independent documents with the same name, date of birth, and photo are much harder to fake than one.

The second is a proof-of-address document to pair with the ID it already has: a utility bill, bank statement, or tax letter, showing the same name and address as the account. This is the most common second request for business accounts, because a business address can change while the owner's identity stays the same.

The third is a liveness or selfie check: a short video or photo of yourself holding the ID, or turning your head on camera, so the platform can match the live face to the photo on the document. It feels intrusive, but it is also the hardest to fake, which is why platforms rely on it when the risk is highest, such as after a payout-method change. Before you send anything, work out which of the three you received — a platform that asks for a second photo ID does not need your bank statement.

What is safe to send

A government-issued photo ID is safe to send when the platform asked for it, the upload goes through the platform's own secure portal, and the document is current and clearly legible. Passport, driving licence, or state ID — whichever one the platform lists as accepted. Send only the pages or sides the platform asks for.

A proof-of-address document is safe to send when it is recent, shows your name and address exactly as they appear on the account, and comes from a recognised issuer — a bank, a utility company, or a tax authority. A PDF from the issuer is better than a phone photo of a paper bill: cleaner, harder to tamper with, and clearly issued.

A selfie or liveness check is safe to complete inside the platform's own app or upload flow, in good light against a plain background. A business document is safe to send when the platform asked for it by name — a formation certificate, an EIN letter, or a business bank statement — not your entire company file.

What to withhold — even when asked

Never send a photo of a payment card, front or back, even partially. No legitimate verification flow needs your card number, expiry date, or security code, and a card image in a support inbox is a fraud risk that outlives the review. If a message asks for a card photo, treat the message itself as suspect.

Never send your password, a one-time code, a 2FA seed, or backup codes. No platform employee will ever need these to verify you, and anyone who asks for them is either a scammer or testing whether you are careless. A real verification request is about documents, not about handing over access.

Never send a full, unredacted Social Security number in an image or a chat message. Some platforms ask for the last four digits during verification — that is normal. A request for the full number, or a photo of the card itself, outside the platform's encrypted onboarding form, is not. If the platform genuinely needs it, it will collect it through its own secure form, not through email or chat.

Never send documents the platform did not ask for. Extra documents do not speed a review up; they widen the exposure if the support ticket or chat is ever breached. If you are unsure whether a document is needed, ask support in writing first. And never send documents to an address or link from an unexpected email or message — the upload channel matters as much as the document.

How to send documents safely

Upload through the platform's own portal whenever possible. Log in the way you normally log in — type the address yourself or use the app you already have installed — and find the verification task inside your account. If the request arrived by email, do not click the link in the email. Go to the platform directly and check whether the same request is waiting in your dashboard. If it is not there, the email may not be genuine.

Check that the file you upload is clean and legible. A blurry photo is the most common reason a second ID gets rejected, and a rejection usually means another round of uploads and another delay. Use a flat surface, even lighting, no glare, and all four corners of the document visible. If the platform accepts PDFs, prefer the PDF over a photo.

Redact what was not asked for. If you must send a bank statement as proof of address, cover the account number and transaction history — the platform needs your name, address, and the bank's letterhead, not your balance or spending. Keep the original untouched and send the redacted copy.

Keep a record of what you sent and when: the redacted files, the date, and the ticket or case number. If the same request comes again, you will not send the same documents twice through different channels.

A real request vs. a phishing request

A real second ID request arrives inside your account — a task, banner, or notification when you log in directly — usually with a matching email from the platform's own domain. The email tells you to log in and complete the step; it does not ask you to reply with documents attached.

A phishing request does the opposite. It arrives out of the blue, often with urgency: your account will be closed today, your payouts will be frozen, act now. It asks you to reply to the email with documents attached, or to click a link and upload them on a page that looks almost like the platform but is not. The sender address is close but wrong — a different domain, a free email provider, or a display name that does not match the address behind it.

Check three things before you trust any request. First, the sender's domain: the platform's real domain, not a lookalike. Second, the destination: the safest test is to ignore the link, open the platform yourself, and see whether the same request is waiting there. Third, the ask: a real request names a specific document for the platform's own flow; a fake one asks for passwords, codes, card photos, or documents by reply email. If you are unsure, do nothing with the message — contact support through the platform's official help page instead.

If your second ID is rejected

A rejection is usually a quality problem, not a verdict on your identity: a blurry or cropped photo, an expired document, an address that does not match the account, or a name spelled differently across the two documents — a middle name on one and missing on the other. Read the rejection message carefully; it often says which of these it was.

Fix the specific problem and re-upload: retake a blurry photo in better light, update the account address before sending a matching proof-of-address document, or correct the account name through the platform's own name-change flow. Do not answer a rejection by sending more documents than asked for, or the same documents through a different channel — one clean upload through the right channel is the fastest route to approval.

If the same document is rejected twice without a clear reason, ask support in writing for the exact cause, and keep the ticket number and the reply. That record lets you escalate — and proves you tried in good faith if the review drags on.

A calm response plan, step by step

First, pause. A second ID request is routine, and the worst outcomes come from rushing — replying to a suspicious email, or uploading unredacted documents in a panic. Take ten minutes to verify the request before you send anything.

Second, verify it inside the platform. Log in directly, not through any link in the message, and check whether the request is waiting in your dashboard. If it is not, contact support through the official help page and ask.

Third, gather exactly what was asked for — one document, of the type named, current and legible. Redact anything the platform did not ask to see, and prefer a PDF from the issuer over a phone photo where you have the choice.

Fourth, upload through the platform's own portal, save your records, and wait. Reviews take time, and re-sending the same document through another channel does not move the queue faster.

Fifth, if the request is rejected, read the reason, fix that specific problem, and re-upload once. If it fails again without a clear reason, ask support in writing for the exact cause and keep the exchange on record.

Safe to send: a quick checklist

  • A current government photo ID the platform lists as accepted — passport, driving licence, or state ID.
  • A recent proof-of-address document from a bank, utility, or tax authority, matching the name and address on the account.
  • A selfie or liveness check completed inside the platform's own app or upload flow.
  • A business document the platform asked for by name, such as a formation certificate or EIN letter.
  • The last four digits of a tax ID when the platform's own secure form asks for them.

Red flags that mean stop and verify

  • The message asks for a photo of a payment card, front or back.
  • It asks for your password, a one-time code, a 2FA seed, or backup codes.
  • It asks you to reply to the email with documents attached instead of uploading in the dashboard.
  • The sender domain is a lookalike, a free email provider, or does not match the platform.
  • It threatens immediate closure or frozen payouts if you do not act within hours.
  • It asks for the full Social Security number or a photo of the card by email or chat.
  • The link leads to a page that looks like the platform but has a different address.

Match the request

Send the exact document type the platform asked for — nothing more, nothing less.

Use the portal

Upload inside the platform's own dashboard or app, never by reply email or chat.

Keep a record

Save what you sent, the date, and the ticket number — so you never send it twice.

Questions about verification on your account?

Every account in our catalog is verified before it reaches you, and our team can walk you through any verification step a platform asks for. Ask us anything before you send a document.