SS-9171 is a one-time engineering & ops process — validate the full Uber Direct flow end-to-end and pass Uber's certification before production API access is switched on. It's run by the team against a checklist and Uber's own certification portal; there is no operator or merchant screen to build.
What it actually is
Sandbox integration & e2e test. Connection, quotes, create & cancel verified; the full quote → dispatch → completion flow succeeds.
Webhook & lifecycle validation. Status plumbing verified in sandbox; live status updates & the full sequence are sandbox-limited and confirmed against production at cutover.
Uber certification review + findings. Uber reviews the integration (e.g. 11 checks); open findings — control-char sanitization, cancellation-fee handling — are resolved.
Production API approval = go-live gate. Production access unlocks only after certification passes and findings are closed.
Why there's no screen
It runs once, before launch — a checklist the eng/ops team works through, not a surface anyone uses repeatedly.
The state lives where the work is: checks & findings in Uber's certification portal + the team's tracker (Jira / wiki), test results in CI/logs. A bespoke console would just mirror them.
Nothing here is per-merchant or ongoing — rollout is controlled by the Services toggle (SS-9173, off until launch), not a certification screen.
🧪Validated at launch, not sandbox: live delivery-status updates, the full status sequence, real cancellation fees & live courier tracking couldn't be tested in Uber's sandbox (per Phase-0 research) — they're verified against production right after cutover.