GET Mobile Pay Token

​

Looks a token up by its hash.

An unknown hash is not a 404: the response is 200 with mobile_pay_token set to null. Check for null rather than relying on the status code.

This returns the token whatever its state, including expired and already-redeemed ones, so check status and expires_at before acting on it.

Path Parameters

  • Venue ID

  • The token hash, as scanned from the QR code

Headers

  • Type of content accepted by the API (application/json in most cases)

  • Application key for specific client app

  • Version of the API to be used

  • Authorization header

  • Unique request identifier

Responses

  • application/json
  • Missing or invalid customer token.

  • The brand is not on the NMG product structure.

  • Unknown venue.

Request Example for get/venues/{venue_id}/mobile-pay-tokens/{hash}
curl 'https://api-public-demo.menu.app/api/venues/{venue_id}/mobile-pay-tokens/7c9e6679f1e4d0b3a2c5e8f1a0b9d4c3' \
  --header 'Accept: application/json' \
  --header 'Application: application-key' \
  --header 'API-VERSION: ' \
  --header 'X-Request-ID: c10b4a70-6274-490d-80a0-03e7bb826937'
{
  "status": "OK",
  "code": 200,
  "data": {
    "mobile_pay_token": {
      "id": 501,
      "hash": "7c9e6679f1e4d0b3a2c5e8f1a0b9d4c3",
      "venue_id": 12,
      "status": "pending",
      "expires_at": "2026-09-19T12:05:00.000000Z"
    }
  }
}