Well, since the Amazon KDP wants me to verify my KDP account, I have had no luck with it. Followed every rule in the book, but still the system can’t verify my identity.
My account isn’t new, never had any problem until now. Their customer service is less than useless.
Send them an email, so will see what happens. The worst part is that I may lose my account.
Any help, suggestions etc are very much appreciated.
Translating what you actually asked: “my account is about to disappear, my photo upload keeps failing for no reason I can see, customer service is a wall, and I don’t know what to do next.”
That’s the real question. The “ID won’t verify” part is the symptom — the panic underneath is account loss. Both get addressed below.
Quick listen-back (so you know I read it, not skimmed):
- Verification keeps failing despite you following every rule
- Account is established — never had problems before, so why now?
- CS was useless when you reached out
- You sent an email and are now in the “we’ll see” zone
- The real worry is losing the account entirely
Tone reads as frustrated-tired, not raging — that’s the right posture for what comes next. Reactive panic-mode would make this harder.
The Next 5 MinutesDo these four things before reading the rest.
| # | Action | Why |
|---|---|---|
 |
Stop hitting retry. Walk away for now, come back Friday. | Each fail counts toward a hidden 72-hour lockout |
 |
Pull out your passport. Look at the bottom two cryptic-looking lines on the photo page. | That’s what Amazon’s system actually reads — more below |
 |
Open KDP > Your account > Your identity in another tab. Don’t change anything yet. | We’ll audit it against your passport in 3 minutes |
 |
Open draft2digital.com in a third tab. Don’t sign up yet. | Your insurance policy for this weekend |
Done? Now slower.
The Thing Nobody Tells You FirstThe verification screen isn’t your problem.
The verification screen is the front door of a back-room process that already started. Something flipped your account into manual review — that’s the actual problem. The photo is just what they’re asking you to upload while the back room is busy looking at something else entirely.
That’s why “follow every rule” doesn’t work. You’re cleaning the front door over and over while the back-room concern hasn’t been touched.
The good news: in roughly 80% of these cases, once you figure out what flipped the account, verification clears on the first clean attempt afterward.
The other 20% need real escalation — covered below.
Quick Map of What’s Bugging You| What’s eating at you | What actually fixes it | Time |
|---|---|---|
| “I keep failing despite doing everything right” | Stop the retry loop, audit the trigger first | 5 min |
| “Why now, when nothing changed?” | Walk the 6-item trigger list — one of them did change | 10 min |
| “CS is a wall” | Skip the chat queue, use the real escalation route | 1 hr |
| “What if I lose everything I built?” | Set up parallel distribution this weekend | 15 min |
The 6 Possible TriggersThe 2025–2026 wave of “established account suddenly fails verification” almost always traces to one of these. Walk through honestly — one of them is yours. Click the one that sounds most like your last 6 months for the specific fix.
Name, address, phone, country — even fixing a typo counts.
If yes — the system is asking you to re-prove the new info matches a real person. Totally normal, fixable in one clean attempt.
Amazon spells this out themselves:
“After editing your account, we may ask you to verify your identity. If you previously verified your identity, you will need to re-verify once you save changes.” (their docs)
Fix: Make sure your current “Your identity” name matches your passport’s MRZ format (next section), then retry from a stable home connection on mobile.
Network signature mismatch is one of the cleanest triggers.
If yes — your network signature didn’t match your usual one.
Fix: Disable VPN, log in from your home wifi on your usual phone, then retry. If you’ve been travelling, do the verification from your home address only — borrow a relative’s wifi if needed.
Amazon hard-caps at 3 titles per day. Going over flags as “abusive behavior” — even if those uploads succeeded.
If yes — you tripped the velocity flag, and it stays on the record for some time.
Fix: No active fix needed beyond waiting it out. Don’t repeat the pattern. Build the packet with this disclosed honestly in the email — they’re not going to terminate over this alone, and being upfront helps you in the manual review.
This is the big one for 2026. The system runs writing-pattern detection on a delay. Re-verification is the first soft-touch response — way before any title removal.
“Amazon uses a combination of automated detection (analyzing writing patterns, metadata, and submission velocity) and human review to identify potential AI content.” — Inkfluence’s 2026 enforcement breakdown
If yes — even with proper disclosure, the detector can re-flag established authors retroactively when patterns get reanalyzed.
Fix: Confirm every AI-touched title has the disclosure checkbox set. If anything was published before the disclosure was required, edit-and-resave each title with the disclosure checked. In your email, lead with this honestly.
Even one rejected complaint stays on the record. Plagiarism complaints, copyright complaints, content-policy complaints, even disgruntled-customer complaints.
Fix: Check your KDP > Bookshelf for any title with a yellow/red status flag. If yes, that’s likely the trigger — address it directly in your email with proof of rights/originality.
This bites Indian authors specifically — silent killer.
The verification system cross-checks three name fields that often don’t align: your KDP profile, your government ID, and your W-8BEN tax form. Three different versions of one person = three different people to the system.
Full breakdown in the next section.
Pick the one that matches your last 6 months. That answer changes everything else in this post — your email subject line, your packet contents, and which escalation route is worth burning early.
The MRZ Trick (the move almost nobody mentions)Pull out your passport. Look at the bottom of the photo page — those two strange-looking lines like:
P<INDMISTRY<<RAVI<KUMAR<<<<<<<<<<<<<<<<<<<<<<
M1234567<2INDxxxxxxx...
That’s the Machine Readable Zone (MRZ) — the part of every passport built specifically for machines to read, standardised globally since 1980. Every major identity-verification vendor (Onfido, Veriff, Jumio — the kind Amazon uses behind the scenes) treats the MRZ as canonical truth.
If the printed text disagrees with the MRZ, MRZ wins.
So:
| Your MRZ shows | Your KDP “Full name” should be |
|---|---|
MISTRY<<RAVI<KUMAR |
Ravi Kumar Mistry |
SHARMA<<PRIYA<<<<<<< |
Priya Sharma |
PATEL<<NIRAV<JAYESH<KUMAR |
Nirav Jayesh Kumar Patel |
Format the system actually parses — not the format you’d write on a school form.
The first line of your MRZ has this structure:
P<COUNTRYSURNAME<<GIVEN<NAMES<<<<<<<<<<<<<<<<<<<
P = passportCOUNTRY = 3-letter country code (IND for India)SURNAME = your family name in caps<< = double angle bracket separates surname from given namesGIVEN<NAMES = your given names, single < between them<<<<<< = filler characters padding to fixed lengthRead the surname (between country code and <<) and the given names (after << until the filler). Flip the order so given names come first, replace < with spaces, and that’s your KDP “Full name” field.
Apostrophes, dots, and accents get stripped in MRZ. If your printed name is D'Souza, the MRZ shows DSOUZA. Use D'Souza (with apostrophe) on KDP — the system normalizes both, but match the printed-text spelling for the human-readable field.
Three Other Indian-Specific TrapsThe India-USA tax treaty (DTAA) lets you claim a reduced 15% withholding rate on royalties — but only if you provide your PAN as your foreign tax identification number on the W-8BEN form.
Worse: a missing or mismatched PAN can desync your tax profile from your identity profile, and that desync is itself a re-verification trigger.
Fix: Go to KDP > Tax Information > Update Tax Profile. Confirm your PAN is entered as the foreign TIN. Save.
Reference: ShoutMeLoud explains the DTAA mechanics for Indian authors.
Amazon technically accepts state-issued documents (Maharashtra DL, voter ID, Aadhaar variants), but the global verification engine handles passports cleanest because of the standardised MRZ.
State-issued documents have inconsistent OCR results across regional variations.
Fix: Use passport every time. If you don’t have one, that’s its own conversation — different post for that situation.
Indian forms often default to surname-first (SHARMA RAVI KUMAR on PAN), western forms default to given-name-first (Ravi Kumar Sharma on KDP), and your passport’s printed name might be either.
The MRZ tells you which order Amazon’s system expects. Use that order on KDP, even if it feels backward from how you’d write it on an Indian form.
Build the Packet (the next hour)Before sending another anything, gather these in a folder on your laptop:
Screenshot of your KDP “Your identity” page with the failure banner High-res scan of your passport — both photo page AND address page Screenshot of your tax profile status page Screenshot of your “Your account” contact info section Account creation year + first published title year (proves established account, not a fresh ban-evasion attempt — important framing) List of every title you’ve published with ASINsThis is your Plan of Action packet. Same structure FBA sellers use — KDP runs on the same Amazon backend.
Gold reference: the deep dive by an actual former Amazon Bezos-team member.
I personally keep a folder called KDP-emergency updated every quarter with these exact screenshots. Once when a friend got hit with this same problem, having that folder ready cut a 3-week back-and-forth into a 4-day resolution because we sent every document Amazon asked for in the same hour. The paranoia pays for itself the one time you need it.
If you do nothing else from this post, do this. It takes 20 minutes once a quarter and saves you a month of headaches when something goes sideways.
The Real Escalation PathYou sent an email — good, that started the clock. Three things to know while it’s pending:
KDP has a phone callback line — submit a call request through the Contact Us form. Callback comes from 1-206-266-4064.
Skip regular Amazon CS entirely. They don’t know what KDP is. Going through them = circles.
The Bezos escalation ([email protected]) is real, but only after one solid POA + 7 business days of silence. Spamming Jeff prematurely burns the case.
| Day | What you do |
|---|---|
| Day 0 | The email you already sent — clock starts |
| Day 7 (business) | If silence: send to [email protected] |
Email subject for Day 7:
Escalation: KDP identity verification – [your account email] – [original case ID if any]
Email body opens with:
“I have already submitted the following request and received no meaningful reply within 7 business days.”
Attach your full packet. Executive Customer Relations (the team that quietly handles Bezos-inbox escalations) takes it from there.
If even Day 14 brings silence: paid services like AMZ Sellers Attorney handle KDP cases specifically. Direct legal-department lines for stuck cases. Pricey. Last resort, not first.
Phone reps can sometimes route to a manual review team that the chat queue can’t reach. The number 1-206-266-4064 is the legitimate KDP callback line (reference) — but you can’t dial it cold, that hits a different queue.
The flow: submit the form → request callback → wait for the call from that number → answer it.
Multiple authors on Kboards confirmed regular Amazon retail support has zero KDP knowledge — calling them is wasted time.
The Insurance Policy (this weekend)Most KDP authors skip this because it feels like giving up. It isn’t. It’s making sure that whatever happens with the appeal, you don’t lose your livelihood with one Amazon decision.
| Action | Time | Why |
|---|---|---|
| Download every royalty report + manuscript backup | 30 min | Before any access tightening |
| Open a free Draft2Digital account | 15 min | Pushes to Apple Books, B&N, Kobo, libraries |
| Note your KDP Select 90-day renewal dates — don’t re-enroll | 5 min | Frees titles to go wide |
| Set up IngramSpark for paperback | 30 min | Reaches bookstores + libraries |
The author who lost his KDP account permanently in February 2026 wrote about losing $50,000+ in royalties he’ll never recover. His only mistake was being on one platform when the decision came down.
That story is rare but not impossible — and it’s exactly why you don’t wait until after the verification fails permanently to set up parallel distribution. Set it up now while the appeal is pending. Best case: never needed. Worst case: it saves your business.
Quick reground: this is the playbook for an established account hit with sudden re-verification. Following these steps in order maximises your odds of clearing on the next clean attempt.
If you already know the basics: the only thing you might be missing is the MRZ-format name match — skip to step 3.
Step 1 — Stop the retry loop
Worked when: the verification page stops showing “too many attempts” on next visitStep 2 — Walk the trigger list
Worked when: you can finish “I think the system flagged me because…” with one specific cause, not “I don’t know”Step 3 — Audit your KDP profile against your passport’s MRZ
Worked when: green checkmark or “Saved” confirmation appearsStep 4 — Build the packet
KDP-verification-2026 on your desktopStep 5 — Retry verification ONCE, cleanly
If it passes — you’re done.
If it fails again — that confirms the issue isn’t photo-related, go to Step 6.Step 6 — Send the packet through the right channel
Identity verification – established account [account email] – multiple failed attempts despite matching ID Worked when: automated case-ID confirmation arrives within 24 hoursStep 7 — Wait 7 business days. Then escalate, but only if silent
[email protected] with the structure from aboveQuick situation → action lookup:
| If this happens | Do this |
|---|---|
| Page says “too many attempts” | Stop, wait 72 hours, don’t touch anything |
| Photo accepted but selfie fails | Retake selfie in daylight, no glasses, match ID expression |
| Both photos accepted but still fails | Issue is the trigger event — go through trigger list |
| First email got auto-reply only, no real response | Wait full 7 business days before escalating |
| Account terminated (worst case) | Work parallel-track plan, prep AMZ Sellers Attorney consult |
1. The MRZ trick on your passport — single highest-leverage fix in this whole post and almost no English-language KDP article mentions it.
2. Verification is a queue, not a person. Even after a clean re-verification, the original trigger that fired the manual review stays on your account record for some period. Keep your packet ready for 30 days afterward, in case round two happens — sometimes it does.
3. The selfie isn’t biometric matching. Amazon explicitly states “It is not used for biometric identification, and no biometric templates are created or stored.” (source)
Practical implication: it’s image-comparison only, fragile to lighting and angle. People fail because they smiled in their ID photo and look serious in the selfie, or vice versa. Match the expression of your ID photo, not just your face.
Your MoveYou said “sent them an email, will see what happens” — that part is fine, the clock is ticking from the day you sent it. While it’s pending, the audit-and-prepare work above is what you can actually control.
One question back to you:
Walking through the 6-item trigger list above, which one matches your last 6 months on KDP?
Once you name the trigger, the email subject line and the escalation path tighten up considerably, and we can tune the next steps to that specific cause instead of the generic ones laid out here.
You’ve been on KDP long enough that you’re not the first established account this has happened to in 2026 — and the framing that keeps people calm:
That’s exactly why the parallel-track setup matters this week, not later.
Done it all by the book, and my account will be shut 29/04
I don’t know why you posted all this, but I am not in India
!