We need help establishing the outcome of one Sandbox CreateOrder attempt. Testing is paused; no payment was attempted.
Endpoint: POST /v2/orders
Square-Version: 2026-09-16
Amount: USD 104.40
Attempt window: October 28, 2026, 16:07:42.830–16:08:49.632 UTC.
We discovered that our code constructed a 43-character reference_id (a 40-character inquiry ID plus “:v3”), exceeding the documented 40-character limit. This was reconstructed from the deployed code, not captured from the outgoing request.
We suspect validation rejection, but our adapter failed to retain the HTTP status, response body, request ID, or specific transport/parsing error. No order ID was saved, so the outcome remains unknown.
We performed one SearchOrders request at 16:49:55.008 UTC for the same location, filtering created_at from 16:00 to 16:20 UTC. There were no state or customer filters; limit was 1000 and return_entries was false.
Our normalized result recorded HTTP 200, no errors, no orders and no cursor. The raw response and request ID were not retained. We do not consider this definitive proof that no order was created.
The original idempotency key is preserved and has not been reused. We have not retried CreateOrder or attempted payment.
Could Square staff please advise:
Can you check the original Sandbox request to confirm rejection or identify any resulting order?
What retention period and scope are guaranteed for CreateOrder idempotency keys, including validation failures?
Is there a read-only way to resolve this outcome? Replaying CreateOrder could create the first order now if the original request failed, which we need to avoid because the accepted proposal has a limited validity period.
Please let us know how to provide the location ID, original idempotency key and other correlation details privately to Square staff.
With your request along with 43-char reference_id, it must have returned HTTP 400, with VALUE_TOO_LONG for reference_id and the detail Field must not be greater than 40 length. That request would be rejected during validation, before order creation.
If you want me to dive deep into your actual request, please share your sandbox app ID, location ID, and original idempotency key in this message. Don’t send access tokens.
Keep the attempt paused. Don’t replay or correct-and-resubmit CreateOrder as a diagnostic since idempotency prevents duplicate creation, but a valid request can create the first order if none exists.
Do you have webhooks configured so that you can receive updates whenever there are updates on the orders? That way, you don’t have to poll but can receive the latest information as it happens.
Thank you, Jaeha, for explaining the reference_id validation and the risk of replaying CreateOrder.
The attempt remains paused. We have not replayed it, submitted a corrected CreateOrder request, or continued to payment.
Please investigate the specific Sandbox SDK CreateOrder attempt on October 28, 2026, within 16:07:42.830–16:08:49.632 UTC, for USD 104.40. This is separate from our earlier Hosted Checkout, which was closed.
The 43-character reference_id was reconstructed from the code. We did not retain the outgoing request or the original HTTP response, status, or request ID. We therefore cannot treat the expected validation error as confirmation of this attempt’s outcome.
Regarding webhooks: the retained sandbox host code had the webhook signature key and notification URL empty, disabling verified webhook processing in that host. We do not have a retained snapshot of the Square Dashboard subscription settings or Square webhook delivery logs for this attempt.
We located the original idempotency key in the archived SDK attempt record and the Location ID in the corresponding code. We also located the Sandbox Application ID retained for this run, although its association with the access token cannot be independently verified from the retained records.
Could you provide a private support channel for these identifiers? We will not post access tokens or secrets.
Please help confirm whether this specific attempt was rejected before order creation, or identify any order it created, without requiring another CreateOrder request.
I searched through our logs and was able to indeed confirm that your sandbox CreateOrder request at October 28, 16:08:23 UTC matching your reported amount and reference-ID pattern. It returned HTTP 400, with VALUE_TOO_LONG for order.reference_id. That logged request was rejected before order creation.
I still need to match your archived original idempotency key and location ID before confirming it was your specific SDK attempt. You can feel free to share the identifiers in this ticket while making sure you don’t share access tokens or secrets. If you prefer more private channels of communication, you can also click on my name box and DM me there too.
The key was recovered from our archived SDK attempt record, version 3. The Location ID comes from the corresponding historical code. Our recorded attempt window is 16:07:42.830–16:08:49.632 UTC on October 28, for USD 104.40. This is separate from our earlier, closed Hosted Checkout.
Could you explicitly confirm that these identifiers match the request you found and that no order was created for this exact attempt? If available, please include its Square request ID.
We have not replayed CreateOrder or continued to payment. The attempt remains Unknown pending your confirmation. No access tokens or secrets are included.
I was able to confirm that both your original idempotency key and location ID exactly match the request I was referring to earlier in my previous response which returned HTTP 400 with VALUE_TOO_LONG for reference_id. No order was created by this exact attempt. You can record its outcome as rejected rather than Unknown.