---
title: "Easily debug your 3DS authentication with Stripe Workbench"
description: "Stripe Workbench provides browser-based tools for investigating EMV 3DS authentication and related payment flow behavior in the Stripe dashboard. It lets developers inspect Payment Intent and Charge data, including payment_method_details.card.three_d_secure.authentication_flow and result, to determine whether authentication used a challenge UI and whether it completed successfully. The Inspector also exposes API history and webhook events, while the Events tab can filter historical payment_intent.requires_action events and show their frequency over a selected period. In the Shell tab, stripe trigger payment_intent.requires_action simulates a 3DS-related flow and generates event data without installing additional tools, allowing webhook handling to be tested and investigated from the dashboard."
---

# Easily debug your 3DS authentication with Stripe Workbench

[Stripe](https://yomu.fyi/company/stripe) · Hidetaka Okamoto · Oct 22, 2024

**Type:** Tutorial

## Summary

Stripe Workbench provides browser-based tools for investigating EMV 3DS authentication and related payment flow behavior in the Stripe dashboard. It lets developers inspect Payment Intent and Charge data, including payment\_method\_details.card.three\_d\_secure.authentication\_flow and result, to determine whether authentication used a challenge UI and whether it completed successfully. The Inspector also exposes API history and webhook events, while the Events tab can filter historical payment\_intent.requires\_action events and show their frequency over a selected period. In the Shell tab, stripe trigger payment\_intent.requires\_action simulates a 3DS-related flow and generates event data without installing additional tools, allowing webhook handling to be tested and investigated from the dashboard.

## Context

Developers may need to investigate payment failures and determine whether EMV 3DS authentication occurred, whether it used a risk-based flow or displayed an identity-verification UI, and why a transaction was rejected.

## Approach / What changed

Use Stripe Workbench in the dashboard to inspect Payment Intent and Charge objects, review API and webhook histories, filter historical payment\_intent.requires\_action events, and run Stripe CLI trigger commands in the Shell tab to simulate 3DS-related events.

## Takeaways

- The Charge object's payment\_method\_details.card.three\_d\_secure.authentication\_flow indicates the 3DS flow type; a value of challenge means the authentication UI was presented to the customer.
- The three\_d\_secure.result\_reason field can explain a failed 3DS flow; card\_not\_enrolled means the card does not support 3D Secure or has not been set up for it.
- Running stripe trigger payment\_intent.requires\_action in Workbench's Shell tab creates simulated event data for testing webhook-driven payment handling without installing additional tools.

**Tags:** [Authentication](https://yomu.fyi/topic/authentication), [Developer Experience](https://yomu.fyi/topic/developer-experience), [Monitoring](https://yomu.fyi/topic/monitoring), [Testing](https://yomu.fyi/topic/testing)

- Source: [Stripe](https://stripe.dev/blog/easily-debug-your-3ds-authentication-with-stripe-workbench)
- Source URL: https://stripe.dev/blog/easily-debug-your-3ds-authentication-with-stripe-workbench
- Ingested by Yomu: 2026-08-28T08:56:38.548Z

[Read original post](https://stripe.dev/blog/easily-debug-your-3ds-authentication-with-stripe-workbench)