Skip to content
DocsGet started

Payments and usageAvailable with Expose

Stop stolen cards before they become chargebacks.

Bots test stolen cards in bulk and some payments get through. Put the session’s verdict on each Stripe payment, so Radar or your team can review or step up the risky ones before you capture.

For merchants and payment teams taking cards through Stripe.

Install ExposeSee how it works

Where 10,000 checkout attempts went

  1. Checkout attemptsCheckout attempts: 10,000
  2. Card-testing patternCard-testing pattern: 400
  3. Approved fraudulent paymentsApproved fraudulent payments: 40
  4. Chargeback cost at stakeChargeback cost at stake: $4,200Avoided only when your Radar rule or review acts before capture.

Human 94%Agent 1%Bot 4%Unknown 1%

Illustrative example 4% card-testing pattern; 10% of those approved; $90 average order plus a $15 dispute fee. Hypothetical.

Where money is affected

A chargeback costs the order, the fee and your standing.

Card testing runs many small checkouts with stolen cards. Each approved one can come back weeks later as a chargeback: you lose the goods, pay a dispute fee, and your dispute rate climbs.

Expose attaches its verdict to the PaymentIntent (da_class, da_score, da_agent). A Radar rule can then send likely bots to review, or ask an agent for 3D Secure. Nothing changes until a rule or a person acts on it.

The real picture

The same month, with and without the verdict on the payment.

Payments sent to reviewPayments sent to review: 400
Chargebacks if not reviewedChargebacks if not reviewed: 0−100%
Dispute costDispute cost: $0−100%

Illustrative example Hypothetical figures; your own numbers will differ.

Your numbers

What it could mean for you.

Replace the example with your own figures.

Chargeback cost at stake
$4,200
Approved fraudulent payments
40
Payments to review
400

At stake = attempts × share card-testing × share approved × (order + dispute fee).

Illustrative example Your numbers, not a promise. Savings depend on the decisions you make with the evidence.

An example decision

One payment, before capture.

Illustrative example
PaymentIntent
pi_3Q…8kd
da_class
bot
Radar rule
Review if ::da_class:: = 'bot'
Outcome
Held for review

The card is never charged until someone looks. A real customer’s agent would be asked for 3D Secure instead.

How it fits

From evidence to a decision.

  1. 01

    Add a public key

    Tokens need a public key on the snippet; keyless installs cannot sign them.

  2. 02

    Get a token at checkout

    Call doubleagent.stripeToken() in the browser before confirming.

  3. 03

    Attach on the server

    Verify it and call attachVerdict with @doubleagent-so/node.

  4. 04

    Write Radar rules

    Review bots, step up agents on large amounts. Custom rules need Radar for Fraud Teams.

What your team can do

Act on it, your way.

Before you start.

Will agents paying for real customers be blocked?

No. Agents are tagged, not refused. A rule can ask for 3D Secure, so a real cardholder can still pay.

What if there is no token?

A missing token means unknown, not bot. Don’t write rules that treat it as fraud.

Does Expose fight or win disputes?

No. It labels the payment; Stripe Radar and your team decide, and disputes stay with your normal process.

Does Radar update when a session is relabelled?

Not automatically yet. Use the Debrief and call attachVerdict again.

Available with Expose

See the real picture.

Install Expose

Stripe guideDouble Agent for e-commerceDouble Agent for fintech