Gateway defaults and managed credential sets
Provider accounts the platform owns, applying them to workspaces, key rotation without downtime, and the Authorize.net limit.
Gateway defaults. Super → Settings → Gateway defaults holds provider accounts the platform owns.
- Keys only: a default stores the API keys, sealed. Webhook values belong to each workspace, because each workspace registers its own endpoint.
- Lifecycle: Draft until Verify makes one authenticated call to the provider; then Verified.
Applying a default. On a workspace's Manage gateways page, choose From a default.
- This creates a credential set in that workspace with the default's keys, re-sealed under the workspace's binding. The set is marked managed and linked to the default.
- Paste the provider's webhook value for the workspace endpoint (the URL is shown on the set). Then verify and put the set in service, as usual.
- Enter keys creates a managed set without a default.
Managed sets in the workspace:
- Members can bind them to products.
- Only the super admin can edit, verify, activate, disable or enable them. Members see a "managed by the platform" note instead of the edit forms.
- On a set linked to a default, the super admin edits only the label and the webhook value; the keys come from the default.
Key rotation:
- Edit the default's keys. The default goes back to Draft, and linked sets keep the old keys and stay in service.
- Verify the default. The new keys are copied to every linked set (audited as
credential_set.keys_propagated), and their status is kept: no downtime.
Limits:
- Authorize.net: a default can serve one workspace only, because Authorize.net webhooks are matched to a set by the account Signature Key.
- Deleting a default: refused while workspace sets still use it.
Workspace setting. On the workspace page, Platform-managed stops the workspace's own members from adding credential sets. Sets the super admin adds work either way.
A gateway default is a provider account the platform owns: payments made through it arrive in the platform's account. To let workspaces use their own accounts without copying keys, see Connected accounts and Super → Platform apps.
Credential sets of a workspace#
On a workspace's Manage gateways page you see every set of that workspace, with its status. You can add a managed set from a default or by entering keys, and for managed sets you edit the label and webhook value, verify, put in service, disable and enable. Sets the workspace added itself are read-only for you, so a workspace's own provider accounts stay under its control.
Text description
A credential set starts as Draft. Verify makes one authenticated call to the provider; when it succeeds the set is Verified. Put in service needs the webhook value too and makes the set Test or Live, depending on its environment. A set can be disabled by hand, or automatically after three provider authentication failures in a row (the owners are emailed), and enabled again.