SS-9161 is a platform-level backend integration, not an operator-facing page. One central INFI-owned Uber Direct account powers delivery for every merchant; its credentials live in backend config and the access token refreshes on a server schedule. There is nothing for an operator to configure or click — so we deliberately build no console for it.
What it actually is
One central account. INFI is the single Uber Direct account holder for all merchants — Production.
Credentials in backend config. The access token (~30-day validity) is stored server-side and auto-refreshed by a background job — no merchant or operator action.
Pickup = the INFI location address, sent to Uber on each delivery. No Uber store is created and there is no store matching.
Merchants never sign up with Uber. No per-merchant Uber onboarding, no accounts to connect.
Why there's no screen
Nothing is configured per merchant here — enabling delivery for a merchant is the Services toggle (SS-9173). This connection is shared infrastructure: one link, all merchants, no list and no per-row action.
The token lives in secrets and a refresh job, not an operator form — surfacing it as an editable screen adds risk, not value.
Connection health is already covered by Monitoring (SS-9172) — a dedicated "connection console" would just duplicate it.
⚠️Failure behavior (automatic, no page): if the connection is ever unavailable, delivery is shown as unavailable at checkout and resumes once it's restored — handled in the checkout & monitoring flows above, not by a dedicated screen.