Appearance
Security & 2FA
Users protect their account with a password and two-factor authentication (2FA), see and sign out their devices, connect Google, Telegram or Apple, and set an anti-phishing code. Withdrawals have extra checks on top. This page explains what users see, and what support can do when someone is locked out.
The security overview
The account page (/user/profile) shows a Security card with a level, Low, Medium or High, based on three checks:
| Check | Done when |
|---|---|
| Two-Factor Authentication (2FA) | 2FA is on |
| Identity Verification (KYC) | The user's identity is verified |
| Login Password | Always done |
Each check has an Enable or Manage button. Below it are Devices and the account email.
Where users manage security
| Website | Mobile app |
|---|---|
Account (/user/profile/…): Email, Phone, Password, 2FA, Passkeys, Devices, Connected accounts, Anti-phishing code, Delete Account | Account → Security: the same settings, natively (no browser) |
Both use the same server rules (api/v1/account/*). API keys made under API Management can't change any of these settings; only the app and the website can.
Email address
The user types the new address and confirms with their password (and 2FA code when 2FA is on). A 6-digit code goes to the new address; the email only changes once that code is entered (30 minutes, 5 tries). The old address then gets a notice, so a hijacked account doesn't go unnoticed. Accounts made with a phone number add their first email the same way (the phone gets the notice by SMS).
Phone number
Phone (website) / Security → Phone number (app): add or change the number (password + 2FA code, then the SMS code sent to the new number), or remove it. A number can be removed only when the account has a verified email, so it always keeps a way to sign in and recover. See Phone registration for the SMS setup.
Password
The user enters the current password and the new one twice (at least 8 characters), plus a 2FA code when 2FA is on. Changing the password signs out every other device: website sessions and app sign-ins. A notice email is sent.
Forgot password on the sign-in page works with a 6-digit email code (Sign-up).
Two-factor authentication
Website 2FA page or app Security → Two-factor authentication:
- The user confirms with their password.
- A QR code and a setup key appear. The user adds them to an authenticator app (Google Authenticator, Authy, 1Password and so on).
- The user enters the 6-digit code from the app. Only then is 2FA turned on. Closing the page before this leaves 2FA off, so nobody locks themselves out with a QR code they never scanned.
- 8 recovery codes are shown. Each works once instead of a 2FA code (sign-in, security changes). Users can show them again or get new ones later (password + 2FA code).
Turning 2FA off needs the password and a 2FA code (or a recovery code). The user gets a notice email when 2FA is turned on or off.
SMS verification
Users with a verified phone can use SMS codes as the second step instead of (or as well as) the authenticator app: Phone → SMS verification → Turn on (password, then the code sent by SMS). It works everywhere a 2FA code is asked: sign-in, withdrawals, P2P release and security changes have a Send code by SMS link, and when SMS is the only method the sign-in code is sent automatically. Recovery codes are created if the user had none. The authenticator app is the safer option (SMS can be intercepted or the number taken over at the carrier), so the pages recommend it; SMS is offered for users without one. Turning SMS verification off needs the password and a code.
Where 2FA is checked
| Action | 2FA code needed |
|---|---|
| Sign in with email or phone and password (website, app) | Yes: authenticator or SMS code (a recovery code also works) |
| Crypto withdrawal | Yes, in the 2FA Code field (authenticator or SMS code; not a recovery code) |
| Sign in with Google, Telegram or Apple | Yes, after the provider step |
| Sign in with a passkey | No: the passkey already is two factors (the device plus the fingerprint, face or PIN that unlocks it) |
| Change email or password, anti-phishing code, recovery codes, turn 2FA off, close account | Yes |
Lost authenticator
The user signs in with one of their recovery codes, then turns 2FA off and on again with the new phone. If they have no recovery codes left:
- Verify that the person really owns the account (for example: KYC documents, recent deposits, the email address).
- In Admin → Users, open the account and click Disable 2FA.
- Ask the user to sign in and turn 2FA on again with their new phone.
Verify before you reset
Resetting 2FA is a favourite trick of account thieves. Never reset it only because someone asks in chat. Agree a verification routine with your support team.
Passkeys
A passkey lets users sign in with their fingerprint, face or screen lock instead of typing a password. It is stored by the phone or computer (or a password manager such as iCloud Keychain or Google Password Manager) and only works on your domain, so a fake site can't phish it.
Adding one (website Passkeys, app Security → Passkeys): the user confirms with their password (and 2FA code when 2FA is on), then the browser or phone asks for the fingerprint, face or screen lock. Up to 10 passkeys per account. The user can rename them and sees when each was added and last used. A notice email (SMS for phone-only accounts) and a push are sent when a passkey is added, and an email when one is removed.
Signing in: Sign in with a passkey on the login page (website and app). The device offers the passkeys it has for your site; no email or password is typed. No 2FA code is asked, because a passkey already needs both the device and the fingerprint, face or PIN. Blocked accounts are refused. A sign-in alert is sent as for any new device (Sign-in alerts).
Removing one needs the password (and 2FA code). The password always keeps working, so a lost phone never locks anyone out. Closing an account deletes its passkeys.
Requirements
Passkeys need your own domain on https. With an IP address in APP_URL they are switched off (browsers never allow passkeys on an IP), and the button is hidden. Set PASSKEYS_RP_ID to your domain (Environment variables). For the mobile app, also publish your app's IDs: see Build & publish. Full setup: Passkey sign-in.
Keep the domain
Passkeys belong to the domain they were made on (PASSKEYS_RP_ID). If you move the exchange to another domain, existing passkeys stop working and users sign in with their password and add a new one.
Devices
Devices lists where the account is signed in: website sessions (browser, system, IP address, last activity) and app sign-ins (device name, last use), with This device marked. Users can sign out a single device, or sign out all other devices with their password. API keys are not listed (they are managed under API Management).
Session list needs the database driver
Website sessions can only be listed when SESSION_DRIVER=database. With redis, only app sign-ins are listed.
Connected accounts
Users can connect Google, Telegram and Apple to an existing account (website Connected accounts, app Security → Connected accounts): they confirm with their password, then sign in to the provider once. After that, the provider's button signs them in to this account, even if the provider's email differs from the account email. A provider account can be connected to only one user. Disconnect removes it; email and password keep working.
Telegram shares no email address, so a new Telegram user first adds an email or a phone number and confirms it with a code (Sign-up). If it matches an existing account, Telegram is connected to it.
Anti-phishing code
Users can pick a code (4 to 20 letters, numbers, - or _; password and 2FA code to change it). It is printed at the top of every email the platform sends them, so an email without it is not from you. The code is shown masked in the settings (Fa•••••••).
Withdrawal protection
Website: account → Withdrawal protection (/user/profile/withdrawal_security). App: Security → Withdrawal protection.
Security hold
After a password change, email change, phone change or removal, turning 2FA or SMS verification off, or a password reset, withdrawals pause for 24 hours (setting). During the hold:
- crypto and fiat withdrawals are refused with the end time ("withdrawals are paused until …");
- new P2P sales are refused: posting a sell ad, or selling to a buy ad. Orders already running can still be released, so buyers who paid aren't stuck;
- trading, deposits, transfers and buying keep working.
The withdraw page and the protection page show a banner with the end time. Another change during the hold extends it. Only an admin can lift it early (Users → Edit).
Address book and whitelist
Users save withdrawal addresses with a coin, a network (or any network), an optional memo and a label. Saving needs the password and 2FA code, checks the address format like a withdrawal does (and refuses the user's own deposit address), and emails a notice. Saved addresses appear as one-tap chips under the address field on the withdraw page (website and app); Save to address book in the app saves the typed address.
With the whitelist on, crypto withdrawals go only to saved addresses; any other address is refused. Turning it on is immediate. Turning it off takes 24 hours: the user gets an email and a push, and can press Keep it on until then. So someone who gets into the account can't switch it off and withdraw at once. Up to 200 addresses per account.
Sign-in alerts
Every sign-in is compared with the devices the account used before (listed as Recognised devices). A sign-in from a new device sends an email (or SMS for accounts without an email) and a push to the user's other devices: "Your account was signed in from Chrome · Windows (IP …) at … (UTC). If this was not you, change your password now and sign out all other devices."
- Website: a device = browser + operating system + device type. A new IP alone doesn't alert (home and mobile IPs change all the time).
- App: a device = the app's device name + the network (first two parts of the IP).
- Brand-new accounts (first 10 minutes) don't get an alert for their first device.
- Devices that were signed in when this feature was installed are already known, so nobody gets a false alarm on the first day.
Closing an account
Website Delete Account or app Security → Close account (password, 2FA code, a tick that the user understands). Closing is refused until nothing is left open:
- open spot or margin orders, futures positions, margin loans, crypto loans;
- withdrawals still being processed, unfinished P2P orders, open P2P ads;
- active staking, copy trading;
- any balance worth $1 or more (smaller dust is fine);
- staff accounts (any admin role).
The app lists exactly what is left. When the account is closed, every session, app sign-in and API key is removed, connected sign-ins, passkeys and 2FA are cleared, the email address is freed (it can be used for a new account) and a last notice is emailed. Balances and history stay in your reports.
How withdrawals are protected
| Protection | Where it's set |
|---|---|
| 2FA code on every crypto withdrawal (when 2FA is on) | The user's own 2FA |
| Security hold: no withdrawals or P2P sales for 24 hours after a password, email, phone or 2FA change | General settings |
| Address whitelist (only saved addresses; turning it off takes 24 hours) | The user, under Withdrawal protection |
| Sign-in alerts for new devices | Always on |
| API keys can withdraw only from listed IPs | The user, under API Management |
| Admin review before funds leave | Always, unless ENABLE_AUTO_WITHDRAWALS=true (Approvals) |
| 24h withdrawal limit in USD, lower for unverified users | General settings |
| Minimum and maximum per withdrawal | Currencies |
| Pause per network or currency | Networks, Currencies |
| Emergency stop for everything | Maintenance mode |
Good advice for your users
Publish these on your Support or FAQ page:
- Turn on 2FA, and never share the code with anyone, including "support".
- Bookmark the site's address. Check it before signing in.
- Staff will never ask for your password or 2FA code.
