This event is triggered when a customer’s payment fails due to needing 3D Secure (3DS) verification.

How to use this event?

This event can be used to trigger any type of integration action. The most common use cases are to trigger your CRM to send an email to notify the customer of an issue, and/or trigger an internal notification to someone on your team to alert them of an issue with a payment that may require extra attention or outreach to the customer to resolve.

What is 3DS verification?

3DS is a security layer created by European legislation with the intention to prevent fraudulent transactions. It is essentially 2-Factor Authentication (2FA), or two-step verification on payments made with credit cards. This 2-step verification is triggered by a customer’s bank to ensure a charge is valid.

Payments needing 3DS verification are becoming more and more common, however, it seems to be more commonly encountered for international customers who live in the EU, UK, and Australia.

3DS is not something that is triggered by Spiffy, or Stripe. It is triggered by the customer’s bank, usually via an email notification from the bank that requires the customer to click to authorize/approve the transaction.

More Information:
Stripe 3D Secure Documentation
3D Secure Wikipedia