New Timeout Reasons

🚀 New 3DS Timeout Reason Codes Now Available in Finalised Event V2

We’ve enhanced transaction visibility by introducing two new reason values for timed-out transactions. These additions provide clearer diagnostics around cardholder interaction and out-of-band authentication flows.

🔎 New transaction.reason Values

NO_CHALLENGE_PAGE_SUBMIT

The cardholder did not return to the challenge page to proceed with the transaction.

NO_OOB_CONFIRMATION

The out-of-band authentication or decline callback was not received.

📡 Where You’ll See This

These values are now included in the transaction.reason field of the Finalised Event V2 webhook that you are currently consuming.

🎯 Why This Matters

• More granular timeout diagnostics
• Improved root cause analysis for 3DS flows
• Better reporting and merchant support workflows
• Clearer differentiation between user abandonment and missing OOB callbacks

No integration changes are required. The new values will automatically appear in the existing webhook payload.

If you rely on transaction.reason for routing, analytics, or dispute investigation, ensure your handling logic accounts for these new states.