Categories
Need a custom hosting configuration?
Now it’s easy (and insanely affordable)
to get help from an expert. Whatever you
need, our pros can handle it for you so
you can focus more on what matters …
growing your business.
Platforms
You dream it — we code it. Tap into 10+ years of Blesta, WHMCS & Paymenter development.
WordPress plugins are coming soon
WordPress add-ons are on the roadmap. Tell us what you need.
From custom embedded firmware to cloud
platforms and mobile apps — we design
and build complete IoT solutions
tailored to your needs.
The fraud signals WHMCS can't see on its own. Read Stripe Radar's verdict on every payment, hold risky or unverified orders out of automatic provisioning, run hosted identity checks, and act on disputes and chargebacks — automatically.
WHMCS's antifraud stops at payment. This reads Radar, verifies identities and reacts to disputes, refunds and early fraud warnings on its own.
Each Stripe payment gets a trust report — Radar risk level and score, AVS and CVC checks, 3D Secure result, card fingerprint and issuer country — stored right on the client's profile.
Risky or unverified orders are held out of automatic provisioning — even on instant-accept order forms — until you clear them. Card-fingerprint reuse across clients and country mismatches are flagged too.
Ask for Stripe Identity when you need it — document or ID-number checks with an optional matching selfie. Hold until verified, approve or reject manually. No identity PII is stored in WHMCS.
Services suspend automatically on a dispute, an early fraud warning, or a refund past your threshold — and can un-suspend when a dispute is won. A signed webhook plus an hourly reconcile keep it accurate.
WHMCS's antifraud runs before payment. This works on the post-charge signals it can't see: Stripe Radar's verdict on the completed payment, disputes, chargebacks, early fraud warnings and refunds — the things that only show up after money has moved.
For each Stripe payment: Radar risk level and numeric score, AVS line1/zip and CVC results, the 3D Secure outcome, the card fingerprint and issuer country, the Stripe review id and any Radar rule message, and a pass / hold / cleared decision. It also detects the same card fingerprint used across different client accounts.
It uses WHMCS's native order-review workflow to hold flagged orders. On instant-accept order forms it moves held orders back to Pending status so they wait for your review instead of provisioning automatically.
No. Identity verification runs through Stripe Identity's hosted flow and no identity PII is stored in WHMCS — details are fetched live from Stripe when needed. You can redact them at Stripe on demand or on a schedule (never, after a set number of days, or immediately on verification).
A Stripe dispute, an early fraud warning, or a refund that exceeds a percentage of the charge you configure. Suspensions are recorded in the service history, and you can enable automatic un-suspension when a dispute is won in your favour.
Current WHMCS versions, PHP with cURL, the stock Stripe Payments gateway, and an HTTPS endpoint for the signed webhook. Stripe Identity and Radar for Fraud Teams are optional and unlock the identity checks and richer scoring when enabled on your Stripe account.
United States [$]
United Kingdom [£]
Canada[$]
Greece[€]