If a high value transaction fails because of 3DS, notify internal user

For extra fraud protection, 3D Secure (3DS) requires customers to complete an additional verification step with the card issuer before being able to complete the transaction. Typically, the customer is directed to an authentication page on their bank’s website, where they enter a password associated with the card or a code sent to their phone. This process is familiar to customers through the card networks’ brand names, such as Visa Secure and Mastercard Identity Check.

3DS is a valuable fraud prevention tool, but losing any transaction because a user can’t complete their step-up authentication is a challenge for any business. With this recipe, your team can provide an elevated customer experience by reaching out to these high-value customers where the transaction failed due to 3DS, and try to guide legitimate customers to complete their transaction, potentially using a different payment method.

Get started with WhenThen and get notified right away when there’s an opportunity to save transactions by taking action directly with the user.