# Mobile Payments SDK - Pairing Square Reader

**URL:** <https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335>\
**Category:** Questions\
**Tags:** mobile-payments-sdk\
**Created:** [May 15, 2025, 10:54pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335 "2025-05-15T22:54:44Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mauliks](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@Mauliks](https://developer.squareup.com/forums/u/Mauliks)\
**Post date:** [May 15, 2025, 10:54pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/1 "2025-05-15T22:54:44Z")

</div>

Hello,

I am trying to connect the square reader via Bluetooth by as per the doc

```auto
[[SquareManager shared] presentReaderSettingsFromViewController:view completion:^(NSError * _Nullable error)
    {
        if (error)
            NSLog(@"Error presenting reader settings: %@", error.localizedDescription);
        else
            NSLog(@"Reader settings completed.");
    }];

```

But when I click on Pair a reader it gives an error:

 ![image](https://global.discourse-cdn.com/square/original/2X/d/d2c8e9403bde6d1529264d99e9d90b28d9158af0.png)

What I am missing here? In doc: [Pair and Manage Card Readers](https://developer.squareup.com/docs/mobile-payments-sdk/ios/pair-manage-readers) no other info as well.

---

<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:** [May 15, 2025, 10:54pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/2 "2025-05-15T22:54:57Z")

</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:

> **[Configure the Reader SDK on iOS for Square Stand](https://developer.squareup.com/docs/reader-sdk/cookbook/square-stand)**
>
> Configure the Reader SDK on iOS to use Square Stand to swipe payments and to connect a Contactless and Chip Reader using USB.

> **[Build on iOS](https://developer.squareup.com/docs/reader-sdk/build-on-ios)**
>
> Build with the Reader SDK on iOS to process in-person payments with Square hardware.

> **Additional Documentation**
>
> [Connect a Contactless Reader](https://developer.squareup.com/docs/reader-sdk/cookbook/contactless-reader)  
> [Reader SDK](https://developer.squareup.com/docs/reader-sdk/what-it-does)  
> [Reader SDK Quickstart](https://developer.squareup.com/docs/reader-sdk/quickstart-guide)

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:** ![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:** [May 15, 2025, 11:09pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/3 "2025-05-15T23:09:45Z")

</div>

Have you added the [application signature](https://developer.squareup.com/docs/mobile-payments-sdk/ios#application-signature)? Readers won’t connect till the app signature is completed. 🙂

---

<div class="post-metadata">

**Author:** ![Mauliks](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@Mauliks](https://developer.squareup.com/forums/u/Mauliks)\
**Post date:** [May 15, 2025, 11:31pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/4 "2025-05-15T23:31:13Z")

</div>

Yes already added with bundle ID and team ID

 ![image](https://global.discourse-cdn.com/square/original/2X/f/f94c69ffc8b125434f967e78769e9fb0766d5c5f.png)

---

<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:** [May 16, 2025, 3:57pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/5 "2025-05-16T15:57:10Z")

</div>

What’s your application ID and are you physically located in our supported regions? 🙂

---

<div class="post-metadata">

**Author:** ![Mauliks](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@Mauliks](https://developer.squareup.com/forums/u/Mauliks)\
**Post date:** [May 16, 2025, 4:37pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/6 "2025-05-16T16:37:14Z")

</div>

App ID is: sq0idp-NBzAyHIIY3mkV0OsuW8\_AA  
Yes, I am physically located in your supported regions.

I have one more question: If I am in another region, will SDK not allow iPads to connect with readers? I know payment flow will not work, but does pairing also affect it?

---

<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:** [May 16, 2025, 4:40pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/7 "2025-05-16T16:40:16Z")

</div>

Yes, pairing would be effected. 🙂

---

<div class="post-metadata">

**Author:** ![Mauliks](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@Mauliks](https://developer.squareup.com/forums/u/Mauliks)\
**Post date:** [May 16, 2025, 4:49pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/8 "2025-05-16T16:49:20Z")

</div>

So if I am developing outside of USA, Canada or Australia, iPad will not connect with Reader? Are you 100% sure? Because doc says:

- Your Square account is based in the United States, Canada, or Australia. If you’re developing from outside these areas, you can take test payments in the Square Sandbox, but cannot take production payments.

Thing is we have dev teams across the different locations to work. But I am testing within the supported region so far but this is concerning because at least we should be able to test connection with readers n all from out side.

Please let me know 100% if other regions will not work for pairing the readers with devices.

---

<div class="post-metadata">

**Author:** ![Mauliks](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@Mauliks](https://developer.squareup.com/forums/u/Mauliks)\
**Post date:** [May 16, 2025, 6:15pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/9 "2025-05-16T18:15:33Z")

</div>

The pairing issue I fixed now. My app was not asking for Bluetooth permission even though calling the location function. So I now fixed it and can connect the reader to an iOS device.

But I am still curious to know if pairing would work outside of the USA, Canada, or Australia. The previous SDK, Reader SDK, was working outside I mean pairing was working.

---

<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:** [May 16, 2025, 11:55pm UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/10 "2025-05-16T23:55:00Z")

</div>

Glad to hear that you got the app to pair.

As for pairing a reader outside the supported regions its not supported. 🙂

---

<div class="post-metadata">

**Author:** ![Mauliks](https://avatars.discourse-cdn.com/v4/letter/m/96bed5/32.png) [@Mauliks](https://developer.squareup.com/forums/u/Mauliks)\
**Post date:** [May 17, 2025, 12:12am UTC](https://developer.squareup.com/forums/t/mobile-payments-sdk-pairing-square-reader/22335/11 "2025-05-17T00:12:53Z")

</div>

Well, this could be the major issue then for us.
