We are planning a daytime takeout shop and an evening dine-in izakaya at the same premises in Japan. We are evaluating our own ordering and table-bill system, with Square for payments, receipts, the kitchen display and cash management. Before we start building, we would like to confirm the following for Japan production. Answers to any part would be very helpful.
What we want to do
- At the izakaya, guests scan a QR code at their table and place several rounds of orders from their own phones. They pay once when they leave, at the counter. This is the usual way to pay at an izakaya in Japan.
- Square Online QR ordering in Japan takes payment for each order, and we have not found documentation confirming that open tabs are available in Japan. So we plan to keep the table’s orders in our own system and use Square for the payment.
- We have read the recent answers in forum topics 28608 and 28269: unpaid API orders reach Square POS, KDS and printers only after they are paid, an app cannot add items to a check opened in Square POS, and the supported way to collect payment for an API order on hardware is a Terminal API checkout that references the order_id.
- So at checkout, we plan to create an itemized order for the whole table with the Orders API and send a Terminal checkout with that order_id to a Square Terminal at the counter.
- Groups often split the bill. At one table, some guests pay by card, some by e-money or PayPay, and some in cash, and some guests pay their share and leave before the others. The rest of the table may order more after that. Guests also often ask for a formal receipt (ryoshusho) addressed to their company. Receipts need to work as simplified qualified invoices in Japan.
- Some reservations include a deposit that the guest pays in advance online. It must be applied to the table bill at checkout.
- Each round of orders must reach the kitchen (Square KDS) as soon as it is placed, long before the table pays, without counting the items twice in sales or showing them twice in the kitchen.
Our main questions are whether this payment and receipt workflow is supported in Japan, and how to send kitchen tickets before payment.
A. Itemized checkout, split payments, deposits and receipts
- Formal receipts. The Develop for Japan guide (Develop for Japan) says for the itemized approach: “Formal receipts are not currently supported - only normal receipts can be printed.” The Take Payments for Orders guide (Take Payments for Orders) says: “For Square accounts in Japan, the Square Terminal prints both a standard receipt and a formal receipt called ryoshusho (領収書).” Which statement applies to an itemized Terminal checkout with an order_id in Japan? Guests often ask for a ryoshusho addressed to their company. For an API-created order, how is the recipient name entered, and is it printed on the ryoshusho?
- Split payments with mixed payment methods. We understand the documented split-tender flow: partial Terminal checkouts with checkout.payment_options.autocomplete=false against one order_id, plus cash recorded with CreatePayment (autocomplete=false), completed together with PayOrder (shown as Beta). The guide says: “Split tenders are available in regions that support order IDs for checkouts.” In Japan, we select the payment method using checkout.payment_type: CARD_PRESENT for card payments, one of the
FELICA_*values for e-money, or QR_CODE for QR-code payments such as PayPay (as explained in forum topic 28116). The PaymentOptions reference says that delay_duration “is only supported for card payments”. CanFELICA_*and QR_CODE (PayPay) checkouts be created with checkout.payment_options.autocomplete=false against an order_id, and completed through PayOrder together with card and cash payments? If not, what workflow do you recommend for splitting a table bill while keeping itemized receipts? - Receipt content. We need the printed receipt to show the seller’s invoice registration number, totals and tax amounts by tax rate, and reduced-rate item indicators where applicable. Are these supported for API-created orders, including cash-only payments and split payments? Which API fields or seller settings control them?
- Receipts during a split. Some guests pay their share and leave before the others. What document can Square Terminal issue while that guest’s payment is still APPROVED, before PayOrder? After PayOrder, does a RECEIPT Terminal action show that payment’s amount, the full order total, or both? To print an itemized receipt for the whole order, which payment_id should we pass?
- Adding or removing items after some guests have paid. After one guest has paid their share, the rest of the table may order another round, or a dish may be canceled. In forum topic 9596, a Square team member described this sequence: create an order, take a payment against it with autocomplete=false, add a line item with UpdateOrder, take another payment for the additional amount, and complete the payments with PayOrder. Does this also work in Japan when the payments are created through Terminal checkouts with checkout.payment_options.autocomplete=false? Assume the earlier Terminal checkouts are COMPLETED, their Payments remain APPROVED, the order remains OPEN, and no checkout is pending or in progress. Can UpdateOrder add items, reduce quantities, or remove items while retaining those approved payments? Does the answer change if the revised order total falls below the sum of the approved payment amounts? If an update is not supported, what workflow do you recommend?
- Reservation deposits. For some reservations, the guest pays a deposit in advance through a Checkout API payment link, which creates its own paid order. At the table checkout, we need to apply that deposit to the table’s itemized order. The receipt should show the total for the whole table, the deposit applied, the amount paid now, and the tax amounts by tax rate for the whole table. In forum topics 8945 and 10253 (2023), a Square team member said that applying an already paid order to another order is not available, and suggested an order-level discount, or a separate order for the deposit linked through reference_id, metadata or custom attributes. The deposit is an advance payment toward the meal, not a price reduction. According to the Order Calculation Guide for Japan, a tax-basis-reducing discount would cause Square to calculate tax on the discounted amount. Using such a discount to represent the deposit would therefore reduce the tax shown for the table order, whereas we need the receipt to show tax on the full meal amount. Is a catalog discount with modify_tax_basis set to DO_NOT_MODIFY_TAX_BASIS supported for orders in Japan, and how would it appear on the Terminal receipt and in sales reports? Is there a better supported way to apply a deposit in Japan?
B. Kitchen tickets on Square KDS before payment
Why we ask: the kitchen needs each round of orders right away, but the table pays only at the end. From forum topic 28028, we understand that paying a zero-total order with PayOrder and an empty payment_ids array is supported, that such an order is expected to route to KDS, and that ad hoc items are treated as uncategorized on KDS.
- Can you confirm that this workflow is supported for Square KDS in Japan production? For dine-in kitchen tickets, is a PICKUP fulfillment appropriate for these zero-total orders when IN_STORE (a restricted Beta) is not available to us? Should we use zero-priced ad hoc line items, or catalog items with a 100% discount? How would each choice affect item sales, quantities and discount reports, given that the same items are sold again in the final paid order?
- Which of ticket_name (shown as Beta),
line_items[].noteandfulfillments[].pickup_details.noteappear on the KDS ticket? We want the kitchen to see the table number. - To avoid sending the final billing order to the kitchen again, can we omit fulfillments from the billing order while keeping Terminal itemization and receipts? Would that prevent a second KDS ticket?
- If a guest cancels one line item in a multi-item zero-total order already displayed on KDS, can an API update remove or mark only that item as canceled while leaving the remaining items active? Forum topic 27132 says a scheduled print cannot be suppressed once a paid fulfillment is canceled. If an API update cannot do this, is a separate cancellation ticket identifying the original order and the canceled item the recommended workaround for KDS?
- For these API-created zero-total PICKUP orders, does completing a ticket on a Prep station or an Expeditor station update the fulfillment state exposed by the Orders API? If so, which state transitions occur, and which webhook events are emitted?
C. Cash drawer
Why we ask: we plan to use Square POS cash management as the record of the counter’s cash, and reconcile it with the cash that our system records for table bills.
- Is the Cash Drawer Shifts API available for Japan accounts? For a Japan location, does a CreatePayment request with source_id=CASH, later completed through PayOrder, count toward cash_payment_money or expected_cash_money in an open Square POS cash drawer shift at the same location? An existing answer in forum topic 26374 says that API payments are not expected to appear in the cash drawer. Does that also apply to this cash-payment flow?
D. Scheduled pickup orders (the takeout shop)
Why we ask: the daytime takeout shop takes pre-orders paid online through a Checkout API payment link. The kitchen should see each order only when it is time to prepare it.
- The Order Fulfillments guide says a scheduled order does not show up on a KDS “until pickup time minus prep time.” We will set schedule_type=SCHEDULED, pickup_at, and prep_time_duration. Assuming payment completes before the preparation window and staff do not manually advance the order, are there any exceptions or additional settings required to keep these CreatePaymentLink orders off KDS until pickup_at minus prep_time_duration in Japan?
E. Storing a card for no-show fees (reservations)
Why we ask: for reservations, we want to save a guest’s card without charging it, and charge an agreed no-show fee later if the guest does not come.
- We plan to save a card using the documented intent=STORE → CreateCard flow (also mentioned for a Japan seller in forum topic 28507), and later charge the agreed no-show fee with CreatePayment as a seller-initiated payment. Are there any Japan-specific requirements or limitations for charging a no-show fee this way? The Web Payments SDK reports from Japan production in forum topics 28329 (CHARGE and CHARGE_AND_STORE) and 28461 do not report a STORE test. Has Square confirmed whether STORE is affected?
Thank you.