Settings control how your Flint integration behaves across checkout, tipping, tax, receipts, inventory, branding, legal, subscriptions, and coupons. The public surface is merchant-scoped for raw reads and writes, while effective settings resolve the full inheritance chain (organization, merchant, location, and device) into the values a given surface actually uses. Pass location_id or device_id to see what applies at that scope; device_id takes precedence and resolves its location automatically.
Settings policies add governance on top: a rule like inherit_only, subset_only, min_bound, or max_bound attached to a scope restricts what descendant scopes can set, never the scope it is attached to. The fees and payment_limits sections appear in reads but are operator-managed and read-only on the public API.
Settings like checkout.enabled_payment_options and checkout.default_expiration_seconds directly shape hosted surfaces; see the Checkout sessions guide and Payment links guide.
