POSTReviewedv1

Initiate a Menu payment with LuxPay

LuxPay owns transaction and settlement state. Consumers need idempotency and a stable order reference, and a successful redirect is never final payment proof.

POSThttps://api.lux.foodtech-pos.com/v1/menu/payments/initiate

Contract state: Reviewed

A path is not a production contract until it is marked verified and matches the runtime source.

Authentication

AuthenticationApproved Menu platform client credential

Required scopeplatform-client · customer · order

Environmenthttps://api.lux.foodtech-pos.com

Last reviewedJuly 16, 2026

Headers

AuthorizationRequired

Partner credential; exact scheme is contract-bound.

Idempotency-KeyRequired

One stable key per logical payment initiation.

Request example

amount, currency, order reference, and return URL must be certified from schema before use.

{
  "order_reference": "<stable-order-reference>",
  "amount": "<minor-units-or-certified-format>",
  "currency": "<ISO-4217>",
  "return_url": "<registered-https-url>"
}

Response example

The final result exposes an opaque transaction identifier and verifiable state; field names await source certification.

{
  "transaction_id": "<opaque-id>",
  "status": "<created-or-pending>",
  "redirect_url": "<verified-luxpay-url>"
}