Skip to main content
Production launch is the only part of this guide that can move real money. It requires the Square account owner, an Inventory workspace admin, the intended Square hardware, and the counter operator to work through the same checklist.
A Production payment can incur Square processing fees. Get explicit approval for the seller, location, item, amount, card, operator, and refund owner before creating the checkout. Tuturuuu never runs this test automatically.

​
Launch gates

Do not skip a gate because the Sandbox test passed. Sandbox cannot prove the real seller, physical device, counter network, or receipt behavior.

​
Preflight checklist

​
Square owner

  • Legal business and bank details are complete in Square.
  • The intended selling location, currency, taxes, tips, and receipt settings are correct.
  • The Square application is in Production and authorizes this seller.
  • The owner approves one clearly named low-value test item and exact amount.
  • The owner decides whether and how the test will be refunded afterward.

​
Inventory admin

  • The Payments page shows Production.
  • Application, connection, webhook, and location checks are complete.
  • The selected location matches the owner’s intended counter.
  • The Production webhook has the required seven events and its test delivery returns 2xx.
  • Catalog links, price, currency, tax, and stock are reviewed.
  • The intended Storefront uses Square POS app + Reader or Square Terminal, matching the physical hardware.

​
Counter operator

  • The phone/Reader or standalone Terminal is powered, charged, updated, and ready for receipts.
  • Wi-Fi or Ethernet is stable and does not require a browser sign-in page.
  • A backup connection and Square login are available if the network fails.
  • The operator knows not to retry an uncertain payment.

​
Choose the Production hardware path

Use this path for the customer’s Square POS app, Bluetooth/contactless and chip Reader, or Tap to Pay. The phone never appears in Refresh terminals.
1

Select Phone or tablet with Reader

Open Payments → Connect & set up → Square POS → Edit Square settings → Hardware & POS, choose Production, then select Phone or tablet with Reader.
2

Save the selling location

Select the same Production location currently signed in on Square POS. A location mismatch is rejected by Square and by Tuturuuu verification.
3

Register the exact callback URL

Copy the read-only callback URL from Inventory. In Square Developer Console, open the Production application, choose Point of Sale API, paste it into Web Callback URL, and save. Do not add, remove, or infer a trailing slash.
4

Prepare Square POS

Install or update Square POS on the phone, sign in to the saved location, and connect the Reader or enable Tap to Pay. The displayed phone name and Square device ID are only support evidence; they are not entered into Tuturuuu Terminal routing.
5

Enable the Storefront

Set the Storefront checkout mode to Square POS app + Reader. Open the Storefront on that same phone. When submitted, Tuturuuu opens Square POS with the exact minor-unit amount and card tender selected.
Tuturuuu accepts the callback only when its random request state matches the reserved order. It then retrieves the returned Square Order and Payment and verifies completed status, card tender, location, currency, and exact amount before consuming stock. Cancellation releases the reservation. A missing or unverifiable online transaction ID stays in review and never reduces stock.
Square’s official pairing sequence is documented in Connect a Square Terminal to a POS application.

​
Activate the selling path

  1. In Settings → Members & roles, invite each counter volunteer as POS operator — start payments only. Confirm the one-time preservation of existing member Admin access before sending the first limited invitation.
  2. Open Storefronts in Inventory and select the intended storefront.
  3. Confirm it belongs to the same workspace as the Square connection.
  4. Select the checkout mode matching the hardware: Square POS app + Reader on the same phone, or Square Terminal for the paired standalone device.
  5. Publish only the approved listings and bundles.
  6. Place one non-payment test cart and verify the name, variant, quantity, tax, discount, currency, and total.
  7. Keep Payments → Test & verify, Square Payments, and the physical Terminal visible during the first sale.
For standalone Terminal, the signed-in operator chooses the intended payment station and Tuturuuu verifies its pairing and location before reserving stock and dispatching a Square Order and Terminal checkout. For POS app + Reader, Tuturuuu reserves stock, opens the Square POS app on the same compatible device, and verifies the returned provider records before completion. Never create a replacement order until the existing one is reconciled.

​
Run one controlled live sale

1

Read the approval aloud

Confirm the seller, location, item, quantity, amount, currency, card owner, operator, and refund decision. Stop if any detail differs from the owner’s approval.
2

Record the starting evidence

Write down the product’s available stock, the Tuturuuu time, and the intended total. Open Square Payments before submitting the checkout.
3

Submit exactly once

Submit the Storefront checkout once. Wait for the itemized request on the selected Terminal. Do not double-click, reload into another order, or send a second request while the status is pending.
4

Complete the card-present payment

Use the owner-approved card and follow the Terminal prompts. Capture the printed or digital receipt according to the store’s policy.
5

Match both systems

Compare the amount, currency, location, status, Square order ID, Terminal checkout ID, payment ID, and receipt evidence in Tuturuuu and Square.
6

Verify stock and finance exactly once

The checkout should be completed, its reservation consumed, available stock reduced once, and the finance sale recorded at most once. A duplicate webhook delivery must not repeat any of those changes.
7

Apply the approved refund decision

If the owner planned to reverse the test, use the store’s normal approved Square refund process and reconcile the refund in both systems. Do not make a second charge to offset an uncertain first charge.

​
First-sale evidence

​
Go/no-go decision

The counter is no-go when any of these are true:
  • the Production environment or seller is uncertain;
  • the location, device, price, currency, or tax is wrong;
  • the webhook test is not accepted;
  • the Terminal is offline or shows a different account;
  • the prior checkout is still pending or its payment result is unknown;
  • stock or finance changed more than once;
  • staff do not know who owns reconciliation and refunds.
Follow the troubleshooting guide before accepting another order.

​
Counter handoff message

Copy this into the customer’s Discord channel and replace the brackets:
After launch, give counter staff the operations and verification guide.