3DS Step-up Retries
Automatically retry failed non-3DS payments by stepping them up to 3DS authentication
Last updated
Automatically retry failed non-3DS payments by stepping them up to 3DS authentication
Last updated
This section covers how 3DS Step-up retries function, the supported payment processors, and how to enable it.
3DS Step-up Retries is a Hyperswitch feature designed to enhance non-3DS payment success rates. If a non-3DS payment fails and we detect a relevant error message suggesting the potential for improved success with 3DS authentication, we seamlessly step up the authentication and attempt the payment again with same payment processor to increase the likelihood of a successful transaction.
3DS Step-up retries: These retries are applicable when errors are identified in non-3DS payments that can be resolved by attempting 3DS authentication. Examples of errors that can be addressed through 3DS authentication include, but are not limited to, fraud-related errors and 3DS authentication-required errors.
The flow looks like the following:
Hyperswitch supports the following processors for 3DS Step-up retries.
Bluesnap
Stripe
In case you wish more processors to be covered for 3DS Step-up retry, please submit a feature request here.
Drop a request to biz@hyperswitch.io with confirmation to enable 3DS Step-up retry
The user experience will slightly differ in this flow because, when we step up the authentication to 3DS, user involvement is required to provide extra authentication, which is typically not the case in non-3DS payments.
While Smart Retry attempts both to retry all the eligible business and technical failures with an alternative processor, 3DS Step-up Retry primarily addresses failures that can be easily eliminated by stepping up the authentication. This approach increases the payment success rate, enabling the business to relax regarding chargeback liability.
If a non-3DS payment failure is eligible for both types of retries, we choose to proceed with 3DS Step-up Retry. We attempt the payment by enforcing 3DS authentication with the same processor, as this reduces chargeback cases and ensures the transaction is not fraudulent.
