Skip to main content

XTMS Device Binding Evidence

Use scripts/xtms-device-binding-evidence.sh to capture the operational evidence package for a NexGO/card-present device-binding check.

Required evidence:

  • Mapping candidate lookup for the target serial.
  • Bind request and bind response for the target location, serial, and terminal ID.
  • Post-bind lookup response showing the device state.
  • Operator note identifying the XTMS credential, profile, and app-version set used for the run.

The script writes timestamped JSON files under tmp/xtms-device-binding-evidence by default and prints a summary with HTTP statuses. A PENDING_CLOUD_SYNC bind response is acceptable only when CARD_PRESENT_DEVICES_NEXGO_CLOUD_BINDING_REQUIRED=false. When cloud binding is required, evidence must show BOUND / synced cloud state.

Command​

GATEWAY_API_BASE_URL=https://api.peakgateway.co \
GATEWAY_BEARER_TOKEN=... \
LOCATION_ID=loc_... \
NEXGO_SERIAL=... \
TERMINAL_ID=... \
./scripts/xtms-device-binding-evidence.sh

Optional variables:

  • MERCHANT_NAME: display name used in the bind request.
  • EASY_DEPLOY_TEMPLATE_ID: XTMS Easy Deploy template to include in the bind request.
  • OUTPUT_DIR: evidence output directory. Defaults to tmp/xtms-device-binding-evidence.

Evidence handling​

Treat device-binding output as operational evidence. Store the generated files in an approved evidence location and summarize statuses in issue or PR discussion instead of pasting raw device/provisioning payloads into chat.