Online payments
Online payments is a historical target whose path and preserved capture do not establish a current category, route, ID, provider, or deployment. Current Dashboard source consumes project-returned categories under /all-settings. Current API source instead catalogs stripe as Card Payments under Basic, not Pro, with six configuration keys: currency, live and test publishable keys, testing mode, and live and test secret keys. That source catalog does not expose values here or prove the category is served.
Returned fields can include credentials, mode, currency, provider, payment, checkout, charge, or refund state. All reads, values, writes, providers, orders, and value-transfer effects are blocked; no security detail is documented.
Audited fixture boundary
The preserved capture is limited to non-secret currency and testing-mode labels from its historical synthetic view.
- It contains no credential values or fields.
- It does not establish a universal provider or field inventory.
- It does not prove mode, currency, account, checkout, charge, or refund behavior.
Current fixed client source only establishes dynamic returned categories and shared config rendering/saving. The accepted and current API catalogs both place stripe under Basic; they conflict with this historical article/fixture's Pro placement. Do not remap the target without a new catalog/mapping receipt.
No category response, config value, provider account, credential, payment, order, or customer record was requested.
The shared source editor stages some changes until Save and persists configurations sequentially; later failure can follow earlier persistence. Image-type fields can write immediately after crop. No config value, credential, media, provider, order, payment, or audit record was read or changed.
Runtime re-entry requires an approved synthetic provider fixture with placeholder credentials, intercepted category/config/media requests, blocked checkout/refund/value paths, and immutable per-effect receipts. A client response alone cannot prove provider or payment success.
Related guides: Pro settings · Settings overview