OpenAI Financial Services Europe & UK

Stripe

Enterprise Knowledge Search · Fraud Detection

Stripe needed to discover where large language models could most meaningfully improve developer support, business understanding, and fraud detection across a large payments platform and community ecosystem.

100 employees mobilized to prototype GPT-4-powered features
15 prototypes considered strong candidates for integration
50 AI use cases identified
GPT-4 outperformed human reviewers in business classification tasks

Reported impact

Business outcome

Stripe identified dozens of viable GPT-4 use cases, found that the model outperformed human reviewers in business classification, improved developer support workflows, and strengthened its ability to detect malicious community behavior.

  • Productivity Improvement
  • Risk Reduction
  • Speed to Market

Solution

Stripe used GPT-4 as a cross-functional experimentation layer across support, onboarding, risk, and documentation workflows. The company paused normal work for 100 employees so they could prototype candidate features, then narrowed roughly 50 ideas into a smaller set of strong product directions. GPT-4 now scans customer websites and summarizes what a business actually does so support can be tailored without laborious manual research, reads Stripe documentation on behalf of developers and returns focused technical answers, and analyzes inbound community communications to identify likely fraudsters or coordinated bad actors. These capabilities build on earlier GPT-3 support-routing and summarization work, but GPT-4's stronger reasoning over free-form text and images made it practical to move from small assists to workflows that outperform human reviewers in some classification tasks and can be productized inside Stripe's broader support and risk systems.

Data flow

Free-form website content, developer questions, documentation, and community posts are sent to GPT-4, which summarizes business context, surfaces relevant support answers, or flags suspicious patterns for fraud teams. Stripe then uses those outputs inside its support, onboarding, and risk processes.

Solution architecture

1 components · 1 layer
  1. Compute
    • GPT-4 Summarizes customer businesses, answers documentation questions, and flags suspicious community activity across Stripe workflows.

Architecture clues

  • Experimentation sprint spanned support, onboarding, risk, and documentation teams
  • GPT-4 summarizes sparse or ambiguous customer websites
  • Same model layer answers technical documentation questions and supports fraud screening in community channels

Evidence from the source

"GPT is able to understand the user's question, read detailed documentation on their behalf"
"GPT-4 is able to scan these sites and deliver a summary, which outperforms those written by people."
"Just by analyzing the syntax of posts in Discord, GPT-4 has been flagging accounts"
"Stripe asked 100 employees to do something highly unusual: stop their day jobs and instead, dream up features and functionality"
Transparency Evidence & methodology 75/100 reference value · 85% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value75/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact0/25
    0 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence85%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    4 direct source quotes retained.
  • Date provenance8/10
    The publication date comes from publisher-controlled metadata.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity8/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. OpenAI

    Stripe customer story

    First-party
    https://openai.com/index/stripe/
    Source type
    Vendor-published customer story
    Published
    Mar 14, 2023
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.