Require 2FA for New SaaS Sub-Accounts in Sparkforge
Sparkforge can require SMS-based 2FA before any new SaaS sub-account purchases its first phone number. Each verifying phone is locked from re-use for 7 days, killing the disposable-number fraud loop.
2-factor authentication on first phone-number purchase is one of the cheapest ways to stop SaaS abuse. Scammers using VoIP numbers and burner email addresses fail the SMS verification step and never reach the point of sending traffic on your account.
Use case
Protect SaaS agencies from the common pattern: a fraudster opens a sub-account with a disposable email, tops up the wallet on a stolen card, then tries to buy phone numbers and blast SMS or robocalls.
Turn on 2FA for new sub-accounts
- Go to SaaS Configurator > Advanced Settings > 2-Factor Authentication.
- Enable the toggle.
What the sub-account user sees
- They attempt their first phone-number purchase.
- Sparkforge prompts them to enter an SMS-capable phone number.
- They receive an SMS verification code and enter it.
- Once verified, they can complete the purchase and any future ones.
A given phone number cannot be used to verify another sub-account for 7 days after its initial use. That window kills the typical bot pattern of cycling one number across many fake accounts.
Bypassing the check
- Sub-account admins cannot bypass 2FA. There is no opt-out from inside the sub-account.
- Agency admins can manually verify a sub-account from the Manage Client page if you trust the customer and want to skip the SMS step.
Frequently Asked Questions
Where do I enable 2FA for new sub-accounts?
Can a sub-account user skip the 2FA prompt?
How long is a verifying phone number locked?
Does this affect sub-accounts that already exist?
Was this article helpful?
Thanks for the feedback.