{"section":"known-issues","requestedLocale":"en","requestedSlug":"transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds","locale":"en","slug":"transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds","path":"docs/en/known-issues/Payments/transactions-with-the-tnspay-connector-being-denied-by-error-card-not-enrolled-in-3ds.md","branch":"main","content":"## Summary\n\nWhen using the **TNSPay** connector with **3DS authentication** configured, a race condition causes the authorization method to be called **twice within 2 seconds**. The second authorization response only arrives after the transaction has already entered the cancellation flow, resulting in the transaction being denied with the error:\n\n> `Card not ENROLLED in 3DS`\n\nThe payout fields also end up in an inconsistent state as a consequence of the duplicate authorization attempt.\nThe issue is identifiable by the following log appearing twice at the start of the transaction:\n\n> `Authorize using 3DS given the configurations 3DS: always MinimumValue`\n\n## Simulation\n\nUnable to reproduce in a controlled environment. The race condition occurs intermittently in production.\n\n## Workaround\n\nThere is no workaround"}