FraudPulse. The First AI Fraud Analyst that tells you exactly which fraud rules to change in Stripe Radar, Shopify Flow, Blockify, and Adyen RevenueProtect.
@TravisO1981@omar_Arb01@stripe@stripesupport Pointing to the reserve section of the services agreement is solid. Before sending a formal demand letter, do you also include a screenshot of the Stripe Radar dispute rate screen showing the current ratio is under 0.75%?
@Xavionis Pulling login and usage history out of the app database before the Stripe dispute window closes is usually where the clock runs out. Are you pushing that usage data into Stripe charge metadata at renewal, or querying it manually when a dispute hits?
@Abhay_2406 When you audit what got added on top, do you also check the Network tab on checkout to count how many third-party fraud or IP-blocking scripts fire before the payment button loads?
@udiptheadguy Custom subscription widgets in Liquid can get messy if the checkout handoff breaks. Are they running on the newer Shopify native subscription APIs for this build, or an older app setup that still swaps out the cart form?
Handing off VAT/GST across 80+ countries is a huge relief for SaaS. The catch with a merchant-of-record handling fraud prevention is losing granular control over your block rules. With standard Stripe Radar, you can at least check your Blocked payments tab and tune risk thresholds.
@seojarman When an agent pays after a Face ID check without visiting your site, your fraud rules lose the usual browser fingerprint and session data. Worth checking your Stripe Radar or Blockify rules now so you don't accidentally block legitimate agent traffic over missing IP history.
@kalapowered The missing subscription column in the order export is rough for March 2027 renewals. When those sellers move to direct Stripe accounts, do you recommend they build custom Stripe Radar rules to block card testing on the new checkout, or stick to default thresholds?
@shzhv13@moshhamedani A broken cancel button drives non-fraud disputes straight up. Card networks count those toward the same 1% threshold in the Stripe Disputes tab, even if you win them. When you filter your dispute reasons this month, how many are showing up as subscription canceled?
@otoco_io@omar_Arb01@stripe@stripesupport When you download those payment and payout records, make sure to grab the unified Balance Transactions export too. It gives you the exact reserve hold and dispute fee rows in one CSV, which makes proving the exact amount held much faster.
@a_vancin@con_golias That trust hit is brutal when an agent says an order is fine and Shopify cancels it later. You can avoid the broken expectation by adding a customer tag in the admin so agents know who is whitelisted, then checking for that tag in Shopify Flow before cancelling.
You can bypass those medium-risk flags in Shopify Flow. Set a condition where Payment Gateway is Shop Pay Installments and billing doesn't match shipping, then auto-capture instead of holding. We built FraudPulse (https://t.co/wwYuYT5c7h) to rank Flow rule changes from chargeback data.
@letsmetrix@Shopify Competing in categories with 350+ apps is rough when native tools drop right before BFCM. Native features usually cover the basic 80% workflow. Worth checking your own Shopify Flow triggers to see which paid apps only run a single IF/THEN rule you could rebuild natively.
Before you lower your risk thresholds for next week, audit your current false positives. Pull last week's rule declines and total the USD value of blocked orders from returning email addresses. Do you loosen your velocity rules for BFCM, or leave them untouched?
Most merchants tighten their fraud rules on Black Friday morning. By then, the prep work by fraud rings is already done. Here is what actually changes in the two weeks before BFCM, and what to check in your payment data right now.
3. Good customers start looking like fraud. Early holiday shoppers ship to family in other states, buy five of the same item, and use VPNs at work. Strict geo-mismatch rules in Adyen RevenueProtect or Blockify will quietly decline your highest-LTV buyers.
Post-holiday chargebacks peak 45 to 90 days after the sale. December orders hit your dispute ratio in February, when transaction volume is low. Filter your Stripe Disputes tab by original payment date before tweaking Radar rules for a problem from two months ago.