Before removing 3DS, it is always best to first try and understand why the transactions are failing. Depending on your region, 3DS could be mandatory and removing it without an adequate exemption in place may result in Strong Customer Authentication (SCA) non-compliance.
To handle cases where the customer's card is not enrolled for any version of 3DS, you can set the `attempt_n3d field` to `true` to downgrade the transaction to non-3DS. This means that if the customer's bank does not support 3DS, we will automatically attempt to process the payment without 3DS authentication instead.
For more information, see our SCA compliance guide.