Skip to article
ecomservices.io
Payment orchestration · How to run this
RoutingCalculatorCascadeCalculatorRetriesCalculator3DS placementCalculatorDeclinesCalculatorAffinityNot on this page yetOptimisationCalculator

Library · Payment orchestration · How to run this

Ask whether step-up 3DS still burns the retry window

How to run thisPayment orchestration4 steps
GuideStep-up 3DS on retry — claim map · Calculator lives in the articleOpen

Step-up retry means you add a 3DS challenge on a later attempt after a soft decline. That path is not free of the written retry window. Issuer messages and gateway attempts still count unless the notice says otherwise. It is not the same job as first-try 3DS placement dollars or shift vs ratio.

Pair: Step-up 3DS on retry — claim map on Orchestration. Pre-auth vs step-up fork: pre-auth vs post-auth 3DS. Soft vs hard next action: decline code playbook. Cascade auth burn: cascade pollution.

What to get in writing

Whether step-up challenges sit inside this MID’s retry / TPE count. What the gateway logs as authenticated vs attempted on the recycle. Whether unique-billing attempts include the step-up hop.

What not to do

Do not assume a challenge is free of the window. Do not count failed challenges as shifts. Do not step-up NSF hoping for cash. Do not hop hard fails onto a spare MID.

Related: Orchestration, retry window, clear-PAN retry, 3DS lift.

Procedure

  1. Name the soft decline family — hard fails stop.
  2. Ask in writing whether step-up counts in this retry window.
  3. Only successful authentication can shift qualifying fraud.
  4. Measure auth burn; do not hop dead cards.

Failure modes

  • Assuming step-up is free of the TPE / processor retry count.
  • Treating failed challenges as liability shift.
  • Stepping up hard fails onto a spare MID.
  • Using step-up to “fix” NSF.

Worked example

None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.

Glossary

Step-up retry
Adding a 3DS challenge on a later attempt after a soft decline. Still usually an auth attempt unless the notice excludes it.

Work with us — We run this job on your accounts. Services

FAQ

Does step-up 3DS count as a new retry?
Usually yes — it is still an auth attempt unless your processor or TPE notice excludes it in writing.
Does a failed step-up get liability shift?
No. Shift needs a successful authentication.
Can I step-up a hard fail on another MID?
No. Hard fails kill the token. Hopping buys chargebacks.