payments_device_display
const url = 'https://example.com/api/payments/v1/devices/display/';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/payments/v1/devices/display/ \ --header 'Authorization: Bearer <token>'Current display state for the device’s station: idle | total | qr | paid. Supports ETag/If-None-Match polling (304 when unchanged). qr_payload renders only on devices declaring the qr_dynamic_present capability.
Authorizations
Section titled “Authorizations”Responses
Section titled “Responses”What a customer-facing display should render right now.
state ∈ idle | total | qr | paid — a stable vocabulary the device
renders verbatim; qr_payload is set only in the qr state and only
for devices whose capabilities include qr_dynamic_present.
object
Examplegenerated
{ "state": "example", "order_display_number": 1, "amount": "example", "currency": "example", "qr_payload": "example", "intent_status": "example", "server_time": "2026-04-15T12:00:00Z"}This deployment cannot store or read protected Handbook content because DJANGO_KNOWLEDGE_CONTENT_KEY is unset or unusable. Answered by the platform exception handler rather than by this endpoint, so any path can return it; retrying does not help until an operator fixes the deployment.
This deployment cannot store or read protected Handbook content because DJANGO_KNOWLEDGE_CONTENT_KEY is unset or unusable. Answered by the platform exception handler rather than by this endpoint, so any path can return it; retrying does not help until an operator fixes the deployment.
object
Example
{ "code": "content_key_missing"}