Stripe Connect
The fixed Dashboard mounts /stripe-connect for level 0 only when addon_stripe_connect is true or configuration is still loading. Its My addons item has separate level-0, non-read-only, availability, and add-on gates.
This surface sits next to payment-routing and store-commission configuration. It can expose provider-sensitive values and persistent configuration writes; no page, category, connection, credential, payment, or provider action was opened for this guide.
Review available categories
The page requests categories whose key is addon_stripe_connect, then renders the returned records through the generic settings UI. A selection writes ?category={id} to client history; IDs, fields, descriptions, and values are runtime data, not fixed-source inventory.
The page does not establish a generic set of OAuth or credential fields. Review the specific, approved test-project configuration before documenting or changing it.
Source-verified request and write boundary
The category request and subsequent config reads are authenticated. Category records are administrator-only in the inspected API source. Generic settings edits are buffered in the client until Save, then submitted one config at a time; partial completion is possible if a later update fails. Accepted updates can create audit-log records, refresh global config state, and run plugin hooks.
Those contracts do not prove the returned Stripe category, a connected account, OAuth availability, commission behavior, or deployed payment routing. The separate store payment-method flow contains provider connection and credential persistence behavior; it is not copied into this category guide.
Keep sensitive data out of captures
Do not capture or disclose provider credentials, connected-account identifiers, webhook destinations, payment data, or live settings values. The retained image is an existing sanitized category-list capture; it was not replaced or refreshed.
For commission-related store configuration, use the applicable store payment-method workflow with the same approval and test-data safeguards.
Troubleshooting
If the menu item is absent, the level, read-only state, add-on availability, and add-on flag are separate checks. A direct route, empty list, or visible category does not prove entitlement, billing state, provider connection, safe credentials, or deployed behavior. Re-entry requires immutable serving receipts and a synthetic, credential-free category fixture with config writes and provider egress blocked.
Related guides: Add-ons overview · Apps & Addons catalog · Store payment methods