Physical POS
Payment Operations
Retrieve a Payment

Retrieve a Payment

Who calls these endpoints?External API (s2s)
Base path
/api/v1/physical-pos
Identity
Ed25519 request signature on every request — X-Key-Id, X-Date, X-Nonce, X-Signature, plus Digest on requests with a body. ±5 min clock window, single-use nonce. A Bearer token or a panel session is not accepted here.
Authorization
The key must carry the Physical POS product (PHYSICAL_POS) and the scope for the endpoints on this page: physical_pos:view · physical_pos:payments. Without the product the call gets 403 PRODUCT_NOT_ENABLED; without the scope 403 API_INSUFFICIENT_SCOPE. See Authentication and Scopes.
Cross-surface
These endpoints are the s2s surface — call them from your own server with a signed request. The same records have screens in the panel, but panel endpoints cannot be called with an API key, and these endpoints cannot be called with a panel session.

Retrieve a payment

GET /api/v1/physical-pos/payments/{paymentId}

Returns the payment with its items and refund items: { "payment": { … } }. A root or child ID can be used. This endpoint takes no query parameters. A payment that does not exist, belongs to another organization or lives in the other environment gets the same answer: 404 physical_pos.payment.not_found.

To get all reversals of a payment and its timeline in one response: Transactions › Transaction detail.

source lunixi-sign.sh
REQ_PATH="/api/v1/physical-pos/payments/01900000-0000-7000-8000-000000000501"
lunixi_sign GET "$REQ_PATH"
 
curl "https://api-gateway.lunixi.com$REQ_PATH" \
  -H "X-Key-Id: $LUNIXI_KEY_ID" \
  -H "X-Date: $DATE" \
  -H "X-Nonce: $NONCE" \
  -H "X-Signature: $SIGNATURE"
  • Base your decisions on paymentStatus. → Payment statuses
  • On the root, reversalStatus, reversedMinor and pendingReversalId show the combined effect of the reversals.
  • All fields: The Payment Object.