# Supported native POS authorization and order evidence for externally tracked store-credit discounts?

**URL:** <https://developer.squareup.com/forums/t/supported-native-pos-authorization-and-order-evidence-for-externally-tracked-store-credit-discounts/28473>\
**Category:** Questions\
**Created:** [November 5, 2026, 10:17pm UTC](https://developer.squareup.com/forums/t/supported-native-pos-authorization-and-order-evidence-for-externally-tracked-store-credit-discounts/28473 "2026-11-05T22:17:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Thundergames](https://avatars.discourse-cdn.com/v4/letter/t/97f17d/32.png) [@Thundergames](https://developer.squareup.com/forums/u/Thundergames)\
**Post date:** [November 5, 2026, 10:17pm UTC](https://developer.squareup.com/forums/t/supported-native-pos-authorization-and-order-evidence-for-externally-tracked-store-credit-discounts/28473/1 "2026-11-05T22:17:41Z")

</div>

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.

1. 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?
2. 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?
3. 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.
4. 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):

> **[Square Developer](https://developer.squareup.com/reference/square/objects/Order)**

> **[order.created Webhook - Square API Reference](https://developer.squareup.com/reference/square/orders-api/webhooks/order.created)**

Tax classification will be reviewed separately; this question concerns the  
supported authorization and evidence contract. Thank you.