Library · Payment orchestration · Guide
Pre-auth vs post-auth 3DS — claim map
GuidePre-auth vs post-auth 3DS — claim mapBack to article
First-try challenge vs step-up after soft decline. Filter the claim. Distinct from 3DS-lift dollars and step-up-retry windows.
| Claim | Reality | Measure / ask | Do not |
|---|---|---|---|
| One 3DS drop % covers first-try and step-up | No. Different who pays friction; different sample | First-try drop and step-up abandon separately | Paste one slide onto both paths |
| Step-up is free of the retry / TPE count | Usually no — still an auth attempt unless notice excludes it | Written count rule on this MID | Assume step-up is invisible to the window |
| Pre-auth on every cart because liability shift | No. Shift needs success. Clean shoppers still pay the tax | Amount / BIN / risk placement on the lift page | Challenge every landing for shift theater |
| Step-up fixes soft NSF | No. NSF is money. A challenge does not create balance | NSF on the soft/hard playbook — not 3DS | Step-up NSF days like expired-card updater |
| This map is the 3DS-lift calculator | No. Lift types tax vs fraud $. This map is pre vs post fork | N/A — open three-ds-lift for dollars | Skip measuring because you named the fork |
| This map is the step-up retry claim map | No. Step-up-retry is count / shift / hop rules. This map is placement fork | N/A — open step-up-retry for the window | Confuse fork naming with retry writing |
Filter the claim. Pre-auth taxes the first try. Step-up hits after a soft decline and still usually burns a retry. Measure each path — do not paste one drop onto both.
Pairing procedure: Pre-auth 3DS is not the same tax as step-up. Topic: Orchestration.
Work with us — We run this job on your accounts. Services