Fraud Architect

Job description

Who we are About Stripe Stripe is a financial infrastructure platform for businesses. Millions of companies—from the world's largest enterprises to the most ambitious startups—use Stripe to accept payments, grow their revenue, and accelerate new business opportunities. Our mission is to increase the GDP of the internet, and we have a staggering amount of work ahead. That means you have an unprecedented opportunity to put the global economy within everyone's reach while doing the most important work of your career. About the team The Fraud Architect team helps Stripe’s largest and most complex users manage fraud and abuse across the customer lifecycle. We combine deep fraud expertise, technical investigation, and product knowledge to help users understand emerging threats, optimize Radar, and implement durable prevention strategies tailored to their business and risk tolerance. Our goal is to enable users’ growth by proactively reducing fraud while protecting legitimate customer activity and turning frontline insights into better products and defenses. What you’ll do Stripe users face fraud and abuse across the customer lifecycle, including payment fraud, free-trial farming, multi-account abuse, and usage-based billing exploitation. They need a partner who understands their business, anticipates emerging threats, and helps them put effective protections in place as their business and the threat landscape evolve. As a member of our Fraud Architect team, you’ll be the fraud and risk specialist embedded in strategic user relationships for a small portfolio of named users, acting as a technical extension of their teams. You’ll help users get more from Radar, build a proactive prevention strategy, and turn complex fraud problems into practical decisions. This role combines analytical rigor, deep fraud investigation, and product judgment. You’ll develop a deep understanding of how Radar scores and classifies transactions, how integrations and available signals affect its decisions, and where its capabilities and limitations matter for a user. You’ll explain what the evidence supports, investigate what it does not yet explain, and translate both into action: better rules and thresholds, integration guidance, or model and feature gaps to pursue with our product teams. Your focus is proactive, user-specific risk ownership and durable prevention. You’ll provide user context, communicate implications and next steps, and turn incident findings into an implemented and verified prevention plan. You’ll help build, expand, and evolve defenses as user needs and fraud patterns change. Responsibilities Own each user’s prevention strategy. Maintain a current risk baseline, threat model, and agreed prevention plan for every assigned account. Understand payment methods, integrations, billing flows, trial and promotion mechanics, existing controls, and risk preferences; identify the top risks and gaps across the full customer lifecycle. Make Radar’s behavior understandable and actionable. Investigate scoring, classification, rule behavior, and signal coverage using transaction evidence and technical context. Explain observed behavior and uncertainty clearly, distinguish configuration or integration issues from potential model or feature gaps, and recommend the right next step for the user and our product teams. Design and improve user protections. Help users configure and optimize Radar for their business model and risk tolerance. Develop and validate user-facing rules, thresholds, and integration recommendations, test their expected impact, and guide approved implementation. Balance fraud prevention with legitimate payment acceptance and false-positive risk, without taking on internal-rule deployment or model operations. Anticipate established and emerging fraud vectors. Investigate payment, account, and behavioral patterns to understand how abuse works and where it may move next. Advise on payment fraud, trial and promotion abuse, multi-accounting, bot activity, and usage-based billing exploitation. Evaluate defenses across payment methods and flows rather than treating each attack surface in isolation. Deliver consistent proactive coverage. Run a weekly risk-health review for every assigned account, including those without active incidents, and share a concise health update. Establish early-warning thresholds and not