POS Terminal Setting

POS Terminal Setting registers physical terminal devices such as Razorpay POS, Paytm POS, or Pine Labs so staff can collect card/UPI payments in the gym.

What this page is for

POS Terminal Setting registers physical terminal devices such as Razorpay POS, Paytm POS, or Pine Labs so staff can collect card/UPI payments in the gym.

Who should use it

Owner, finance, front desk lead, platform admin

Where to find it

/admin/pos-terminal-settings

Before you start

Register location, gateway account if the provider uses one, device type Payment terminal, provider, device name, code, external device ID, serial number, and active status.
Supported terminal provider choices in the staff app are Razorpay POS, Paytm POS, and Pine Labs.
For Razorpay POS, collect the terminal/device identifier, serial number, linked merchant/account, location mapping, and webhook signature secret. Razorpay callback verification uses the raw callback body and x-razorpay-signature.
For Paytm POS, collect merchant/MID context, terminal id/TID or provider device id, serial number, merchant key/checksum credential, and callback/webhook status from the Paytm POS/business portal. Paytm callback verification accepts CHECKSUMHASH from header or payload when merchant key is configured.
For Pine Labs, collect Plutus terminal id/client id/POS id or cloud integration terminal reference, base serial number where applicable, callback/status-postback setup, and the callback signature secret or adapter token from the Pine Labs portal/API-gateway handoff.
Terminal provider/device readiness means a configured active terminal provider, active device, external device ID, location mapping, callback signature secret or verify token, and at least one verified callback confirmation exist before staff can collect through the terminal.
Operational collection is covered by the POS terminal collection, callback, and reconciliation lifecycle runbook: setup proves the device can be used, while collection proof starts from a SquareOS-created terminal payment and ends only after verified callback or audited Staff app reconciliation updates payment and invoice state.
The external device ID must come from the provider/terminal onboarding portal or device management screen, not from a local nickname printed by staff.
In SquareOS Commerce Device, choose Location or Brand-wide, Linked Razorpay account when relevant, Type Payment terminal, Provider, Name, Code, External device ID, Serial number, Webhook signature secret / merchant key, and Webhook verify token if the provider adapter uses a shared token.
Terminal collection stays disabled until a configured active terminal device exists.
SquareOS terminal callbacks/webhooks must preserve provider transaction ID, terminal device ID, amount, status, and settlement reference for reconciliation.
Current backend contract: terminal webhooks POST /commerce/webhooks/terminals/:provider support Razorpay POS, Paytm POS, and Pine Labs provider names, normalize transaction/order/status fields, match an existing terminal payment, verify callback signature/token against the matched terminal device metadata, and only then update payment status. Unsigned or mismatched callbacks create a failed webhook event and do not reconcile payment.

Daily workflow

In SquareOS, open Admin, POS Terminal Setting, choose Payment terminal, provider Razorpay POS, Paytm POS, or Pine Labs, then enter location, device ID, serial, linked gateway account if required, callback signature secret or verify token, and status.
From POS or Transactions, start a small terminal collection and confirm the terminal receives the request, payment succeeds/fails, and SquareOS updates payment/invoice state from provider confirmation.
Before live exposure, send one real provider callback or certified adapter callback to POST /commerce/webhooks/terminals/:provider and confirm webhookEvent.signatureVerified is true and the pending payment changes state once.
Verify Transactions and Settlements show provider reference, device, gross amount, fees/settlement if available, and audit trail.
Assign the device to the correct gym/location if the brand has multiple locations.
Deactivate lost/replaced devices immediately.

Watch out

Do not reuse one terminal external device ID across locations or devices.

Use the left menu to open related pages in Integrations.
Use Ask Docs for questions that are already covered in this public documentation.