Card verification with a $1 hold
that blocks SaaS signup fraud
Free trial abuse and credit card testing cost SaaS founders real money. A $1 verification hold at signup instantly confirms the card is real and activeβblocking bad actors before they drain your trial infrastructure.
$1
Authorization hold amount
<5s
Verification time
100%
Card activity confirmed
0
Legitimate signups blocked
How $1 card verification blocks SaaS signup fraud
- 1
Signup form submitted
When a user enters their card during signup, MRRescue receives the event via Stripe webhooks.
- 2
$1 hold created
We create a manual-capture PaymentIntent for $1 on the card. This is a pure authorizationβno charge occurs.
- 3
Instant release
If the authorization succeeds, the hold is cancelled immediately. Fraudsters with stolen cards fail here.
- 4
Real user confirmed
The card is marked verified. Free trial abusers and credit card testers are blocked before they consume resources.
Card verification flow
Why card verification protects your Stripe account from day one
Without card verification
- βFraudsters sign up with stolen cards at zero cost
- βYour trial environment runs jobs for bad actors
- βYou spend money on infrastructure for non-customers
- βCredit card testers drain your signup form
- βAbuse patterns pile up until you notice them
With MRRescue card verification
- βStolen cards are caught before the trial loads
- βOnly real, active cards can enter your system
- βInfrastructure spend maps to real potential customers
- βCard testers are blocked at the $1 hold
- βYour Stripe dashboard stays clean and fraud-free
SaaS signup fraud: why card testing costs more than founders realize
Card testing is a fraud technique where bad actors use automated scripts to test stolen card numbers against real payment processors β validating which cards are active before using them for larger fraudulent purchases elsewhere. SaaS free trials are a particularly attractive target because the charge amount is often low (or zero) and the signup process is typically frictionless. The cost to the founder isn't always the direct financial loss from the test charge; it's the downstream impact: chargebacks when stolen-card transactions are disputed, dispute fee accumulation, and Stripe rate threshold risk.
A $1 authorization hold at signup costs almost nothing to implement but creates a significant filter. Stolen cards often have limited authorization headroom, prepaid gift cards used for fraud decline on hold attempts, and disposable virtual card numbers used for one-time signups frequently fail verification. Legitimate customers with valid cards sail through β the hold is released immediately and most never see it on their statement. The filter catches the fraud category that causes the most damage while imposing zero friction on real signups.
Disposable email addresses work as a complementary signal. Legitimate customers use real email addresses β work emails, personal gmail accounts, hosted domain emails. Fraud actors overwhelmingly use disposable domains because they want no paper trail and no follow-up. Blocking signups from known disposable domains (there are thousands, maintained in regularly updated blocklists) catches a large percentage of bot signups, trial abusers, and fraud testers before they ever interact with your product or payment system.
Hardening your signup funnel against fraud
- βCombine $1 hold verification with disposable email blocking β the two signals catch different fraud vectors.
- βDon't add friction to the payment step for standard users; the $1 hold happens invisibly and the release is immediate.
- βMonitor your 'verified vs. unverified' signup split monthly β a spike in unverified signups often signals a bot campaign targeting your trial.
- βFor annual plans, the stakes are higher β a fraudulent annual signup is a larger chargeback risk, making verification even more critical.
Frequently asked questions
Does the $1 hold charge the customer?
No. The $1 is a pure authorization hold β not a charge. It appears as a pending transaction for a few minutes, then vanishes. The customer's bank statement shows zero actual charge.
Will my customer see a $1 charge on their statement?
They may see a temporary $1 pending authorization that disappears within minutes. The hold is cancelled immediately after verification β no actual charge is made.
When does the verification happen?
By default, MRRescue verifies cards when a new trialing subscription is detected. You can also trigger it on-demand via the API for any customer with a payment method on file.
What happens if the card fails verification?
The failure is logged in your dashboard with the decline reason. You can then decide to notify the customer, block the trial, or take no action.
Does this work with all payment methods?
It works with any card-based payment method that supports authorization holds (Visa, Mastercard, Amex, Discover). Digital wallets like Apple Pay and Google Pay are also supported.
Start verifying cards at signup today
Block fraud before it hits your Stripe account. Connect your account in minutes and start protecting your trial from day one.
Related features
Signup Fraud Blocking
$1 authorization hold at signup that instantly confirms cards are real and blocks fraudulent signups.
Learn more βFraud Alerts
Real-time Early Fraud Warning alerts with one-click preventive refund β stop chargebacks before they land.
Learn more βExpiring Card Alerts
Automated reminders 30 days before card expiry β prevent the most preventable form of involuntary churn.
Learn more βBackup Payment Requests
Proactively ask customers to add a backup card before their primary payment method fails.
Learn more βReady to stop losing MRR?
14-day free trial. No credit card until day 15. Connect Stripe in 5 minutes.
Start free diagnosis β14-day trial Β· no credit card Β· cancel anytime