Harden Your Sparkforge SaaS Checkout Against Fraud

SaaS sub-accounts are a target. A few configuration steps cut down fraudulent signups and keep bad actors from racking up usage on your dime.

Step 1: Use v2 funnels and websites

If you're on legacy funnels for SaaS sales, switch to v2. The newer version uses native Stripe integration and 3D Secure, so high-risk cards face the additional auth layer.

Step 2: Add custom authorization on trials

For products with a trial, set a Custom Authorization amount under Funnel → Products → Additional Options → Custom Authorization. Stripe creates a payment intent to confirm the card is real with sufficient balance, then immediately refunds it. The customer is never charged.

Set the authorization to roughly the monthly fee of your most basic plan.

Step 3: Run Sparkforge Phone and Sparkforge Email

External Twilio and Mailgun accounts add latency between usage and rebilling, which gives bad actors a window to spike calls, SMS, and email before sub-account credits debit. Sparkforge Phone and Email close that gap and add:

• Ramped sending limits for SMS, email, and voicemail drops.
• Maximum sending caps per sub-account.
• Error rate, unsubscribe rate, and complaint rate monitoring.
• Email verification and phone error thresholds.

Migration is faster than most agencies expect. Move the agency and sub-accounts to Sparkforge Phone and Email, then enforce the limits.

Step 4: Turn on phone and email verification

Email verification is mandatory by default for SaaS signups. Add phone verification at Agency → SaaS Configurator → Security Settings → Verify Phone Number using a security code during sign-up.

To enforce email verification across existing sub-accounts: Agency → Settings → Email Services → Sub-Account Settings → Enable Email Verification for all sub-accounts.

Step 5: Use Stripe Radar

Stripe Radar is Stripe's fraud detection layer with machine-learning rules trained on global payment data. It costs extra, but it pays for itself fast on a SaaS funnel. Find it under Stripe Dashboard → More → Radar for Fraud Teams.

Rule types worth setting

• 3D Secure rules — force 3DS challenge on risky payments.
• Block rules — reject payments matching specific patterns.
• Review rules — hold payments for human approval before settling.

What to do when fraud still gets through

Refund the payment and mark it Fraudulent (not just refunded). Stripe Radar uses the signal to:

• Add the card fingerprint to your blocklist.
• Add the email to your blocklist.
• Train the model on the IP, email, and card to catch similar attempts.