Corridor pauses without panic pages

Corridors pause for maintenance, compliance holds, or partner incidents. Each cause suggests different shopper messaging, but all need the same structural calm: what is paused, what is not, when to try again.

We draft fallback routes that do not silently switch currencies or tax treatments. If a fallback is not trustworthy, we block with an honest maintenance state instead of clever reroutes.

Telemetry gets explicit events for pause begin and end. Without them, product teams argue from anecdotes weeks later.

Support receives a one-page matrix: symptom, explanation allowed, explanation forbidden, escalation path. That page is versioned like code.