Braintree 3D Secure Authentication Failed

Share
Ongoing Web, iOS, Android, Server SDKs Updated November 13, 2026Based on 4 user reportsHow we research

Quick answer

3DS failures usually come from a Control Panel rule rejecting transactions without liability shift, or an integration problem. Log threeDSecureInfo and check the rule.

Most likely fix: Log threeDSecureInfo

How to fix it

Try these in order — the most common fix is first.

  1. 1. Log threeDSecureInfo

    1. Inspect liabilityShifted and liabilityShiftPossible
    2. If possible is true but shifted false, authentication failed
    Did this fix it?
  2. 2. Review the rules

    1. Control Panel > Settings > Processing > 3D Secure
    2. Check reject rules for Liability Not Shifted and Card Ineligible
    Did this fix it?
  3. 3. Use a client token

    1. Tokenization keys cannot verify 3DS cards
    2. Generate a client token server-side
    Did this fix it?
  4. 4. Ask for another payment method

    1. Suggest another card or PayPal when the issuer fails the challenge
    Did this fix it?

Symptoms

Error 81571 'Failed to authenticate', liabilityShifted false, or no challenge ever appears.

Why it happens

  • Reject rule for Liability Not Shifted
  • Card ineligible for 3DS or issuer bypass
  • Using a tokenization key instead of a client token

This guide also covers

  • braintree 3d secure not working
  • braintree 81571

Still not working?

If Braintree keeps failing, you're not alone. See every Braintree problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other Braintree errors

All 11 Braintree errors and fixes →