Hello Square team,
We are evaluating a merchant-facing inventory/trade-credit integration using
Square OAuth. A merchant would maintain customer credit in a shared backend.
Cashiers would select that customer in ordinary Square POS/Retail, apply a
tracked credit discount, and complete checkout. The backend must reserve credit
before use and settle it exactly once, including concurrent tills and refunds.
We have not enabled this native checkout workflow.
Which supported public API, SDK or approved partner integration can provide the
following contract? Please identify supported US Square products/device modes
and any App Marketplace or partnership prerequisites.
- Before payment, obtain the active native cart/order reference and bind a
one-time credit authorization to the merchant, location, customer, discount
and exact amount. Is there a supported hook that prevents a second till or
offline client from reusing that authorization? - Reliably identify the authorized discount on the final native order. Which
immutable identifiers and applied-money fields are guaranteed? The Order
reference describes version behavior specific to API-created orders; how
should an integration verify finalized native orders that have no version? - Discover fully discounted zero-total native sales and credit-only returns
when no Payment or PaymentRefund is available. Which events or paged queries
provide complete, replayable coverage? The specific order.created reference
and general webhook event table appear to describe different POS coverage. - Reconcile cash/card/Other payments, voids, itemized returns and delayed
offline transmission using authoritative order/discount/return links. Which
lifecycle states and original-sale identifiers should govern credit release
or restoration?
Our requirement is arbitrary-cent customer credit, rather than a configured
loyalty reward tier. If ordinary native POS cannot support the authorization
contract above through the public platform, could you confirm that boundary
and identify any approved partner path? An API-owned checkout would be a
separate workflow decision for the merchant.
Documentation reviewed (reference API version 2026-09-16):
Tax classification will be reviewed separately; this question concerns the
supported authorization and evidence contract. Thank you.