Properties must meet the following location-specific API requirements:

• Default to local for kiosks and other on‑premises workflows that must operate through WAN outages and need predictable lower latency. If your integration already uses a cloud guest‑experience stack (for example, mobile order and pay) and you want to re-use common services, tooling, and release cadence across channels, the cloud kiosk endpoint can be a better option.
• Use cloud for partner integrations, mobile or venue apps, and multi‑site governance.
• Hybrid is an option: transact locally for resilience, orchestrate and report through the cloud.