# CARD\_DECLINED\_VERIFICATION\_REQUIRED but user not challenged?

**URL:** <https://developer.squareup.com/forums/t/card-declined-verification-required-but-user-not-challenged/18498>\
**Category:** Questions\
**Tags:** payments-api, web-payments-sdk\
**Created:** [August 29, 2024, 11:40am UTC](https://developer.squareup.com/forums/t/card-declined-verification-required-but-user-not-challenged/18498 "2024-08-29T11:40:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![TheotimeVibes](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/theotimevibes/32/7308_2.png) [@TheotimeVibes](https://developer.squareup.com/forums/u/TheotimeVibes)\
**Post date:** [August 29, 2024, 11:40am UTC](https://developer.squareup.com/forums/t/card-declined-verification-required-but-user-not-challenged/18498/1 "2024-08-29T11:40:04Z")

</div>

Hello there,

I’m facing another issue. Everything works well in sandbox but once I use a real card in production mode:

- User is not challenged (userChallenged = false from verifyBuyer)
- verification\_token is sent (verified from Square’s API log)
- Get CARD\_DECLINED\_VERIFICATION\_REQUIRED error

Can we somehow force challenge?

Thank you

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [August 29, 2024, 11:40am UTC](https://developer.squareup.com/forums/t/card-declined-verification-required-but-user-not-challenged/18498/2 "2024-08-29T11:40:23Z")

</div>

👋 I’m Square Dev AI, here to help answer your question!  
Based on the information you’ve provided, the following documentation will help answer your question:

> **[Troubleshoot In-App Payments SDK Problems](https://developer.squareup.com/docs/in-app-payments-sdk/troubleshooting)**
>
> Troubleshoot problems with the Square In-App Payments SDK.

> **[Verify a Buyer](https://developer.squareup.com/docs/in-app-payments-sdk/verify-buyer)**
>
> Learn how to start an SCA buyer verification, get the resulting verification token, and use that token to complete a payment with the Square Payments API.

> **Additional Documentation**
>
> [Verify the Payment](https://developer.squareup.com/docs/get-started/verify-transaction-in-seller-dashboard)  
> [Create a Card on File and a Payment](https://developer.squareup.com/docs/cards-api/walkthrough-seller-card)  
> [Test in the Sandbox](https://developer.squareup.com/docs/devtools/sandbox/testing)

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.  
Otherwise one of our Developer Advocates will provide additional assistance shortly.

---

<div class="post-metadata">

**Author:** ![Square-Dev-AI](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/square-dev-ai/32/2513_2.png) [@Square-Dev-AI](https://developer.squareup.com/forums/u/Square-Dev-AI)\
**Post date:** [August 29, 2024, 3:54pm UTC](https://developer.squareup.com/forums/t/card-declined-verification-required-but-user-not-challenged/18498/3 "2024-08-29T15:54:10Z")

</div>

The error `CARD_DECLINED_VERIFICATION_REQUIRED` typically indicates that Strong Customer Authentication (SCA) is required for the transaction but was not completed. This is common for transactions in regions where SCA is mandated, such as the European Economic Area (EEA).

Since you mentioned that `userChallenged = false` from `verifyBuyer`, it seems like the SCA challenge was not presented to the user. This could be due to the card issuer not requiring a challenge for this particular transaction.

However, the error suggests that the issuer did require SCA. This discrepancy might be due to the specific conditions of the transaction, such as the amount or the risk assessment by the issuer.

To resolve this issue, ensure that your application is correctly handling the SCA flow. This includes calling `verifyBuyer` during the payment process and handling the result correctly. If `userChallenged = false`, your application should be prepared to handle cases where the issuer still requires SCA.

If you continue to experience this issue, it may be helpful to reach out to the card issuer to understand their SCA requirements.

_This answer was reviewed by @Bryan-Square._
