# Android Mobile Payments SDK Sandbox: “Please re-authorize” on Mock Reader Tap Card, with and without appFeeMoney

**URL:** <https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670>\
**Category:** Questions\
**Tags:** payments-api, sandbox, oauth-api\
**Created:** [November 19, 2026, 9:27am UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670 "2026-11-19T09:27:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Memleak](https://avatars.discourse-cdn.com/v4/letter/m/c68b51/32.png) [@Memleak](https://developer.squareup.com/forums/u/Memleak)\
**Post date:** [November 19, 2026, 9:27am UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/1 "2026-11-19T09:27:09Z")

</div>

Hello Square Forum!

I’m testing a React Native app using Square Mobile Payments SDK for Android in Sandbox with the Mock Reader’s Contactless & Chip option.

Environment

- React Native bridge: mobile-payments-sdk-react-native 2026.10.1
- Android Square Mobile Payments SDK: 2.6.1
- Mock Reader UI: 2.6.1
- Physical Android device; Sandbox application ID and seller/location were verified to match the credentials used for SDK authorization.
- Authorization uses a Sandbox personal access token and the seller’s Sandbox location. I can provide the app and location IDs privately to Square Support. I will not post the access token.

I ran two controlled tests using the same $17.00 USD amount, seller, location, Sandbox account, and Mock Reader. In both tests, immediately before opening the Square payment screen, our native SDK preflight reported AUTHORIZED for the expected location.

Test 1 — application fee included

- Payment amount: $17.00 USD
- appFeeMoney: $0.20 USD
- On “Tap Card,” Square displayed: “Payment failed — Please re-authorize the application.”
- On returning to the app, the callback reported CANCELED / payment\_canceled. In this attempt, the callback details array was empty.
- The native authorization state was then NOT\_AUTHORIZED.

Test 2 — application fee omitted entirely

- Same setup and amount, but the appFeeMoney field was omitted from the request entirely (not set to zero).
- The same Square failure screen appeared on “Tap Card.”
- The callback reported CANCELED / payment\_canceled with details:  
AUTHENTICATION\_ERROR / UNAUTHORIZED — “This request could not be authorized.”
- The native authorization state was then NOT\_AUTHORIZED.

For both attempts, complete read-only Square Sandbox payment searches found no payment. The Developer Console API Logs page showed no payment request or error entry around either attempt, only the GET requests used for our inspections.

The Sandbox token’s reported scopes include PAYMENTS\_WRITE, PAYMENTS\_WRITE\_IN\_PERSON, and PAYMENTS\_WRITE\_ADDITIONAL\_RECIPIENTS. This is a Sandbox personal access token, not a seller OAuth token.

Questions:

1. Can Square inspect its server-side Mobile Payments SDK logs for these attempts and identify why the payment request was unauthorized?
  - Test 1: November 19, 2026, 08:16:46 UTC
  - Test 2: November 19, 2026, 08:51:48 UTC

2. Is a Sandbox personal access token supported for this Android Mobile Payments SDK payment flow when appFeeMoney is omitted?
3. If Square received the request, what was the underlying HTTP status and error? If no request reached Square’s server, what client-side or account configuration would cause this exact failure?
4. Is the SDK expected to transition to NOT\_AUTHORIZED after this payment failure?

I found a related Square Developer Forum report where Square staff identified an INSUFFICIENT\_SCOPES error for app\_fee\_money. However, omitting appFeeMoney entirely did not resolve this failure, so that does not appear to be the sole cause here.

---

<div class="post-metadata">

**Author:** ![Memleak](https://avatars.discourse-cdn.com/v4/letter/m/c68b51/32.png) [@Memleak](https://developer.squareup.com/forums/u/Memleak)\
**Post date:** [November 20, 2026, 7:25pm UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/3 "2026-11-20T19:25:19Z")

</div>

Can Anyone Please Take a look at this?

---

<div class="post-metadata">

**Author:** ![ashley-square](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@ashley-square](https://developer.squareup.com/forums/u/ashley-square)\
**Post date:** [November 20, 2026, 8:02pm UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/4 "2026-11-20T20:02:45Z")

</div>

Yes investigating this now will have an update soon!

---

<div class="post-metadata">

**Author:** ![ashley-square](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@ashley-square](https://developer.squareup.com/forums/u/ashley-square)\
**Post date:** [November 20, 2026, 8:10pm UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/5 "2026-11-20T20:10:57Z")

</div>

A Sandbox personal access token is supported for this flow, as noted in the [Android quickstart](https://developer.squareup.com/docs/mobile-payments-sdk/android#3-authorize-the-mobile-payments-sdk). Your test with `appFeeMoney` omitted also means we shouldn’t assume this is solely an application-fee permission issue.

In React Native plugin `2026.10.1`, calling `authorize()` while the SDK already reports authorized skips authorization rather than applying the newly supplied token and location.

Could you check the following?

1. Was authorization skipped? Did the call return “Already authorized, skipping”? You can answer yes or no, don’t paste the full authorization response, because this plugin version can include your access token in that message.
2. Does a clean authorization reproduce it? Explicitly deauthorize, wait until the authorization observer reports `NOT_AUTHORIZED`, and then authorize again. Retry without `appFeeMoney`, using `ONLINE_ONLY` and a new `paymentAttemptId`.
3. What does the running SDK report? What environment does `getEnvironment()` return, and does `getAuthorizedLocation()` show the expected Sandbox location? No need to publish the location ID.
4. Has this setup ever completed a Sandbox payment? If so, did the behavior start after changing credentials, the Sandbox account, or an SDK/plugin version?

If it still reproduces, could you share the payment and prompt parameter construction code, with identifying information removed? Include any optional fields you set, such as `locationId`, `orderId`, or `allowCardSurcharge`. Don’t include access tokens, authorization headers, or card information.

---

<div class="post-metadata">

**Author:** ![Memleak](https://avatars.discourse-cdn.com/v4/letter/m/c68b51/32.png) [@Memleak](https://developer.squareup.com/forums/u/Memleak)\
**Post date:** [November 20, 2026, 8:58pm UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/6 "2026-11-20T20:58:44Z")

</div>

Thank you SO MUCH for investigating!! We checked the prototype and run notes:

1. The app’s authorization handler calls `authorize()` with `forceFresh: true`. That path deauthorizes, waits for `NOT_AUTHORIZED`, and then authorizes again. The native preflight immediately before each payment reported `AUTHORIZED` for the expected Sandbox location. We did not preserve the exact `authorize()` return text, so I can’t confirm whether it ever displayed “Already authorized, skipping.”

2. The failure reproduced in both controlled attempts, including the attempt with `appFeeMoney` omitted entirely. Both used the same $17.00 amount, seller, location, and Sandbox setup.

3. The recorded run notes do not include `getEnvironment()` output. The authorization preflight did report the expected Sandbox location. The payment parameters were `ONLINE_ONLY`, `allowCardSurcharge: false`, the expected `locationId`, a newly generated `paymentAttemptId`, and a transaction `referenceId`; no `orderId` was set. The prompt used the SDK’s default mode with `TAP_TO_PAY` enabled. The first attempt included a $0.20 `appFeeMoney`; the second omitted that field. We can provide the sanitized construction code if useful. We have not captured `getEnvironment()` yet.

4. These two attempts did not produce a payment, and read-only Sandbox searches found no matching payment. I can’t confirm from the available records whether this Sandbox setup completed a payment before these tests.

Could you correlate the two timestamps against the Mobile Payments SDK logs and tell us whether Square received either request? If received, please share the underlying status and error. If not, please advise what read-only diagnostics would identify why the SDK rejected the request.

We have paused further payment attempts while awaiting your guidance.

---

<div class="post-metadata">

**Author:** ![Memleak](https://avatars.discourse-cdn.com/v4/letter/m/c68b51/32.png) [@Memleak](https://developer.squareup.com/forums/u/Memleak)\
**Post date:** [November 20, 2026, 9:06pm UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/7 "2026-11-20T21:06:48Z")

</div>

Investigating further, I can confirm that this test setup has never produced a successful payment

---

<div class="post-metadata">

**Author:** ![ashley-square](https://avatars.discourse-cdn.com/v4/letter/a/5f9b8f/32.png) [@ashley-square](https://developer.squareup.com/forums/u/ashley-square)\
**Post date:** [November 21, 2026, 2:16pm UTC](https://developer.squareup.com/forums/t/android-mobile-payments-sdk-sandbox-please-re-authorize-on-mock-reader-tap-card-with-and-without-appfeemoney/28670/8 "2026-11-21T14:16:05Z")

</div>

Thanks for checking these details. The deauthorize → `NOT_AUTHORIZED` → authorize sequence makes the authorization-skipping explanation less likely. Knowing this setup has never completed a payment is also useful.

Could you provide:

- The output of `getEnvironment()` and `getSdkVersion()` from the same installed build. These checks don’t require starting another payment.
- The sanitized SDK initialization code, your `forceFresh` authorization wrapper, and the payment/prompt construction code you offered.
- A clarification of how `TAP_TO_PAY` is configured. Were both attempts performed through the Mock Reader’s Contactless & Chip → Tap Card action, rather than the phone’s Tap to Pay flow?

Separately, could you share your Sandbox application ID, Sandbox location ID, and Android package name privately? Include the two `paymentAttemptId` values if they were retained. We already have the UTC timestamps, so there’s no need to repeat the payment attempts to generate new ones.

Those identifiers will let us narrow the log search for the existing attempts. We haven’t yet established which request was rejected or its HTTP status.

Don’t include the access token or the full authorization-success message. This plugin version can include the token in that message.

I’ll send you a DM now so you have a private thread to share details.
