SYSTEM Cited by 2 sources
Stripe Radar¶
Stripe Radar is Stripe's fraud-detection service. Originally a card-fraud system gated to Stripe-processed payments, Radar has expanded along four axes per the 2026-05-27 Sessions disclosure: global payment-method coverage, multiprocessor signal export (predictive signals usable on non-Stripe transactions), custom fraud models (per-tenant ML fusing tenant features with global network features), and agentic-era abuse vectors (multi-account abuse, pay-as-you-go abuse, agentic-commerce bot scoring).
Surface¶
The Radar surface is a fraud-detection control plane consumed by three audiences:
- Direct merchants — fraud blocking on Stripe-processed transactions.
- Multiprocessor merchants — predictive signals on non-Stripe transactions (concepts/multiprocessor-fraud-signal-export). Two signals at the 2026-05-27 disclosure: early-fraud-warning likelihood and fraudulent-dispute likelihood; "we plan to add new signals that can be used across your entire payments stack."
- Platforms — via systems/stripe-radar-for-platforms, exposing 0-to-100 fraud scores per business and per transaction, AI-powered explanations, and account-level metrics. Hosts the new merchant-risk signals (fraudulent website, fraudulent merchant, merchant delinquency risk).
Cross-payment-method propagation¶
As of 2026-05-27, "Radar now protects all supported payment volume globally, including bank debits, buy now, pay later (BNPL) options, crypto, digital wallets, real-time payments, and cash vouchers. When Radar detects a fraudulent pattern on a transaction, that information becomes available to protect transactions across all payment methods."
The architectural shape is the cross-payment-method fraud network — a fraud signal detected on a card transaction (IP address, device fingerprint) becomes a flag against the same actor on bank debits, Affirm, Cash App, Klarna, PayPal, and other methods network-wide.
Disclosed outcome: "Radar reduced suspected fraud by 71% during a five-month period for businesses using Affirm, Cash App, Klarna, and PayPal." Baseline and merchant segment unstated.
This is the network-effect-fraud-detection thesis: each payment method added to Radar's coverage enriches detection on every other method. (Source: sources/2026-05-27-stripe-expanding-stripe-radar-to-protect-more-of-your-business)
Multiprocessor signal export¶
Stripe sells fraud-prediction signals as a B2B API for use on transactions Stripe doesn't process. Two signals at the 2026-05-27 disclosure:
-
Early-fraud-warning likelihood — "Stripe can now identify whether a payment is likely to trigger an early fraud warning from the card network. You can then choose to proactively refund the transaction and protect your dispute rate." Pattern: patterns/preemptive-refund-on-early-fraud-warning.
-
Fraudulent-dispute likelihood — "Stripe can also predict whether a payment is likely to result in a fraudulent dispute. You can use this signal to issue refunds, gather evidence, or adjust your dispute strategy."
The architectural pattern is patterns/multiprocessor-signal-as-api — fraud-detection signal value monetised independent of payment processing, implying the Stripe-network signal density is the actual asset, not just card-acquirer logistics.
Custom fraud models¶
For "businesses with more complex risk profiles", Radar offers custom fraud models per the tenant features + network data pattern:
- Tenants pass "signals unique to your business, such as product catalog data, loyalty status, behavioral metrics, or any structured metadata relevant to your risk profile."
- "Stripe then combines this information with our global network data to deploy a model customized specifically to your business."
Disclosed outcome: "For early adopters, custom models are detecting at least 15% more fraud with no increase in false positives." Model class, training cadence, feature-schema versioning, and per-tenant deployment isolation undisclosed.
Agentic-era abuse vectors¶
Three new fraud-class detections targeting LLM/agentic-commerce era abuse:
Multi-account abuse¶
Multi-account abuse — single fraudulent actor cycling through several accounts to reuse promotional coupons or spread stolen card activity to avoid detection.
- Detection signal mix (named, mechanism not disclosed): "device fingerprints, IP addresses, email domains, and more."
- Population claim: "more than 1 in 6 sign-ups at AI companies are linked to multi-account abuse."
- Production reference: ElevenLabs "has been able to block 2,000 users a day from abusing its free tier."
Pay-as-you-go abuse¶
Pay-as-you-go abuse — customers exploit consumption-billing latency by accumulating thousands in compute over a billing period, then never paying. The novel mechanism is predictive intervention before billing — Radar predicts non-payment as usage accumulates, allowing platforms to require a top-up, throttle, or cut off service before the bill is generated.
Bot scoring on Stripe Checkout¶
Bot score on Stripe Checkout payments, distinguishing legitimate agentic-commerce buyers from malicious bots exploiting checkout for limited-inventory / promotional / purchase-limit abuse.
The hard problem (named in the post): "Both are nonhuman traffic making purchases, but one is a customer's authorized agent, and the other might exploit your checkout to buy limited-availability inventory, abuse promotional pricing, or bypass purchase limits." Disambiguation mechanism undisclosed.
This sibling-clusters with the 2026-03-12 Stripe Radar adaptation: there Radar substitutes Stripe-network density signals for vanished human-behaviour fingerprints on agentic channels (so legitimate agents can buy); here Radar adds a bot-malicious score on the same surface (so illegitimate bots can be filtered out). The two pieces are complementary halves of the same agentic-commerce-fraud architecture.
Agentic-commerce adaptation (2026-03-12)¶
Per the 2026-03-12 Stripe retrospective, traditional fraud detection relies on human-behavioural signals — browser fingerprinting, mouse movements, device battery level, window size — that vanish in agentic channels where no human is on the frontend.
Radar's substitute for agentic traffic is Stripe network density: even if an agentic purchase is new to the merchant, the end customer and their payment method are usually already known to Stripe across other merchants, which "gives an immediate source of history and risk context."
Integration path with SPTs: authorisation for agentic transactions can happen off-Stripe (at the payment-network level), but Radar can still apply scrutiny because SPTs carry enough metadata for Radar to score the transaction "even when authorization happens off-Stripe."
Claimed outcome on Coach / Kate Spade / Ashley Furniture deployments: "fraud rates have been near zero." (No baseline disclosed; unqualified claim.) (Source: sources/2026-03-12-stripe-10-things-we-learned-building-for-the-first-generation-of-agentic-commerce)
Operational numbers¶
- 71% suspected-fraud reduction over five months for businesses using BNPL + wallets alongside cards.
- 15% more fraud detected with no false-positive increase for early-adopter custom-model tenants.
- >1 in 6 AI-company sign-ups linked to multi-account abuse.
- 2,000 users/day blocked at ElevenLabs (free-tier abuse).
Seen in¶
- sources/2026-05-27-stripe-expanding-stripe-radar-to-protect-more-of-your-business — cross-payment-method coverage; multiprocessor signal export; custom fraud models; multi-account abuse + pay-as-you-go abuse
- bot-score-on-checkout primitives; partner platform variants.
- sources/2026-03-12-stripe-10-things-we-learned-building-for-the-first-generation-of-agentic-commerce — Radar's substitution of network-density signals for human-behavioural fingerprinting in agentic channels.
Related¶
- systems/stripe-radar-for-platforms — platform-tier variant with merchant-risk signals.
- systems/stripe-smart-disputes — companion AI-dispute product, separate surface from Radar but co-evolving.
- systems/stripe-checkout — surface for the new bot score.
- systems/stripe-agentic-commerce-suite — Suite uses Radar as its fraud substrate for agentic transactions.
- concepts/shared-payment-token — carries metadata enabling Radar scoring even when authorisation is off-Stripe.
- concepts/multi-account-abuse — abuse class detected via device-fingerprint / IP / email-domain network signals.
- concepts/pay-as-you-go-abuse — abuse class predicted as usage accumulates.
- concepts/agentic-commerce-bot-score — bot-vs-agent classification on checkout.
- concepts/multiprocessor-fraud-signal-export — signal-export to non-Stripe transactions.
- concepts/cross-payment-method-signal-propagation — network-effect signal propagation across payment methods.
- concepts/network-effect-fraud-detection — generalised fraud-detection-as-network thesis.
- patterns/cross-payment-method-fraud-network — Radar's canonical cross-method propagation pattern.
- patterns/tenant-features-plus-network-data-fraud-model — Radar's custom-models pattern.
- patterns/preemptive-refund-on-early-fraud-warning — defensive action pattern enabled by Radar's early-fraud prediction.
- patterns/bot-score-on-checkout — bot-detection pattern at checkout surface.
- patterns/multiprocessor-signal-as-api — signal-export pattern.
- companies/stripe — Radar vendor.