Signup and verification
Verify your email, choose an account and recover access without merchant intake.
On this page
Get your first key with an email address and the required policy acceptance. No password, credit card, merchant website or account/application name is required.
Verify your email
Enter your email at developer signup, accept the Terms, Privacy Policy, Refund & Credit Policy and Acceptable Use Policy, then choose Continue with email. Enter the eight-digit code on the verification page.
The code expires in ten minutes, has a five-attempt limit and is subject to server throttling. Only the newest challenge is valid. Resend supersedes the earlier challenge; Change email returns to entry. Secure email-link compatibility remains, but visiting a link never redeems proof or creates resources by itself.
Your first key
Successful verification prepares a new developer’s Personal account, Default application and Default key, then shows the key-ready console. Save the secret when shown once. Names and settings can be changed later; there is no routine naming wizard.
Returning users reuse their authorized context without automatically receiving another key. An account/application picker appears only when the available contexts are genuinely ambiguous. Unavailable or revoked authority is not permission to create replacement ownership.
Stay signed in
The developer portal has its own host-only session, separate from the main site. Ordinary console browsing stays signed in for up to seven days from authentication, with expiry after twelve hours of inactivity. Sensitive administration requires proof from the last fifteen minutes.
A step-up challenge does not discard your ordinary session. Successful proof returns to the intended action; it does not silently carry out that action.
Recover safely
Delivery failure, an invalid code and an expired or already-used challenge are different states. Request a fresh challenge when required; never share a code with support.
If preparation completed but the response was lost, resume the existing preparation instead of creating duplicate accounts or keys. A secret that was not received is unavailable: inspect safe key metadata and explicitly replace the key. These instructions describe the release contract, not production deployment evidence.