# No per-person code setting

October 21, 2026 · API · Breaking

## What changed

- A person can no longer turn on a code for every order in Layout. A live confirm asks for the 6-digit code only for the other reasons in [When a code is due](https://developer.layout.link/reference/how-it-works#when-a-code-is-due).
- `codeReason` no longer has the value `person_setting`, on a cart or on `code_required`.
- In sandbox, the cart and the `code_required` error at `test_place_code` now say `codeReason: "risk_check"`, where they said `person_setting`. The code is still `000000` and nothing is texted.

## Why it matters

Fewer live confirms need a code. A person whose orders were asking for one only because of that setting now places in one call when no other reason holds.

## What to do

Nothing for live orders. Keep handling `code_required` on every confirm. If you tell the person why a code is needed, you can drop the line for `person_setting`. If a sandbox test checks the reason at `test_place_code`, expect `risk_check`.

## Breaking changes

A test that expects `codeReason: "person_setting"` at `test_place_code` now fails, because the reason there is `risk_check`.