3ds-challenge-failed-after-customer-co-2aefc60fdc41b03blisted
Install: claude install-skill Vectle/skills
## TL;DR
If the customer finished the challenge and the payment still failed, the break is usually between the authentication result and your confirmation call. Stop re-confirming the same PaymentIntent and read the three_d_secure result fields instead. Capture the result once so the customer is never asked to authenticate twice.
```text
3ds challenge failed after customer completed authentication
```
## Use this when
- The customer completed the bank challenge but the payment shows as failed.
- Your logs show authentication succeeded and confirmation failed.
## Not for this skill when
- The customer abandoned the challenge halfway. That is a UX problem, not an integration bug.
- The issuer declined during the challenge. Treat that as a hard decline.
- Skipping authentication is out of scope for this skill.
## Steps
1. Read the PaymentIntent status plus the three_d_secure authenticated and succeeded fields. Verify: you know whether auth actually succeeded.
2. If authentication succeeded but confirmation failed, do not call confirm again. Create a fresh PaymentIntent for the retry. Verify: the customer is never asked to authenticate twice.
3. If authentication shows failed or not attempted, check your return URL and webhook handling for the post-challenge redirect. Verify: the redirect lands and your handler runs.
4. Confirm server-side immediately on callback to shrink the gap between challenge completion and confirmation. Verify: no timeout window sits between the auth r