{"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\n\nThe default is that they are canceled and we send two Authorize 3Ds Requests, and you still haven't received the Authorize Request response.\nThe second response only appears after it has already entered the cancellation flow.\n\nThe issue is due to a race condition, and this causes the payout fields to be inconsistent.\nAt the beginning of the process, the first log is\n\n`Authorize using 3DS given the configurations 3DS: always MinimumValue`\n\nThe authorization method was called 2 times within 2 seconds.\n\n\n#### Simulation\n\n\nCannot simulate\n\n\n#### Workaround\n\n\nThere is no workaround"}