Skip to main content

Stripe Split plugin settings

The fixed Dashboard renders Plugin settings from returned key_plugin configuration categories. Historical project evidence recorded Publishable Key, Secret Key, Client ID, matching Sandbox fields, Sandbox, and Stripe Currency; the category schema and implementation are not fixed in Dashboard/API source.

Plugin settings navigation showing Stripe Split without payment values
Payment and credential exclusion

Keys, client/account IDs, currency, sandbox state, allocation rules, balances, transfers, refunds, disputes, fees, wallet/value data, provider responses, and all payment records remain excluded.

Fixed category and mutation boundary​

AllSettings passes returned plugin categories to SettingsMenuOptions; a numeric category opens generic SettingsList. Config edits stage locally and Save persists changed items sequentially; type-5 image configs use an immediate save path.

API-core declares config category/item contracts. Neither source establishes the returned Stripe Split schema, account structure, split rule, validation, payment routing, deployment, persistence, or success. The separate Developers → Plugins manager owns installation/root/iframe actions. No request or mutation ran.

Source-only boundary​

  • /all-settings is level-0 routed; Plugin settings requires returned plugin categories.
  • The retained screenshot is sanitized historical navigation evidence, not current installation or settings proof.
  • No runtime/GET/HEAD, credential, payment/billing/wallet/value/refund, config/image write, plugin-manager action, job, provider, order, or outbound call ran.

Re-entry requires immutable Dashboard/API and Stripe Split serving receipts plus a credential-free synthetic category/payment fixture with all config reads/writes, provider egress, orders, payments, and callbacks intercepted.

Related guides: Plugin settings · Online payments