3ds2-declined-with-liability-shift-mis-4e3d4ab46f60c1dflisted
Install: claude install-skill Vectle/skills
## TL;DR
Liability shift only happens when authentication succeeds. A declined challenge means the issuer said no, so the liability stays with you and the payment is dead. Treat it as a hard decline and route the customer to another payment method.
```text
3ds2 declined with liability shift missing: how to fix
```
## Use this when
- A challenged payment declines and the charge shows no liability shift.
- You need to decide whether to retry, reroute, or abandon the payment.
- Finance asks why a 3DS payment still produced a chargeback.
## Not for this skill when
- Authentication succeeded and liability shifted. That payment worked as designed.
- You want the challenge to succeed. No integration change forces an issuer's hand.
- The goal is avoiding authentication. That is out of scope for this skill.
## Steps
1. Read the charge's three_d_secure fields and the outcome decline code. Verify: you can confirm authentication did not succeed.
2. Treat the payment as a hard decline. Show the customer a clear message and offer another payment method. Verify: no automatic retry of the same card inside the session.
3. Check whether the payment went through frictionless flow or a full challenge, to separate issuer declines from integration gaps. Verify: you know which path the payment took.
4. For low-risk orders, request a TRA exemption on the next attempt instead of forcing another challenge. Verify: exemption requests only go out for orders that meet your risk criteria.
5. Track dec