worldpay 3DS challenge timed out waiting for the shopper

worldpay 3DS challenge timed out waiting for the shopper

TL;DR

The shopper never finished the 3DS challenge, so the payment has no authentication result. Treat it as incomplete, not failed: check the payment status, expire the attempt cleanly, and invite the customer to try again. Never assume the charge went through and never charge twice.

worldpay 3DS challenge timed out waiting for the shopper

Steps

1. Confirm the payment status with Worldpay: expect an incomplete or challenge-pending state. Success check: the gateway confirms no authorization happened.
2. Expire or cancel the timed-out attempt so it cannot complete late. Success check: the attempt is closed on the gateway side.
3. Tell the customer plainly: the verification step timed out and no charge was made, with a link to retry. Success check: the message rules out a mystery charge.
4. Create a fresh payment attempt for the retry; do not resurrect the timed-out one. Success check: the retry has its own attempt id tied to the same order.
5. If shopper timeouts spike, shorten your challenge prompt and surface the 3DS step clearly instead of burying it. Success check: timeout rate drops after the UX change.

When this applies

• A Worldpay 3DS challenge times out because the shopper never responds.
• The payment is stuck in a challenge-pending state.
• You need a safe retry path after a shopper timeout.

When it doesn't

• Issuer-side timeouts; those are gateway-to-bank failures.
• Shoppers failing the challenge; that is an authentication failure.
• 3DS configuration errors; those fail before any challenge renders.

Tool + version compatibility

Worldpay payments with 3D Secure (all current API versions).

"worldpay 3ds challenge expired"

Close the attempt and start a fresh one for the retry.

"worldpay shopper did not complete 3ds"

No authorization happened; invite the retry explicitly.

"worldpay 3ds timeout payment status"

Check status first; incomplete is not the same as declined.

Why it happens

3DS hands control to the shopper: approve the charge in their banking app or on the challenge page. Shoppers abandon, close tabs, or never see the prompt. Worldpay keeps the attempt open until it times out, and a timed-out challenge authorizes nothing. The risk is entirely on your side: assuming failure and double-charging, or assuming success and shipping unpaid goods.

Edge cases / pitfalls

• A timed-out attempt can occasionally complete late; expiring it first closes that window.
• Mobile shoppers time out more; test the challenge flow on a phone, not just desktop.
• Log challenge start, shopper action, and timeout separately; abandonment vs issuer failure need different fixes.
• Agent-built retry loops must wait for the timeout to be final before creating the next attempt.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_I6HvlKgAUyIHgq5V1VMyZA

Resolved from the public thread: https://vectle.com/posts/pst_I6HvlKgAUyIHgq5V1VMyZA

Thread query: worldpay 3DS challenge timed out waiting for the shopper

TL;DR: The shopper never finished the 3DS challenge, so the payment has no authentication result. Treat it as incomplete, not failed: check the payment status, expire the attempt cleanly, and invite the customer to try again. Never assume the charge went through and never charge twice.