Amazon Appstore Developer Verification Stuck – Support Ticket Escalation / Urgent Help Needed

I’m currently facing the same issue described by others in this forum regarding developer verification failing multiple times on the Amazon Appstore, and I’m completely stuck without a clear path forward.

Issue Summary

Developer verification failed 2–3 times during the process.

After multiple failed attempts, the system now prompts me to contact support.

Current Status

I have already submitted a support ticket regarding this verification issue.

The ticket remains open but is not progressing, and I have not received any meaningful human response or actionable guidance.

My Request

Since this issue is actively blocking our app release and business operations, I would like to formally request that my existing support ticket be escalated and marked as urgent.

Could someone from the Amazon Appstore team please:

Review my open support ticket and provide a human response.

Escalate the ticket for faster resolution.

Advise if there is any direct channel or additional step I can take to move the verification forward.

Any help to get this resolved promptly would be greatly appreciated.

Hello,

Please make sure to use the exact name as it appears on your ID. If your ID name is in non-English characters, please enter it in those characters under the Full Legal Name field. You can safely ignore the “The name entered contains special characters” notification.

Hi,Emma

Thank you for your response.

I wanted to update you on my current situation:

  • I am no longer able to attempt the verification again — the system has locked me out after multiple failed attempts.
  • My support ticket has already been submitted:
    • Ticket ID: 20276858141
    • Status: Work in progress

Given that this issue is currently blocking our app release and business operations, could you please help check if this ticket can be escalated or processed with urgency?

Any assistance to move this forward would be greatly appreciated.

Thank you!

I have been experiencing the same issue too. Even after committing to the logistics and instructions given to me by their Support Team