Everything you need to know about Bolt SMS verification codes: why they arrive, why they don't, how travellers get a working local number before a trip, how rider and driver rules differ, and what to do when the resend button isn't enough.
Bolt sends every login code by SMS to the phone number on your account, so the number you register decides whether the app just works or locks you out on a rain-soaked street in a city where you don't speak the language. This guide covers the questions that actually come up: codes that never arrive, foreign numbers that fail abroad, rider versus driver number changes, what driver verification really involves, and that mysterious hold on your card.
Yes. No email-only path exists, and no workaround is hiding in the settings. A Bolt rider account is built around a mobile number, and every session begins with a one-time SMS code sent to it. Email is a secondary field you can add and edit later (it even works while unverified), but it's a contact address, not a login method. Lose access to your number and you lose the easy way into your account. The number you pick at sign-up deserves a moment of actual thought.
Why so strict? Scale, mostly.
50+ countries and 600+ cities — that's Bolt's current footprint, and a verified mobile number gives the platform a lightweight identity layer across all of it: fraud control, cards tied to real people, and a way for drivers to reach passengers at the kerb. The upside for you is that there's no password to remember. You request a code, it lands, you're in. The code itself is a short one-time password, valid for that login attempt only, and Bolt commits to delivering it in under a minute. If you've ever wondered why the app never asks you to create a password at all, this is the reason: the SMS channel effectively is the password, which is also why the quality of the number behind it matters so much.
The markets where this matters break down roughly like this:
In every one of those places, the requirement is identical: a number that can receive SMS at the moment of login. It doesn't have to be your personal SIM. It just has to work where you're standing. Plenty of people keep a separate number for app registrations purely as a privacy practice, and if you're weighing how to do that, our comparison of free vs paid temporary phone numbers covers the options honestly.
Picture the scene. You land in Warsaw, open Bolt, type in your US number, and wait. Nothing. Resend. Still nothing. The taxi queue outside is getting longer and your phone insists it has signal.
This is one of the most commonly reported Bolt frustrations among travellers, and the honest answer to "will my foreign number work?" is: sometimes, but you shouldn't bet an airport pickup on it. Bolt doesn't publish a list of approved or blocked prefixes. What happens in practice is that your code travels through SMS gateways and international carrier routing, and cross-region delivery runs into filtering, delays, or silent blocking that Bolt cannot fully control. A code can leave Bolt's systems instantly and still die somewhere over the Atlantic.
User reports add a second failure mode. When the app rejects a number outright, people describe an error along these lines:
This phone number is not eligible.
According to those third-party reports, the message tends to appear for numbers that are unsupported in the region, already attached to another account, entered with the wrong country prefix, or flagged as previously blocked virtual numbers. Bolt doesn't document any of this officially, so treat it as observed behaviour rather than policy. It's consistent enough to plan around, though.
Android users report one more wrinkle: RCS, the enhanced messaging protocol in Google Messages, can intercept incoming one-time codes so they never surface in the SMS inbox. Disabling RCS and retrying has fixed it in a number of reported cases. Again: user workaround, not official guidance.
Roaming adds its own layer of unpredictability. When your home SIM attaches to a foreign network, inbound SMS gets forwarded across carrier agreements that were engineered around person-to-person texting, not time-sensitive one-time codes. Some codes crawl in minutes late. Others evaporate entirely, with no error on either end. That silence is the worst part: the app believes the message was sent, your phone believes nothing happened, and you're left staring at a countdown timer.
The fix travellers consistently describe as most reliable? Get a number registered in the country you're visiting before you fly, and arrive with verification already behind you.
The playbook is simple: rent a number in your destination country through an SMS verification service, receive the code in a private dashboard, and link your Bolt account to it before you pack.
SMSXR covers Bolt verification in 182 countries, including all of Bolt's primary European and African markets. Pricing is per code. You pay only when a code is actually delivered, a 10-minute automatic refund applies if nothing arrives, and numbers are never resold to another user for the same service. That last point matters more on Bolt than almost anywhere else: a number already attached to another Bolt account is typically rejected during verification, users report, so a recycled number is worse than useless here.
Current per-country pricing across Bolt's core markets (as of July 2026):
| Country | Bolt Presence | SMSXR Price |
|---|---|---|
| United Kingdom | Major market | $0.30 |
| Colombia | Active market | $0.40 |
| Chile | Active market | $0.40 |
| Philippines | Active market | $0.50 |
| Spain | Major market | $0.50 |
| Germany | Major market | $0.50 |
| United States | Toronto + expansion | $0.60 |
| Netherlands | Active market | $0.60 |
| France | Active market | $0.90 |
A UK number at $0.30 is the cheapest entry into a major Bolt market. Spain and Germany sit at $0.50, France at $0.90. All under a dollar. Across the full catalogue, Bolt-capable numbers currently range from $0.30 up to $77.10 depending on country, so check your actual destination rather than assuming a flat rate.
Which country should you pick? Match the number to the market you'll ride in. Landing in Lisbon means a Portuguese or Spanish number keeps you inside the regional routing that users report as dependable. If your itinerary spans several countries, pick the one where you'll first need a ride; once verified, the app itself runs on any connection, because the SMS dependency only bites at login.
Step by step:
One honest caveat. Bolt sends a fresh code at every login, so think about whether you'll log in again mid-trip. Staying signed in on your phone avoids repeat codes entirely, and if Bolt becomes a long-term part of your life, you can move the account onto your permanent number later through the profile flow described below. Budget for a spare code too: at $0.30 to $0.90 per delivery in Bolt's core markets, a second verification is small change next to a single airport taxi fare.
Sixty seconds. That's Bolt's stated delivery window, and most failed-code frustration comes from people acting before it expires or giving up right after. Bolt's support documentation lays out a clear sequence, and it's best run in order before blaming the number:
Steps one through five take maybe three minutes total. In our experience reading traveller reports, the restart and the RCS toggle resolve a surprising share of the "impossible" cases.
Registered with a travel number and now want your permanent SIM on the account? Switched carriers? The change flow exists and it's quick, but it behaves differently for riders and drivers, and that difference catches people out.
For riders, go to Account → Profile and open the phone number field. Bolt sends the verification code to the new number you enter, not the old one. Type it in and the change applies immediately. From then on, every login code goes to the new number.
That new-number-first design is quietly brilliant for travellers. You don't need the old SIM in hand to move your account onto a fresh number, which is exactly the situation you're in when a foreign number has stopped receiving codes abroad.
A practical tip: if the number you're switching to is one you're renting for the purpose, have the SMSXR dashboard open before you start the change in Bolt. The 60-second window applies here exactly as it does at sign-up, and you want eyes on the inbox when the code lands.
Drivers face the reverse logic. Bolt routes the driver-side confirmation to the old number on the account. No access to the old number means the in-app flow is a dead end, and the correct path becomes contacting Bolt driver support, which runs a manual verification process for precisely this case. Resolution times vary by market. The lesson for drivers: change your number while the old one still works, not after the SIM has been recycled.
Users also report that a number already linked to a different Bolt account gets rejected during the change flow with an eligibility error. One number, one account appears to be the operating rule, even though Bolt never states it outright in official documentation.
Completely different, and it's worth being blunt about why, because a persistent misconception floats around that a clever choice of phone number somehow smooths the path to driving for Bolt.
It doesn't. A temporary number plays no part whatsoever in driver approval.
For riders, verification is minimal: one SMS code plus a payment method. The phone check effectively is the identity check. For drivers, the phone number is the trivial first step in a much longer pipeline. Bolt's official driver onboarding requires:
And the scrutiny doesn't stop at onboarding. Since 2025, Bolt has run ongoing AI-powered selfie checks: periodic prompts requiring drivers to submit a real-time selfie that gets algorithmically matched against the ID document on file. The goal is confirming that the person behind the wheel today is the same person who passed verification originally, which targets account-sharing and account-selling on the driver side.
So here's the honest framing for anyone considering driving for Bolt. The phone verification is the easiest sixty seconds of the entire process. Everything that determines approval happens afterward, on paper and on camera, and your choice of number is irrelevant to all of it. The asymmetry is deliberate: riders present a reachable number and a payment card, while drivers carry passengers for a living, so Bolt verifies the human, the vehicle, and the paperwork behind both.
Bolt Drive, the car-sharing and rental arm, adds yet another tier: a driving licence check and an ID document verified through Veriff (Bolt's third-party identity partner), plus a confirmed payment method. Veriff photographs your physical documents and matches them to a live capture. The pattern across Bolt's higher-stakes products is consistent. SMS verifies the number. Documents and biometrics verify the person.
Short answer: no, and that's good news.
Bolt Food shares the same account as the Bolt ride app. Same login, same phone number, same profile. If you're already a Bolt rider, you open Bolt Food, log in with the same number and code, and everything is waiting for you. No second registration, no second number, no repeat verification.
For a traveller, one verified number therefore unlocks the entire consumer side of the platform: the ride from the airport and the dinner delivered to the apartment an hour later, on a single account. That single sign-on convenience is unusual among ride platforms, and it changes the maths of verifying carefully, because the effort you spend getting one reliable number pays off twice.
Profile details, phone number, and payment methods all propagate automatically in both directions. A card added in Bolt Food becomes available in the ride app; a profile edit made in either app shows up in the other. Bolt Drive sits on the same account too, but layers its own extra verification on top (licence, ID via Veriff, and a payment method) before you can unlock a car.
The flip side is that your login number carries more weight than it first appears. That single number guards your ride history, delivery addresses, and saved cards across every Bolt consumer app. Keep that in mind when we compare number sources below, because a credential this central deserves better than an inbox published on a public webpage.
Add a card to Bolt and a small pending charge may appear on your statement within minutes. Before you reach for the fraud hotline: this is expected, it's reversible, and it's not money leaving your account.
The pending item is an authorisation hold (banks also call it a pre-authorisation). Bolt places it to confirm the card is real, active, and chargeable before you take your first trip. Your bank earmarks the amount temporarily and then releases it.
14 days — the window in which Bolt says the hold is released in the vast majority of cases, stretching to 30 days only rarely, depending on how fast your card issuer processes reversals.
Banks display holds inconsistently, which is where most of the panic comes from. Some show them mixed in with real charges. Others tuck them into a separate pending section. The same hold can look alarming in one banking app and be invisible in another. If a hold lingers past the 14-day window, patience is usually right; past 30 days, raise it with your bank or Bolt support, since every issuer should have cleared the release by then. You don't need to do anything to trigger it.
One more thing this step is not: connected to your phone verification. Adding a card doesn't fire a new SMS code, and receiving a login code never touches your card. The two systems answer different questions ("can this person receive messages at this number?" versus "is this a real, chargeable card?") and run independently. A failed code doesn't mean a card problem, and vice versa.
On Bolt, your number isn't a one-off formality. It's your permanent login credential. That raises the stakes on where the number comes from, so here's the honest comparison:
| Method | How it works | Main l |
|---|
Yes. A Bolt rider account is tied to a mobile number. Every login triggers a one-time SMS code sent to that number. Email is a secondary field and can be added later, but the phone number is the primary login credential.
Official guidance says to wait up to 60 seconds, then use the Resend button. If that fails, check the number is entered correctly, restart your device, and confirm you have signal or data. Users on roaming or RCS-enabled Android phones have reported interception issues, and disabling RCS in Google Messages can help. If none of that works, contact Bolt's local support by email.
Technically you can try, but travellers frequently report that foreign numbers (for example a US number used in Poland) fail to receive the verification code reliably. Getting a local-market number before you travel, such as a UK number at $0.30 or a Spanish one at $0.50, is the approach users report as most reliable.
Riders can update their number in Account > Profile. Bolt sends a verification code to the new number; once you enter it, the change takes effect. Drivers have a different process: the confirmation goes to the old number on file, and if you no longer have access to that number, you need to contact Bolt driver support directly.
No. Rider sign-up requires only a verified phone number and payment method. Driver onboarding requires a driving licence, vehicle registration, proof of insurance, a photo, an ID document, background checks, and ongoing AI-powered selfie checks. A temporary number plays no role in passing those document checks.
No. Bolt Food shares the same account as the Bolt ride app. Your profile, login, and phone number sync automatically across both apps.
When you add a payment card, Bolt places a small reversible authorisation hold to confirm the card is valid. This hold is released inside 14 days in the vast majority of cases, though in rare situations it can take up to 30 days. It is not a charge, and no money leaves your account.
No. Bolt's official safety guidance states that the company never contacts users via WhatsApp from foreign numbers. Any such message should be treated as a scam. Official verification is delivered only by SMS to your registered number.
We test verification flows and price data first-hand, then write it up plainly.
Codes in seconds, automatic refund if none arrives, prices from $0.10. No personal number required.
Get started freeYou can verify your Lyft account without exposing your personal phone number by renting a temporary number from SMSXR. Follow this practical guide to choose the right number, request the code, and keep your privacy intact.
Need a DoorDash verification code but don’t want to share your personal phone number? This guide shows you how to use SMSXR’s temporary numbers safely and quickly.
Get a Gojek verification code without exposing your personal phone. This guide walks you through renting a temporary number from SMSXR, understanding pricing, and avoiding common pitfalls.
