United States +1 when foreign MSISDNs fail risk checks — for banks, KYC, and apps that expect lasting US identity on the account across re-logins and renewals.
This hub answers location policy. Banks, wallets, and marketplaces that only enroll +1 subscribers need the account to read as United States-based to their risk engine — including later password resets and device checks.
Choose it when “must be a US number” is a standing product rule: domestic KYC, compliance gates, region-locked wallets, or any profile you reopen under the same American country constraint. The goal is kept US presence for the account story.
Prefer staying inside +1 pools before hopping to another country; many US-centric risk graphs treat a sudden foreign MSISDN as a spike. For a named app inside the United States, open that app×USA combo page for scoped copy.
Line-type “VoIP not allowed” errors belong on the non-VoIP hub. Pure one-off capture windows belong on /temp-number-usa/. This page stays on geography-locked, long-lived account use.
Billing note: metered OTP capture (often from $0.02), wallet timeouts credit back automatically — reserve a line, enter it on the app, read the code in console. Catalog spans 2,200+ apps across 200+ countries where stock exists. Avoid public SMS inboxes; they recycle numbers across strangers.
No consumer contract — you still reserve a verification route. The use case is kept US geography for the account (re-logins, KYC, region policy), not owning a lifelong DID.
Anything that hard-requires a domestic +1 for enrollment or later risk checks: US-only wallets, banks, and apps that reject foreign country codes as policy.
Geography-locked products often fingerprint the country of the MSISDN before the code arrives. Matching +1 first avoids false rejects that look like delivery failures.
When you need one short capture window and will not reopen the profile under a United States identity rule. Geography-locked accounts stay here.