The Real-SIM Number That Unlocks Your Substack Payouts
To accept paid subscriptions, Substack requires you to complete Stripe's KYC — and Stripe rejects VoIP numbers. A dedicated JoltSMS real-SIM number clears the payout wall and keeps your personal number out of Stripe's records after the February 2026 data breach exposed 663,000 creator accounts.
- Real carrier SIM that passes Stripe's phone carrier check — the exact validation that rejects Google Voice, TextNow, and VoIP ranges
- Your number appears on Stripe invoices sent to subscribers; a dedicated JoltSMS number keeps your personal mobile off every receipt
- Keep the number long-term for Stripe re-verification, account recovery, and Substack 2FA — a disposable number means losing your payout access permanently
- Share the inbox with a co-author, VA, or agency team so verification codes never get stuck on one person's phone
Why Substack's payout verification rejects virtual numbers
Substack requires Stripe's Connect identity verification to unlock paid subscriptions. Stripe checks carrier type, blocks VoIP numbers silently or with confusing errors, and exposes your phone number on subscriber invoices.
- •Stripe KYC phone carrier check (hard block): When you activate paid subscriptions on Substack, Stripe checks your phone number's carrier type. VoIP lines, virtual numbers, and most prepaid MVNOs fail — Stripe shows "Unable to verify your identity" or "Please provide a valid mobile phone number" and pauses your payout capability.
- •Substack 2FA SMS (soft block): Substack's SMS-based two-factor authentication uses carrier-type filtering. VoIP numbers are silently rejected: no code arrives, no explicit error is shown — creators don't know whether to retry, try a different number, or wait.
- •Personal number on Stripe receipts: Substack's own support documentation warns that the phone number entered during Stripe onboarding may appear on subscriber receipts and invoices. There is currently no first-party solution that passes KYC and keeps your personal number off subscriber invoices simultaneously.
- •February 2026 data breach SIM swap exposure: Substack confirmed that a breach exposed 663,121 user records including phone numbers. Security researchers noted that phone numbers tied to Stripe accounts are high-value SIM swap targets — a successful SIM swap gives an attacker full control over two-factor codes and payout authorization.
JoltSMS provides real-SIM numbers for legitimate account verification and privacy protection. Using numbers to evade Stripe's KYC obligations, impersonate identity, or violate Substack's Terms of Service is prohibited.
How JoltSMS solves Substack's specific verification checks
JoltSMS numbers are registered to physical SIM cards on US carrier networks — the same classification as your personal cell phone — so Stripe's KYC clears without the 'invalid phone number' block.
- Passes Stripe's carrier lookup to unlock payouts: JoltSMS numbers appear in carrier databases as standard mobile lines, so Stripe's KYC clears without the "invalid phone number" block
- Dedicated number keeps your personal mobile off Stripe invoices: A dedicated JoltSMS number gives subscribers a real, working support number that is not your personal mobile — and is not in the breach dataset
- Long-term rental survives Stripe re-verification cycles: Stripe re-checks identity when you change your payout bank account, cross new revenue thresholds, or trigger a risk review — keep your number month-to-month and every future request lands in the same inbox
- Shared inbox for co-authors, VAs, and newsletter agencies: Route Substack verification SMS and Stripe security codes to a shared dashboard, Slack, or email so no personal phone is ever needed
Who uses JoltSMS for Substack verification?
Blocked monetizers
New paid creators who have set up their subscription tiers but hit the Stripe KYC phone wall before receiving their first payout. A real-SIM number clears the block without exposing their personal mobile.
Post-breach migrators
Existing creators whose phone numbers were exposed in the February 2026 breach who want to move their Stripe 2FA and Substack account off their personal number before a SIM swap attempt.
Pseudonymous and privacy-first writers
Independent journalists, researchers, and creators writing under a pen name who need a business phone number that is not traceable to their personal identity via Stripe's public invoice records.
Newsletter agencies
Marketing agencies and ghostwriting firms managing multiple client Substack publications who need a separate verified phone number per client account without using personal phones.
How to verify your Substack payout account with JoltSMS
Sign up at JoltSMS
Get your dedicated US number — it arrives instantly, no waiting period
Start Stripe Connect onboarding
In Substack, go to Settings → Payments → Set up paid subscriptions and begin the Stripe Connect onboarding flow
Enter your JoltSMS number
When Stripe's identity verification asks for your phone number, enter your JoltSMS number and select United States (+1)
Receive the code instantly
Stripe sends a 6-digit verification code — it appears in your JoltSMS dashboard within seconds
Complete Stripe verification
Enter the code in Stripe's "Verify your phone number" field to complete identity verification and unlock payouts
Set up invoice privacy and 2FA
In Stripe's Public details, set your JoltSMS number as the "Support phone" so it appears on subscriber invoices. Then in Substack Settings → Security → Two-factor authentication, select Text message and enter your JoltSMS number
Keep your number active
Stripe may request re-verification when you change your bank account or hit new payout milestones — you will need the same number to clear those checks
Managing Substack accounts as a team
When multiple people co-manage a newsletter — or when an agency handles Substack for multiple clients — verification codes locked to a single person's phone create access bottlenecks. JoltSMS routes every Stripe and Substack verification SMS to whoever needs it, without anyone sharing a personal number.
- Agency client management: Each client Substack publication gets its own JoltSMS number. Stripe KYC, payout confirmations, and security codes are routed to the client's dedicated inbox — not to an agency employee's personal phone that creates liability if they leave
- Co-author access: Both co-authors get dashboard access to the shared number. When Stripe sends a periodic security check, either person can respond — no late-night texts asking "did you get a code?"
- VA-assisted newsletters: Route Stripe verification and Substack 2FA codes to Slack, Discord, Telegram, or email so your VA can handle Substack admin tasks without needing access to the owner's personal phone
What to know before you get started
Not affiliated with Substack or Stripe. JoltSMS provides real-SIM numbers for legitimate verification and privacy protection. Stripe's acceptance decisions are theirs to make.
Best practices:
- Keep your JoltSMS number active for the lifetime of your Substack publication — Stripe re-verification can trigger months after initial setup
- Set up Slack or email notifications so your team never misses a Stripe security code even when the newsletter owner is unavailable
- Use a separate JoltSMS number per client account if you manage multiple publications — Stripe treats accounts that share a phone number as potentially linked
- After setting up, also add an authenticator app as a backup 2FA method on Substack so you have a non-SMS fallback if needed
- JoltSMS numbers receive inbound SMS only — they cannot make calls, so they cannot be used for Stripe's voice verification fallback if Stripe triggers it
- Also works for the underlying Stripe KYC — see our Stripe verification guide
Substack verification FAQ
Four concrete differences matter for Substack creators specifically. First, dedicated vs. shared: disposable numbers are cycled through hundreds of users — Stripe's carrier intelligence sees a number associated with dozens of recent account signups and flags it. Your JoltSMS number is exclusively yours for its entire rental period. Second, re-verification value: Stripe re-verifies Substack Connect accounts when you change your payout bank, exceed new revenue thresholds, or trigger a risk review. A $2 number is gone within hours, so the second time Stripe requests a code, your payouts freeze again. Third, invoice visibility: your JoltSMS number can serve as the "support phone" on every subscriber receipt — a $2 disposable number will be dead when your subscriber tries to call it. Fourth, breach protection: the February 2026 Substack breach exposed phone numbers for 663,000 creators. A number used across hundreds of other accounts and then recycled is substantially less safe than a dedicated number tied only to your Substack identity. The $50/month is cheaper than losing a month of subscriber revenue while fighting to re-verify a Stripe account.
Get your Substack verification code now
Stop letting Stripe's KYC block your subscriber revenue. Get a dedicated real-SIM number that passes carrier verification — $50/month, cancel any time.