# Japan Sandbox: Bookings API rejects writes with “Merchant subscription does not support write operations”

**URL:** <https://developer.squareup.com/forums/t/japan-sandbox-bookings-api-rejects-writes-with-merchant-subscription-does-not-support-write-operations/28298>\
**Category:** Questions\
**Created:** [October 22, 2026, 2:43pm UTC](https://developer.squareup.com/forums/t/japan-sandbox-bookings-api-rejects-writes-with-merchant-subscription-does-not-support-write-operations/28298 "2026-10-22T14:43:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tomu](https://avatars.discourse-cdn.com/v4/letter/t/7c8e57/32.png) [@tomu](https://developer.squareup.com/forums/u/tomu)\
**Post date:** [October 22, 2026, 2:43pm UTC](https://developer.squareup.com/forums/t/japan-sandbox-bookings-api-rejects-writes-with-merchant-subscription-does-not-support-write-operations/28298/1 "2026-10-22T14:43:45Z")

</div>

Hello Square Developer Support,

I’m testing an integration between an existing flower shop website’s pickup reservation form and Square Appointments in Japan.

The goal is to create a booking in Square from the form submission, linking the customer’s name and phone number and storing order details in the booking notes.

This is Sandbox testing only. I am not trying to process payments or change the production account.

Issue:  
Booking creation fails with HTTP 403 and the message:  
“Merchant subscription does not support write operations.”

The booking configuration also reports:  
support\_seller\_level\_writes: false

I attempted the Square Appointments Plus trial setup in Sandbox, but I have not confirmed that the required subscription entitlement was successfully activated.

Square Customer Support referred me to this developer forum.

Could you please clarify:

1. Are seller-level booking write operations supported for Japanese Sandbox sellers?
2. What exact steps enable the required Plus/Premium entitlement in Sandbox?
3. If support\_seller\_level\_writes remains false after onboarding, how can the account be investigated or corrected?
4. Can this integration be tested entirely in Sandbox without starting a paid production subscription?

Please let me know which sanitized request/response details you need and how to locate the request ID.

Thank you.

---

<div class="post-metadata">

**Author:** ![helner-square](https://avatars.discourse-cdn.com/v4/letter/h/d9b06d/32.png) [@helner-square](https://developer.squareup.com/forums/u/helner-square)\
**Post date:** [October 22, 2026, 8:15pm UTC](https://developer.squareup.com/forums/t/japan-sandbox-bookings-api-rejects-writes-with-merchant-subscription-does-not-support-write-operations/28298/3 "2026-10-22T20:15:52Z")

</div>

Hi @tomu,

Square has a [documented procedure for testing Appointments Plus and Premium in Sandbox](https://developer.squareup.com/docs/bookings-api/onboard-to-the-api#test-integration-with-appointments-plus-or-premium-in-the-sandbox).

1. Are seller-level writes supported for Japanese Sandbox sellers?

Yes

2. How do I enable the Sandbox subscription?

1. Open the Developer Console → Sandbox test accounts.
2. Choose Open beside the test account used by your integration.
3. In that account’s Sandbox Dashboard, open Appointments and complete onboarding if needed.
4. Choose Manage subscription, then select Appointments Plus or Premium.
5. (_Sometimes this does not appear in sandbox_) Add the documented test payment method to prevent the Sandbox subscription from expiring after 30 days:
  - Card number: `4111 1111 1111 1111`
  - CVV: `111`
  - Expiration: `12/40`
  - Name: any test name
  - Postal code: a test value appropriate for your locale

6. Finally, **the most important step** ❗: Make sure you enable **Online Bookings** it is in the Appointements tab. Without this enabled you will still keep seeing the 403 error.

3. What if the flag remains false?

Send me a message here and I can help find a solution or workaround for this

4. Can testing stay entirely in Sandbox?

Yes, this type of testing can stay in Sandbox but there are a few functionalities that do not work in Sandbox, in cases where you reach those limitations you can test using production.

I hope this helps!