FlashADAPTIVE 3DS

Decide when 3DS triggers, customer by customer

Strong Customer Authentication only adds friction when you ask for it. Worthy reads every charge against your trigger rules and decides on the spot whether to step up to 3DS or send the transaction frictionless. Over 50 trigger conditions available. Your conversion stays high, your liability stays covered.

adaptive checkout intelligence

  • +12.4% net auth lift
  • 50+ trigger conditions
  • 82.4% frictionless

Setting2HOW IT WORKS

Three checks,
one decision

Worthy reads each charge before it leaves your servers, matches it against your trigger rules, and either authenticates or sends the transaction frictionless. The buyer only sees the challenge when you've decided it's worth showing.

STEP 01

Read the charge

Country, amount, card type, MCC, device signals, buyer history. Worthy pulls every relevant attribute on the way to authorization.

STEP 02

Apply your rules

The rule engine evaluates every trigger condition against the charge. The first match wins. Authentication fires or it doesn't.

STEP 03

Challenge or pass

If a rule fires, Worthy invokes 3DS through the issuing bank. If nothing fires, the charge skips authentication entirely. Either way, liability shifts to the issuer when authentication succeeds.

Setting2TRIGGER CONDITIONS

Over 50 conditions
you can trigger on

Worthy ships with a wide library of triggers across geography, card details, charge attributes, buyer profile, and risk signals. Use them on their own or combine them with AND and OR to build precise rules.

Geography

Issuer country, buyer country, or merchant country. Trigger by region, ISO code, or risk tier.

Card details

BIN, card brand, product type, or issuer. Trigger on commercial cards, prepaid, or specific banks.

Charge amount

Trigger above thresholds in any currency. Tier rules to match how your business handles risk.

Merchant category

The MCC code determines how the network classifies your business. Some categories require authentication.

Device profile

New device, suspicious user agent, mismatched timezone. Trigger when device signals look off.

Buyer history

Brand-new buyer, returning customer, or vaulted card. Skip the challenge when you already trust the person.

Time signals

Off-hours charges, holidays, or unusual timing. Issuers behave differently across the day.

Risk score

Trigger 3DS only when Worthy's risk model flags the charge. High-risk gets challenged, the rest pass through.

FlashRELAY SYSTEM

One 3DS challenge,
multiple processor attempts

The buyer completes 3DS once. If the first processor declines the payment, Worthy passes the same authentication to the next processor. The retry does not require a second challenge.

01Buyer authenticates once

The 3DS challenge runs in the browser exactly once. Worthy captures the authentication artifact.

02Worthy relays the artifact

When the first processor declines on a soft code, Worthy relays the same 3DS authentication to the next.

PadlockEXEMPTIONS

Built-in rules for the charges that skip the challenge

Some charges qualify to skip 3DS entirely under network rules. Worthy ships pre-built exemption logic for low-value, trusted-buyer, recurring, and merchant-initiated payments. The exemption is requested, the network confirms, and the buyer sees no interruption.

GlobalOBSERVABILITY

See the frictionless
rate by region, by rule

Track how many charges qualified for frictionless, how many got challenged, and what each rule contributed. Drill into any region to see issuer-level authentication patterns.

Laptop CodeDEVELOPER API

3DS state, exposed
on every charge

Every charge response includes the 3DS decision, the rule that triggered, and the authentication artifact when a challenge ran. Build dashboards, alerts, or audit trails on top.

The  three_d_secure object on every charge captures the full authentication trace.

  • decision is one of frictionless, challenged, or exempt.

  • matched_rule shows which trigger fired, if any.

  • liability_shift tells you whether the issuer accepted authentication.

  • relayed_to lists every processor that received the authentication artifact.

json
const response = {
"id": "ch_8FA2B",
"status": "succeeded",
"amount": 74900,
"three_d_secure": {
"decision": "challenged",
"matched_rule": "country_my",
"version": "2.2.0",
"liability_shift": true,
"authentication_value": "h7g9k...",
"relayed_to": [
"processor_1",
"processor_2",
"processor_3"
],
"exemption_requested": null,
"challenge_ms": 2840
}
};

ShieldPAIRS WELL WITH

Adaptive 3DS works alongside
the Acceptance Engine

Smart Routing picks the processor, Cascade catches the soft declines, and Adaptive 3DS makes sure liability shifts when it should. Stack them to capture every recoverable charge.

Smart Routing

Score acquirers in real time. Send each charge to the path most likely to clear.

Cascade Fallbacks

Retry soft declines on backup processors. Up to four attempts per charge.

Adaptive 3DS

Trigger authentication only when you want it. 50+ trigger conditions available.

Network Tokenization

Replace card numbers with tokens that survive reissues and expirations.

FlashREADY WHEN YOU ARE

Trigger 3DS only when it pays

Apply for a Worthy account and configure your 3DS triggers in minutes. No contracts, no setup fees, no engineering team required. Talk to sales for a custom package or volume pricing.