Intelligent 3DS

Intelligent 3DS for balanced authentication.

Authenticate with intent, not by default — risk-informed 3DS adds protection where it helps and keeps friction off transactions that don't need it.

Risk-informed
Step-up where useful
Frictionless flow
Signals3DS decision
Device & contextTransaction riskIssuer requirementMerchant policy

3DS decision · per transaction

Frictionless
Challenge · step-up
Review · route
Low risk · frictionlessHigher risk · step-up
Why not authenticate everything

Every challenge has a cost.

Some transactions need authentication. Many don't. Treating them all the same adds friction exactly where it isn't needed.

Challenge everything
Risk-informed
FrictionlessChallenged
01Friction

Friction has a cost

Challenging every transaction treats good customers like risks. Authentication should be intentional, not a default.

02Issuers

Issuer requirements differ

Some transactions need issuer or customer authentication — the decision layer accounts for where it is required.

03Context

Risk context matters

Device, transaction and history signals tell different stories. 3DS decisions are informed by them, per transaction.

04Balance

Security and conversion, balanced

Intelligent 3DS helps balance payment security, issuer requirements and conversion impact — without guesswork.

Risk-informed authentication

Signals in. Decision out.

Each transaction is decided on its own context — not on a blanket rule.

Signals

Device & context
Transaction risk
Issuer requirement
Merchant policy

3DS decision

Authentication applied with intent — informed by the signals, per transaction.

Frictionless

Low risk — no challenge added.

Challenge · step-up

Authentication where it adds protection.

Review · route

Higher risk — handled with controls.

Decided per transaction. Part of the same decision layer as fraud controls — not a separate bolt-on.

Decision layerFraud controls
3DS in the payment path

One decision inside the flow — not a detour.

Checkout
Risk signals
3DS decision
Authorization
Outcome visibility

Challenge only where useful

Step-up is applied when signals or issuer requirements call for it — not as a blanket rule on every payment.

Context carried into visibility

Authentication outcomes stay attached to the transaction — visible to your team alongside risk and routing context.

Operations & policy

Authentication your team can steer.

Step-up thresholds and policies are configurable per integration — and every outcome stays visible, with its authentication context, in the merchant portal preview.

PoliciesStep-up thresholdsSignal contextOutcome visibility
Authentication policy
Step-up thresholdConfigurable
Low risk · frictionlessHigher risk · step-up
Issuer requirements
RequiredOptional
Risk signals
FrictionlessStep-upAuthenticatedReviewed
Intelligent 3DS

Add intelligent 3DS to your card payment flow.

Talk to our team about risk-informed authentication, step-up policies and how outcomes stay visible to your team.

Risk-informed

3DS decisions informed by risk signals.

Less friction

Can reduce unnecessary challenges on good transactions.

Issuer-aware

Authentication where requirements call for it.

Visible outcomes

Authentication context in the portal preview.