3DS challenge initiation latency spikes under concurrent requests

3DS challenge initiation latency spikes under concurrent requests

The threedsmax library exposes a single method to start a 3DS challenge and expects the payment gateway to return a challenge URL. When a burst of simultaneous requests hits this endpoint, the response time increases dramatically, and occasional timeouts occur.

There is no documented fallback path to 3DS v1 if the v2 challenge fails, and the library does not expose a timeout or retry configuration for the challenge initiation call. This raises uncertainty about how the library behaves under high load and whether it can gracefully degrade to an older protocol.

What is the maximum concurrent request threshold before latency degrades, does threedsmax automatically fall back to 3DS v1 when a v2 challenge cannot be completed, and is there a configurable timeout for the challenge initiation API?