Appearance
Sign-up & social login
Visitors create an account with their email or their phone number and a password, or in one click with Google, Telegram or Apple. You choose which options appear and whether a referral code is required.
Email registration
Page: Sign up (/register).
| Field | Rules |
|---|---|
| Required, must be unique | |
| Password and Confirm Password | At least 8 characters |
| Referral ID (optional) | A referral code. Filled in automatically when the visitor arrives through a referral link. Required when you turn on referral required (below). |
| Terms | Signing up means accepting your Terms of Service and Privacy Policy (links to those pages) |
| Security check | Cloudflare Turnstile, shown when the captcha is on |
Sign-up has three steps: the user enters their email (and referral code), types the 6-digit code emailed to them, then sets a password. The account is created only after the code is confirmed, already verified. Codes expire after 30 minutes, work once, and 5 wrong tries cancel the code. Resend sends a new one.
Older accounts that never verified their email confirm it on Verify your email with a code the same way. Until they do, account pages ask them to verify first. The mobile app uses the same steps.
Phone registration
On Sign up the visitor can switch from Email to Phone. The steps are the same, with an SMS code: phone number (with country code, for example +44 7700 900123) → the 6-digit code sent by SMS → password. The account is created with the phone verified and no email; the user can add one later under Security.
- One account per phone number. Numbers are stored in international form (
+447700900123); spaces, dashes and a leading00are accepted when typing. - SMS codes expire after 10 minutes and work once. A number can get one code a minute and 5 an hour; the sign-up and reset routes are also limited per IP address.
- A verified phone counts like a verified email for everything that needs a verified account (trading, withdrawals and so on).
- Accounts without an email get no emails. Notifications go to the app (push) and important security notices (password changed, email added, account closed…) go by SMS.
Setting up SMS (Twilio)
SMS codes are sent with Twilio: a Verify service for the codes (recommended) and a phone number or sender ID for security notices. The full step-by-step setup, country rules, testing and error codes are in SMS with Twilio.
SMS_DRIVER=log writes the codes to storage/logs/laravel-YYYY-MM-DD.log instead of sending them. Use it only for local testing. While SMS isn't set up, the Phone options show "SMS is not available".
The very first account on a new installation is verified automatically and becomes the superadmin. See First admin account.
New-user notifications
To get an email for every new registration, set the admin email and turn on New user registered in Notifications.
Check the sign-up promise
The sign-up page shows "Enjoy ZERO fees on spot trading and welcome rewards". Change it in Languages if your fees aren't zero or you don't give welcome rewards.
Sign in with other accounts
The buttons appear under the form on both the sign-in and sign-up pages:
| Button | Shown when | Setup guide |
|---|---|---|
Always on the website; in the app when GOOGLE_CLIENT_ID is set | Google sign-in: Cloud project, consent screen, OAuth client, redirect URI https://yourdomain.com/login/google/callback | |
| Telegram | TELEGRAM_BOT_TOKEN is set (and TELEGRAM_AUTH_ENABLED isn't false) | Telegram sign-in: bot from @BotFather, /setdomain |
| Apple | APPLE_AUTH_ENABLED=true | Apple sign-in: App ID, Services ID, return URL https://yourdomain.com/auth/apple/callback, .p8 key, private email relay |
The Google button is always visible
If you don't use Google sign-in, fill in the keys anyway or remove the button from the templates. Otherwise visitors who click it see "Google authentication failed."
After changing .env, run php artisan config:clear.
How accounts are matched
| Provider | Existing account | New account |
|---|---|---|
| Google, Apple | The account that connected this Google / Apple account, else the account with the same email | Created with that email, already verified |
| Telegram | The account that connected this Telegram account (Telegram shares no email) | The user must add an email or phone first (below) |
Every account has an email or a phone number. When the provider shares no email (Telegram always, Apple when the user hides it, Google rarely) and no account matches, the user lands on Complete sign-up (/signup/complete/…, in the app a native screen). They enter an email or a phone number, accept the terms, optionally add a referral code, and confirm with a 6-digit code sent by email or SMS. Then:
- if that email or phone already belongs to an account, the provider is connected to that account (the code proves ownership; the account's 2FA still applies);
- otherwise a new account is created with the email or phone already verified and the provider connected.
The page is valid for 15 minutes and only in the browser that started it.
2FA and blocked accounts
Google, Telegram and Apple sign-in follow the same rules as email and password:
- If the user has 2FA on, they are sent to the two-factor challenge page and must enter the code (or a recovery code) before they are signed in.
- Accounts an admin has blocked or deleted are refused with "Your account is blocked. Please contact support."
Requiring a referral code
Turn on Referral code required in General settings to make the exchange invite-only:
- The Referral ID field becomes required, and an invalid code shows Valid Referral Code is required.
- New users can't sign up with Google or Apple without a code. Existing users can still sign in that way.
Referral links look like https://yourdomain.com/register?referral=CODE. Users find their code and link in their account. See Referrals.
Signing in
Page: Log in (/login). Email or Phone (verified numbers only) and password, then the second step if the user has one (authenticator code, SMS code or a recovery code). Forgot password sends a 6-digit code by email or, for a phone, by SMS; after entering it the user sets a new password (codes expire after 15 minutes). Resetting the password signs the account out of the mobile app. See Security & 2FA.
The reset step never tells anyone whether an account exists: for any email or phone number the page says If an account exists for …, we sent it a 6-digit code, and the answer is the same for real and unknown addresses (also when a code is requested again within a minute). The old reset-link route of the login package is switched off.
Accounts that an admin has blocked can't sign in with any method (email and password, Google, Telegram or Apple) and can't place orders (Users).
