Set up baseline fraud protection for my payment flow. I use a payment provider (Stripe if that is what my code shows) and have no fraud tooling configured beyond defaults. 1. Provider rules: review my provider's fraud tooling (Stripe Radar) and configure sensible starting rules: block payments where the CVC check fails, block where the billing postal code check fails, and review or block payments the provider scores as highest risk. Tune to block, not just flag, for the clear failures. 2. Card testing defense: card testers hit checkouts with small transactions to validate stolen card lists. Add rate limiting on payment attempts per account and per IP, and make sure repeated failed attempts back off or lock temporarily. Confirm my checkout requires authentication before payment where my product allows it. 3. Velocity signals: log and alert on fraud-shaped patterns: many failed payments from one IP, many cards tried on one account, or signups immediately followed by a large purchase from a disposable email domain. 4. Dispute readiness: make sure every transaction stores the evidence I would need to fight a chargeback: customer email, IP at purchase time, terms acceptance, and delivery/usage records where applicable. 5. Test it: use the provider's test cards for fraud scenarios (declined CVC, blocked card, elevated risk) and verify each is handled with a clear customer-facing error, not a crash. Do not set rules so aggressive that legitimate customers get declined; explain the false-positive tradeoff of each rule you block on. Do not store raw card numbers anywhere, ever. Give me: the provider rules configured, the app-level rate limits added, the fraud signals now logged, and the test card results per scenario.