Payment Fraud Scoring and Review
Evaluate provider risk signals, review thresholds and fraud outcomes while measuring false positives and delayed labels.
Use this skill to design and evaluate a payment-risk decision process. Define the payment flow, provider, available signals, fraud loss measure and customer-friction limits. A risk score is not proof of fraud and should not be presented as an accusation against a person. ## Key Points - [Stripe Radar risk evaluation](https://docs.stripe.com/radar/transaction-risk-prevention)
skilldb get payment-services-skills/payment-fraud-scoringFull skill: 37 linesPayment Fraud Scoring and Review
Use this skill to design and evaluate a payment-risk decision process. Define the payment flow, provider, available signals, fraud loss measure and customer-friction limits. A risk score is not proof of fraud and should not be presented as an accusation against a person.
Establish data and decisions
Separate provider signals from your decision policy. A provider's score, risk level, authentication result and network response may describe different stages of a transaction. Record their definitions and availability for the exact integration rather than assuming every field exists for every payment.
Inventory legitimate outcomes: approve, request additional authentication, hold for review or decline. Specify who may review or override a decision and what evidence they can access. Minimize sensitive data and protect any payment information under the applicable handling requirements.
Build labels from verified operational outcomes while acknowledging that disputes arrive late and are incomplete measures of fraud. A blocked payment's true outcome may remain unknown. Do not treat every declined payment as a confirmed fraudulent example.
Evaluate a policy
Create chronological evaluation sets that reflect information available at decision time. Do not use the same event's future dispute, refund or manual-review outcome as an original authorization feature. Prevent duplicate customers or transactions from leaking across evaluation boundaries where that would inflate performance.
Report precision, recall where labels support it, false-positive rate, approval rate, loss and review workload. State denominators and label maturity. Evaluate thresholds against the business cost of fraud and the cost of rejecting legitimate customers, not only a model accuracy percentage.
Review performance across relevant customer and transaction segments for unintended disparities. Avoid adding sensitive traits or crude proxies merely because they appear predictive.
Operate and monitor
Start with a shadow evaluation or bounded test where available. Confirm that rules do not contradict provider handling or authentication requirements. Document how unavailable signals and provider outages are treated.
Use a review queue with evidence, reason codes, decision history and an escalation path. Keep explanations understandable without exposing details that would help evade fraud controls. Reconcile duplicate events so one payment does not create repeated holds.
Monitor drift, review backlog and delayed dispute outcomes after changes. Retain the previous policy and a rollback procedure. Deliver a threshold report, decision matrix, evaluation limitations and monitoring plan. Activating a production block rule is a separate authorized change; an offline score analysis does not justify silently declining real customers.
References
Install this skill directly: skilldb add payment-services-skills
Related Skills
Paypal
Accept payments with PayPal. Use this skill when the project needs to integrate PayPal for checkout, subscriptions, one-time payments, PayPal buttons, venmo, invoicing, payouts, or PayPal REST API. Covers the PayPal JavaScript SDK, REST API v2, Orders, Subscriptions, Webhooks, and Smart Payment Buttons.
Razorpay
Accept payments with Razorpay. Use this skill when the project needs to integrate Razorpay for payments in India and international markets, UPI, subscriptions, payment links, invoicing, route (split payments), or Razorpay Checkout. Covers the Razorpay API, Checkout.js, orders, subscriptions, webhooks, and UPI.
Square
Accept payments with Square. Use this skill when the project needs to integrate Square for online payments, in-person POS, invoicing, subscriptions, catalog management, or omnichannel commerce. Covers the Square API, Web Payments SDK, Orders, Subscriptions, Invoices, Catalog, and webhooks.
Stripe
Accept payments and manage subscriptions with Stripe. Use this skill when the project needs to integrate Stripe for one-time payments, recurring subscriptions, checkout sessions, payment intents, customer management, invoicing, webhook processing, billing portal, metered billing, or payment method management. Covers the Stripe API, Stripe.js, Checkout, Elements, Billing, and webhooks.
Adyen
Accept payments with Adyen. Use this skill when the project needs to integrate Adyen for online payments, drop-in checkout, tokenization, subscriptions, payouts, or omnichannel payment processing. Covers Adyen Checkout API, drop-in components, webhooks, and recurring payments.
Braintree
Accept payments with Braintree (PayPal). Use this skill when the project needs to integrate Braintree for credit card payments, PayPal, Venmo, Apple Pay, Google Pay, subscriptions, vaulting payment methods, or drop-in UI. Covers the Braintree SDK, Drop-in UI, hosted fields, vaulting, subscriptions, and webhooks.