Demo with sample data. Everything below is made up for a fictional shop, Northwind Candles. Nothing here connects to Stripe.
See FendPulse in action
This is how FendPulse looks inside the Stripe Dashboard. Pick a view.
FendPulse · Northwind CandlesSample data
Status: needs review. 1 Critical and 2 High alerts are open.
Status Light: green means no open High or Critical alerts, amber means an open Medium alert, red means an open High or Critical alert. It shows what FendPulse checks found, never a guarantee.
Last 7 days
1Critical
2High
0Medium
0Info
Latest alerts
Critical
What happened
A payout bank account was added on a connected account.
Why it matters
If someone else added it, future payouts could go to their bank. Next step: confirm the change with the account owner in Stripe.
Confidence
High
In the app, "Review in Stripe" opens the exact Dashboard page for this alert.
High
What happened
Possible card testing: 16 declines in 5 minutes.
Why it matters
Many small declined payments in a short time often mean someone is testing stolen cards. Next step: add a Radar rule or a CAPTCHA to your checkout.
Confidence
High
In the app, "Review in Stripe" opens the exact Dashboard page for this alert.
High
What happened
A webhook endpoint was changed to a new host.
Why it matters
A changed endpoint can send your payment events somewhere you don't control. Next step: check the endpoint URL in Workbench.
Confidence
High
In the app, "Review in Stripe" opens the exact Dashboard page for this alert.
Security Score
67 / 100
Charges are enabledPass
Payouts are enabledPass
Webhook endpoints look safeCheck
Dispute rate is under 0.5%Pass
Refund rate is under 5%Pass
Declines are under 20%Check
Six checks over the last 30 days. Each check links to the Stripe Dashboard page where you can review it.
FendPulse reduces risk; it does not guarantee protection.