BlueSage — Back Office

BlueSage Back Office

Internal tool — org & location provisioning, delivery health, signups.

Email

6-digit code (check your email — valid 10 min, this browser only)

Use password instead

Password

Use email code instead

BlueSage · Back Office

Transactions

Click a row for the full drill-down: the signed event payloads exactly as the CRM receives them, the ledger record, and the raw processor response.

	When	Ref	Customer	Job	Type	Channel	Amount	Status

Event deliveries ⬇ Export debug JSON

Latest 15 — click a row to see the delivered payload.

	#	Event	Location	Delivery	Attempts	When

Create organization

One org per CRM customer (e.g. You Move Me). The API key and webhook secret are shown once.

Name Ingestion URL (their events endpoint)

Back-office access (email sign-in)

Email	Added

Add user email

Sign-in codes are single-use, expire in 10 minutes, and only work in the browser that requested them (a relayed/phished code fails). Keep at least two emails on this list — email delivery is the login path. Password sign-in disables automatically while this list is active; the break-glass is ADMIN_FORCE_PASSWORD=1 in the server env + restart (requires server access, by design).

New signup requests

Submitted by the CRM via POST /v1/onboarding-requests as YMM adds organizations/locations. Provision the location, then send back its location_id.

When	Org	Location	Contact	Notes	Status

Device test

This gauntlet proves the terminal is production-ready: connectivity, tap sale with tip, silent voids, pre-auth → above-auth completion, and remote cancel. Follow the highlighted instruction whenever a step is waiting on the terminal. Pennies of live money move and are voided automatically at the end.