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:
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
Is a Sandbox personal access token supported for this Android Mobile Payments SDK payment flow when appFeeMoney is omitted?
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?
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.
A Sandbox personal access token is supported for this flow, as noted in the Android quickstart. 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?
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.
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.
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.
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.
Thank you SO MUCH for investigating!! We checked the prototype and run notes:
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.”
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.
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.
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.