Library · Payment orchestration · Guide
Step-up 3DS on retry — claim map
GuideStep-up 3DS on retry — claim mapBack to article
Adding 3DS on a soft retry is still a retry attempt unless your notice says otherwise. Filter the claim. Get the count rule in writing.
| Claim | Reality | Get in writing | Do not |
|---|---|---|---|
| Step-up 3DS does not count as a retry | Usually still an auth attempt on this MID — TPE / processor windows count messages, not “feel” | Does this notice exclude step-up challenges from the retry count? | Assume a challenge is free of the window |
| Failed step-up still gets liability shift | No. Shift needs a successful authentication — abandoned challenges are not shifts | What this gateway logs as authenticated vs attempted on the retry | Count failed challenges as shift wins |
| Step-up fixes soft NSF | No. NSF is money. 3DS does not create funds | N/A — wrong tool for NSF | Step-up every soft decline hoping for cash |
| Step-up is free of the cascade pollution count | Extra auths and issuer messages still burn. Net lift can hide the cost | Whether step-up hops sit in unique-billing attempts here | Ignore auth burn because the order finally paid |
| Hard fail → step-up on another MID | No. Hard fails kill the token. Hopping is how you buy chargebacks | N/A — stop, do not step-up | Open a spare MID to challenge a dead card |
| Checkout 3DS placement rules apply unchanged on retry | Retry step-up is a different path — still measure drop and fraud save, still respect the window | Who owns step-up rules vs first-try 3DS on this gateway | Copy first-try placement blindly onto every recycle |
Filter the claim. Step-up is usually still an auth attempt inside the written retry window. Failed challenges do not shift liability. Hard fails stop — do not open a spare MID to challenge a dead card.
Pairing procedure: Ask whether step-up 3DS still burns the retry window. Topic: Orchestration.
Work with us — We run this job on your accounts. Services