We are investigating a start-date mismatch in our Square sandbox integration.
Our saved creation request specifies:
start_date: 2026-11-02
timezone: America/Chicago
monthly_billing_anchor_date: omitted
Square returned:
start_date: 2026-11-03
timezone: America/Chicago
monthly_billing_anchor_date: 2
status: PENDING
No scheduled anchor-change action
A subsequent retrieval returned the same November 3 date.
We reconstructed the request and inspected the SDK’s serialized HTTP body through its underlying before-request callback. It contained November 2 and America/Chicago, with the anchor field omitted. That diagnostic was aborted before sending. We did not capture the original creation request’s final HTTP body, so please verify what Square received in your server logs.
Sandbox API Logs show Payments and Catalog calls but no subscription calls. A direct retrieval returned HTTP 200 with an empty Square-Trace-Id header.
We have scheduled cancellation for this subscription’s November 3 start date and removed its card reference. Our application has blocked recovery finalization and further replacement creation.
Please confirm:
What start_date and timezone did Square receive for this creation?
Why does the stored start_date differ from our requested date?
What is the supported way to create a future monthly subscription starting exactly November 2 in America/Chicago?
Is this behavior related to sandbox processing or this API version?
We do not want to compensate by subtracting a day without understanding the cause.
Thanks for the detailed report. Are you seeing the same behavior in our production? Would you please replicate this in the production and let me know if the issue persists?
I’d love to investigate further if the issue persists. Please share the below with me once you replicate the issue:
We are keeping our testing in sandbox for now. We haven’t verified production behavior, and switching would introduce live billing records.
The issue is currently reproduced only in sandbox. Integration Support already has a ticket. Can you investigate the existing sandbox subscription IDs first? I can send the identifiers privately.
That also works too. We’ve experiencing some behavior discrepancy between sandbox and production, so wanted to understand if you are experiencing the same in prod by any chance.
Please feel free to share the sandbox subscription IDs here. It’s safe to share them as long as you don’t post access tokens, application secrets, authorization headers, or real customer information.
Thanks for sharing the details here. I’ve looked into the sandbox creation logs and confirmed that Square’s subscription service received start_date: "2026-11-02" and timezone: "America/Chicago" while the response returned November 3.
With your specific examples, I’m going to reach out to the relevant team internally and get back to you once I have some findings. Again, thank you for raising this to our attention.