Pocket Option Changing Email and Credentials

Editing Your Login Details

Sign in first, then open the account or profile area of that session. The password and contact preferences are normally yours to edit directly; anything tied to your verified identity usually goes through the official support route instead.

Start from a screen you trust. Open the login page from a bookmark you saved yourself, from the address where you originally registered, then sign in and go looking for settings. Editing credentials on a page you reached through a message or an ad is how people hand an account away without noticing, which is why recognising a fake login page matters here more than almost anywhere. The two operator-run addresses verified on 31 July 2026 were pocketoption.com and po.trade; if the bar says anything else, go back to your bookmark.

Where account settings usually sit

On platforms of this kind the controls live behind your profile picture or initials in a corner of the signed-in interface, under a heading along the lines of Account, Profile or Settings, with a Security subsection holding the password and two-factor controls. Wording and placement can change without notice, and a mobile app often groups the same options differently from the browser, so treat any menu path you read, including this one, as a sketch rather than a map. If an option seems missing in the app, open the same account in a browser: the web interface generally exposes the fuller set of controls.

What you can normally change yourself

Credential edits split into two groups, and knowing which group a change belongs to saves you a wasted support ticket.

What tends to need support

Anything that touches your verified identity is deliberately harder to move, because the whole point of verification is that the account record and your documents agree. If the name or date of birth on the account is wrong, correct the account so it matches your documents, never the other way round: a document that misstates who you are or where you live is fraud, plainly stated and left there.

• Name or date of birth corrections after a marriage, a legal name change or a typo at registration.
• Country or residence updates after a move, which can change what the operator is willing to do with the account.
• Email changes when the old mailbox is gone, since the usual confirmation loop cannot close without it.
• Two-factor removal with no device and no backup codes, the hardest of all, which needs the official channel.

Reach support from inside the signed-in account or from the operator's own site, never from a phone number or link that arrived in a message. And whoever answers does not need your password or any code you were sent.

Edit credentials only from a session you opened yourself, and expect identity-linked details to move through support rather than through a settings toggle.

Changing Your Email

Add the new address while you still control the old one, confirm it through the link or code the platform sends, and only then stop using the previous mailbox. Doing it in that order avoids most lockouts.

The email on an account is not just a contact detail. It is the anchor for password resets, security notices and most recovery paths, which makes it the most consequential thing on this page. The good news is that changing it is straightforward while both mailboxes still work.

Updating the address you sign in with

Here is the sequence that goes wrong least often:

1. Get into the new mailbox first. Confirm you can send and receive from it on the device you will be holding when the confirmation lands.
2. Sign in from your own bookmark and open the account or profile settings area.
3. Enter the new address exactly, then read it back character by character. A single wrong letter creates a recovery problem you cannot see until you need recovery.
4. Re-enter your password if prompted. A sensitive change asking you to prove you are still you is the system working, not a glitch.
5. Open the confirmation message and follow the link or enter the code. Some platforms message the new address, some message each one, some do both in sequence.
6. Sign out and sign back in with the new address to prove the change took effect rather than merely appearing to.
7. Keep the old mailbox alive for a few weeks if you can, as a net while everything settles.

Getting the confirmation to arrive

Confirmation mail goes missing more often than accounts break. Before assuming the change failed, check the spam and promotions folders in the new mailbox, any filter or forwarding rule that might be quietly moving it, and whether a work or school mailbox is stripping external links. Corporate filtering is a common culprit, which is why a personal address you fully control is the better anchor for a trading account. If nothing arrives, wait before hammering resend: repeated requests can trigger rate-limiting on top of the original problem.

Keeping recovery in step

Once the login address changes, everything that pointed at the old one needs a look. If you sign in through an identity provider rather than an email and password, changing the email on the trading account does not change the account at that provider, and the two can drift apart in ways that surprise you later. Update your password manager entry the same minute you finish, not later. Check that any backup address on file is not the mailbox you have just abandoned. And if the reason for the change is that you lost control of the old mailbox, treat mailbox recovery as the prerequisite rather than the alternative: with the provider's own recovery done first, the platform-side password reset flow has somewhere to deliver to.

Change the email while both mailboxes still work, confirm through the message the platform sends, then sign in again with the new address to prove it stuck.

Changing Your Password

Use the change-password control inside a signed-in session rather than the reset link, pick a long unique passphrase no other site shares, and treat the forced re-login afterwards as a feature.

A password change is the fastest security action available to you, it costs about ninety seconds, and it is worth doing on a schedule you choose rather than only after a scare.

Doing it from inside the account

Two routes exist and they are not interchangeable. From inside a signed-in session you use the change-password control, which normally asks for the current password first; that check is what stops someone who has borrowed an unlocked device. From outside, when you cannot get in at all, you use the forgot-password link that mails a reset to the address on file. Use the inside route whenever you can still sign in, because it never depends on mail delivery.

1. Sign in from your bookmark, on a device and network you control.
2. Open the security section of your settings and choose the change-password option.
3. Enter the current password, then the new one twice, reading the second copy back before you submit.
4. Submit and watch for the confirmation, which may also arrive as an email notice.
5. Sign back in with the new password on your main device straight away.
6. Update your password manager, and delete any note of the old password from wherever you wrote it down.

Choosing a replacement worth having

Length beats decoration. Four or five unrelated words strung together are harder to crack and easier to type on a phone than a short string mangled with symbols, and a password manager makes even that unnecessary. What matters most is that this password exists nowhere else: credential stuffing, where attackers replay username and password pairs leaked from unrelated breaches, is how most trading accounts are taken over, and reuse is the only thing that makes it work.

• Unique to this account. Not a variation of your email password, and definitely not the email password itself.
• Long rather than clever. A memorable phrase of several words outperforms eight characters of punctuation.
• Free of your own data. Birthdays, names, the brand name and the year are the first things guessed.
• Changed immediately after any scare, including a phishing page you typed into before catching yourself.

The broader habits behind this sit on the login security basics page, and they apply as much to your mailbox as to the trading account.

Pushing other sessions out

Signing in on a second device does not sign you out of the first on platforms of this type. Balances and history live on the server, so every signed-in surface shows the same account state, and a session left open on a shared laptop or an old phone stays open. Some platforms publish an active-sessions list with a remote sign-out button; if yours does, use it. If not, do not hunt: changing the password is the universal fallback, because on essentially every platform of this kind it invalidates other sessions and forces a fresh login everywhere. Re-enable two-factor afterwards if the change reset it.

Change the password from inside a signed-in session, make it long and unique to this account, and let the resulting sign-out sweep old sessions off devices you no longer use.

Updating Recovery Options

Recovery details are what get you back in when the password fails. Review the backup address and phone, re-enrol two-factor deliberately when a device changes, and keep backup codes offline where you can reach them.

Most people set recovery options once at registration and never look again, then discover later that the backup address belongs to a job they left and the phone number to a country they no longer live in. Fifteen minutes now is cheaper than a support queue later.

Backup contact details

A secondary address and a phone number are the two levers that let a platform re-establish that you are the account holder, so both need to be reachable today, not in principle. Use a different provider for the backup address where you can: if one provider has an outage or locks you out, both eggs in that basket is exactly the failure you were guarding against.

• Test the backup mailbox by sending yourself something, rather than assuming the password you half-remember still works.
• Update the number before you change carrier, not after the old SIM goes dead, since recycled numbers are a real risk.
• Prefer app-based codes to text messages where you get the choice, because SIM swapping targets the text route specifically.
• Keep the two channels independent, so one compromised device does not hand over everything at once.

Re-enrolling two-factor after a device change

Two-factor authentication is a category rather than a single feature: authenticator app codes, codes delivered by mail or text, and one-time backup codes all behave differently under stress. Where an app offers the authenticator route, the code you read is generated on your device from a shared secret and a clock, rotating roughly every thirty seconds, which is why a phone whose time has drifted starts producing codes the server rejects even though nothing else is wrong. Automatic time sync fixes that in seconds.

The trap is the new phone. Authenticator secrets do not always travel in a phone backup, and if you wipe or sell the old handset before moving them, the codes go with it. Transfer in this order:

1. With the old device still working, sign in and open the two-factor section of your settings.
2. Turn the existing factor off, or start the re-enrolment flow if one is offered, confirming with your current code.
3. Enrol the new device, scanning the fresh code or entering the new key on it.
4. Verify a code from the new device before you close the page.
5. Generate a new set of backup codes, since the old set stops matching.
6. Only then wipe or hand over the old phone.

More on how the factor behaves at the sign-in screen is on the two-factor login page.

Storing backup codes properly

Backup codes are single-use keys that work when your normal factor is unavailable, which makes them both your safety net and a serious liability if they leak. Write them out and keep them somewhere physical: a wallet card, a drawer at home, a folder you already keep locked. A password manager is a reasonable second choice, though storing them beside the password they protect is weaker than keeping the two apart. What they must never do is travel: not in a chat message, not in a photo in your camera roll, and above all not to anyone who asks for them, however official they sound.

Keep a reachable backup address and phone on file, move two-factor before retiring the old phone, and store backup codes offline.

Verification for Sensitive Changes

Expect extra checks when you change an email, a password or a two-factor method. Confirmation prompts, short holds and cautious limits are normal, and planning for them keeps you out of a lockout.

The friction around credential changes is deliberate. If a stranger with your password could quietly swap the recovery email, the password would be the only thing standing between them and everything else. So the checks exist, and they land on you as well as on them.

Confirmation prompts you should expect

None of these means anything has gone wrong:

• Re-entering your password before a settings change is accepted.
• A code sent to the address or number already on file, not to the new one you just typed.
• A two-factor prompt on a change you did not think involved two-factor.
• A notification to the old address, which is your early warning if you did not request the change.
• A fresh device check on the next sign-in, because your old session was invalidated.

If a notice like that arrives and you did not start it, act on the assumption someone else did: change the password from a session you open yourself, re-enrol two-factor and generate new backup codes. Do not click the links in the notice to do it, since a message announcing a change is exactly the message an attacker would forge.

Holds and quiet cooling-off periods

Some changes settle instantly and some sit for a while. Across this product category the recognised categories are temporary rate-limiting after repeated failed attempts, holds pending verification, and restrictions following a terms breach; they look similar on screen and resolve very differently, so read the notice rather than guessing from the symptom. An account may also be treated more cautiously for a period after the recovery email or password changes.

Identity checks are the other side of this. Verification with photo ID, proof of address and proof of payment method is the standard pattern in this category, and it typically bites before a payout rather than before a first sign-in. Rejections cluster on mismatches, where a name, date of birth or country on the account does not line up with the document, and the fix is always to correct the account record rather than the document, through the official route covered on the page about signing in after verification.

One more thing before you edit a country field: the operator publishes its own limits on who it serves, and both verified addresses carried the same notice on 31 July 2026.

This website does not provide service to residents of the EEA countries, USA, Israel, UK, Philippines, Japan and Brazil.

Absence from that list is not a guarantee of the opposite. Registration, funding, verification and payout stay the operator's decisions and can change without notice. The practical point is that your account record should describe your real circumstances, and where those sit relative to the notice is not something you can edit your way around. Fixed-time options are also high-risk, short-horizon speculation in which capital can be lost in full and quickly, so the account you are securing deserves only money you can afford to lose.

Not locking yourself out

Almost every credential lockout traces back to the same handful of mistakes.

• Changing the email to a mailbox you have not tested. Send yourself a message first.
• Wiping the phone that holds your authenticator before enrolling the new one.
• Changing several things at once, so a failed confirmation tells you nothing about which edit broke it.
• Doing it all while travelling, on an unfamiliar network and a phone that may not receive texts.

Change one thing, prove it works by signing out and back in, then change the next. If a change stalls, the official support route reached from your signed-in account or from the operator's own site is the only path worth taking. No intermediary and no unblocking service can recover an account, and every one of them will ask for the credentials nobody legitimate needs.

Extra prompts and short holds are the system protecting you: change one detail at a time, verify it, and never let urgency rush you into sharing a code.