# mosaic_v2-payments-config

_Witnessed 2026-09-04T22:55:13.574Z — QRATE-UAT-1_

_Can the owner of this restaurant see whether card payments are on, and choose which methods are accepted? That is the half of this journey a person can check - the other three steps are assertions about a JSON flag, a 409 and a Stripe client_secret._

**Nothing is saved and nothing is paid.** These fixtures are live Stripe merchants on dev, and toggling a shared fixture's kill switch would also hand the builder a false red on the next canary run.

> **This restaurant's sidebar:** Home · Food Items · Menu · Tables/Staff · Personalize · Insights

### 01 · OWNER

**I expected:** I sign in and look at what this restaurant's own menu offers me

**I saw:** The sidebar offers 6 places to go: Home, Food Items, Menu, Tables/Staff, Personalize, Insights. A Payments entry is NOT there — as this restaurant's owner I am never shown a way to reach payment settings. Dashboard reads: Skip to main content QRate Canary Mosaic V2 Electronic Pay — dev Home Food Items Menu Tables/Staff Personalize Insights C Canary Owner GOOD 

> **The page, word for word:** "Skip to main content QRate Canary Mosaic V2 Electronic Pay — dev Home Food Items Menu Tables/Staff Personalize Insights C Canary Owner In-app card payments aren’t enabled for this restaurant yet."

> **Every control on it that is not the sidebar:** `submit` ""

### 02 · OWNER

**I expected:** I read the payments settings page — the baseline this journey starts from

**I saw:** HTTP 200, header confirms "Canary Mosaic V2 Electronic Pay — dev". It says: "Skip to main content QRate Canary Mosaic V2 Electronic Pay — dev Home Food Items Menu Tables/Staff Personalize Insights C Canary Owner In-app card payments aren’t enabled for this restaurant yet.". Controls beyond the sidebar: 1.

### 03 · OWNER

**I expected:** I look for the accepted-methods control this journey round-trips

**I saw:** STOPPED — There is no control on this page for turning payments on, and none for choosing which methods are accepted. The page is a single sentence and the sidebar. So the owner round-trip this journey asserts is not something an 

> **The same page on four restaurants:**
>
> - **mosaic_v2-electronic-pay** (header "Canary Mosaic V2 Electronic Pay — dev") → "In-app card payments aren’t enabled for this restaurant yet." · controls: submit:
> - **mosaic_v2-split** (header "Canary Mosaic V2 Split — dev") → "In-app card payments aren’t enabled for this restaurant yet." · controls: submit:
> - **canary-mosaic** (header "Canary Mosaic — dev") → "In-app card payments aren’t enabled for this restaurant yet." · controls: submit:
> - **micro-kitchen** (header "Canary Micro Kitchen — dev") → "UPI payment UPI is available for kitchens priced in ₹ INR. This kitchen is set to USD. Change the currency fir" · controls: submit:

### 04 · OWNER

**I expected:** Before I blame the page, I check it is not the same page for every restaurant

**I saw:** The page reads differently across them (2 distinct readings), and the header does follow the restaurant I chose.

---

**Verdict:** STOPPED

**Why it ended here:** There is no control on this page for turning payments on, and none for choosing which methods are accepted. The page is a single sentence and the sidebar. So the owner round-trip this journey asserts is not something an owner can perform.