# Issues with store card using SCA

**URL:** <https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290>\
**Category:** Questions\
**Created:** [January 20, 2023, 5:43pm UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290 "2023-01-20T17:43:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![raZaSat](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@raZaSat](https://developer.squareup.com/forums/u/raZaSat)\
**Post date:** [January 20, 2023, 5:43pm UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290/1 "2023-01-20T17:43:13Z")

</div>

1. Getting customers complaints about inability to save cards.  
– The Visa, Mastercard verification page shows up without any challenge and closes. But the card does not get stored to file on Square account.  
– For one of the UK banks - Santander, the verification flow does not complete. Even after the customer has authorised, the verification flow shows message “Please provide a response to the challenge before proceeding”.  
– Customers reporting time out errors when trying to add card.

We have integrated the React-Native-in-app SDK in our mobile app. [in-app-payments-react-native-plugin/get-started.md at master · square/in-app-payments-react-native-plugin · GitHub](https://github.com/square/in-app-payments-react-native-plugin/blob/master/docs/get-started.md)

We use “react-native-square-in-app-payments” SDK version 1.7.2.

Are there known issues with the react native SDK?

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [January 20, 2023, 6:39pm UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290/2 "2023-01-20T18:39:51Z")

</div>

What are the location\_ids, application\_id , time/date of errors? 🙂

---

<div class="post-metadata">

**Author:** ![raZaSat](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@raZaSat](https://developer.squareup.com/forums/u/raZaSat)\
**Post date:** [January 20, 2023, 10:38pm UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290/3 "2023-01-20T22:38:19Z")

</div>

The latest of the issues where the Mastercard - Verification page shows up but closes without allowing user action, happened at -20 Jan 2023 16:43 GMT.

Around that time we were able to replicate the issue consistently.

The user was using iPhone 13 with latest iOS on 5g network.

Application id: sq0idp-o0N6k8PPRX5F8KexhSwhBw  
Location id: LJP3SPSYJ7VB9

---

<div class="post-metadata">

**Author:** ![Bryan-Square](https://sea1.discourse-cdn.com/square/forums/user_avatar/developer.squareup.com/bryan-square/32/38_2.png) [@Bryan-Square](https://developer.squareup.com/forums/u/Bryan-Square)\
**Post date:** [January 21, 2023, 12:31am UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290/4 "2023-01-21T00:31:13Z")

</div>

Do you get a verification failure message? Any logs? 🙂

---

<div class="post-metadata">

**Author:** ![raZaSat](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@raZaSat](https://developer.squareup.com/forums/u/raZaSat)\
**Post date:** [January 21, 2023, 6:35am UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290/5 "2023-01-21T06:35:13Z")

</div>

We are not logging the verification logs in current version of our app. Hoping the error messages are shown on the verification screens. On Sandbox we had verified the process by using the test cards.

---

<div class="post-metadata">

**Author:** ![josh-square](https://avatars.discourse-cdn.com/v4/letter/j/77aa72/32.png) [@josh-square](https://developer.squareup.com/forums/u/josh-square)\
**Post date:** [January 23, 2023, 7:11pm UTC](https://developer.squareup.com/forums/t/issues-with-store-card-using-sca/8290/6 "2023-01-23T19:11:19Z")

</div>

Hey @raZaSat! No worries, we were able to find the error message based on the timestamp. The team’s still digging into this, but we’ll update you as soon as we know more.
