Library · Payment orchestration · How to run this
3DS routing can abandon the auth
3DS-routed auths leave the happy path. Some abandon before challenge complete. Lost $ = routed × (abandon % ÷ 100) × AOV. Type 3DS routed, abandon %, and AOV $.
Pair: 3DS route abandon on Orchestration. Step-up: step-up abandon. Lift: 3DS lift.
What you type
3DS routed — auths sent to 3DS on this route / workflow in the window.
Abandon % — share of those that never completed the challenge (orchestration export).
AOV $ — average order value on the routed set.
Abandoned ≈ routed × abandon %. Lost $ = abandoned × AOV. Tighten routing or UX when lost $ is material — do not invent an abandon chip.
What not to do
Do not invent an abandon percent. Do not mix soft declines into abandon without splitting. Do not treat completed 3DS failures as abandon. Do not ignore AOV when comparing two routes.
Related: Orchestration, step-up abandon, 3DS lift, workflow timeout.
Procedure
- Type 3DS-routed auth count and abandon %.
- Type AOV $ on the routed set.
- Tighten routing or UX when lost $ is material.
Failure modes
- Inventing an abandon percent.
- Mixing soft declines into abandon without splitting.
- Treating completed 3DS failures as abandon.
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
- 3DS route abandon lost $
- Routed × (abandon % ÷ 100) × AOV. Workflow 3DS path that never completes.
Work with us — We run this job on your accounts. Services
FAQ
- Is this step-up abandon cost?
- Related abandon. [Step-up abandon](/manuals/forter-step-up-abandon-cost) is fraud step-up / challenge exit. This page is workflow 3DS-routed auths that never finish.
- Is this 3DS lift?
- Related 3DS. [3DS lift](/manuals/three-ds-lift) prices approval lift from 3DS. This page prices abandon on the routed path.
- What abandon percent should I invent?
- None. Type abandon % from the orchestration / 3DS export for that route.