A Paid Square Checkout Is Not Restaurant Acceptance

Square payment and restaurant acceptance are separate outcomes. A customer can complete a payment while the pickup fulfillment still needs attention. If a voice assistant announces “your food is being prepared” solely because a payment succeeded, it may create a promise the restaurant has not made.

Burki's current Square evidence comes from controlled Sandbox work. It demonstrates useful provider behavior but does not establish live restaurant ordering, actual caller checkout, kitchen routing or customer fulfillment.

Read two states, not one

Payment status answers whether the supported payment outcome was recorded. Fulfillment status answers what is known about the order's pickup process. They can change at different times and should be reviewed independently.

Square documents pickup and other fulfillment information in its order fulfillments guide. That separation is a reason to preserve distinct wording in the assistant and staff interface.

A customer-facing status might be “Payment has been received; restaurant acceptance still needs confirmation.” Whether that exact statement is appropriate depends on the current verified results. Do not use it as a default when payment itself remains uncertain.

What the Sandbox evidence actually shows

In controlled provider tests, a simulated payment could complete while the order's pickup fulfillment remained proposed. That is valuable evidence about the distinction between payment and fulfillment. It is not a real customer's meal or a verified restaurant operating process.

The Square setup guide makes this boundary explicit. Browser practice is another level of simulation and does not create a real Square order, payment link or SMS.

When evaluating the feature, ask which layer has been tested: conversation, Burki action, provider Sandbox, production payment or restaurant handling. A successful result at one layer does not silently prove the next.

A hypothetical paid but unaccepted pickup

Imagine a caller selecting a pickup time and completing payment through the hosted page. The restaurant's staff have not yet accepted the order in their operating process.

The assistant should avoid claiming a preparation start, guaranteed ready time or kitchen receipt without evidence. If the caller asks whether they should leave home, the answer must reflect what the business can actually verify.

This hypothetical case is not solved by making the greeting more confident. It requires a defined process for who monitors incoming orders, how acceptance is recorded and what happens when a pickup cannot be fulfilled.

Do not treat link deletion as a refund

Removing or cancelling an unpaid checkout and handling an already-paid order are different operations. Staff need to inspect the current order and payment before deciding what action is appropriate.

The current Burki guide directs paid-order management and refunds to Square. Do not tell a customer they have been refunded merely because a link was removed or a cancellation request returned successfully.

Likewise, an unconfirmed cancellation can leave an unpaid link in a state that still needs review. The team must not assume the customer can no longer pay until the relevant result is established.

Give staff an outcome checklist

For a pickup under review, identify the exact checkout and order, read the latest payment result, read the fulfillment result and confirm the restaurant's next action. Record who checked it and how the customer should be informed.

Keep older creation responses separate from current status. A response captured when the link was created may still describe an unpaid draft even after a later payment. Staff should use the supported current-status path for operational decisions.

The restaurant voice-assistant page can help frame a buyer discussion, but the merchant's actual acceptance process determines whether the workflow is useful.

Before considering live restaurant use, walk through one unpaid, one paid and one uncertain example with the people responsible for fulfillment. Ask what they can truthfully tell the caller at each point. If payment is the only status anyone can inspect, the workflow is not yet sufficient to promise an accepted pickup.