Set a store's payment-handler configuration
Enable handlers and supply their processor/gateway parameters. Secret material is write-only (accepted here, never returned). A store cannot pass validation with checkout enabled but no configured handler.
/stores/{store_id}/payment-configAuthorizationBearer token (JWT) · headerrequiredJWT issued by the external IdP via the OAuth 2.0 authorization-code flow (Kinde in
production; a simulator in test). The client obtains it and sends it as a Bearer token on
every authenticated call. Sarvex's services verify it — issuer, audience, signature
(IdP JWKS), expiry — and read identity and tenant from its claims. Sarvex does not issue
or revoke these tokens. merchant_id/store_id are read from the verified claims (and the
merchant→store mapping), never from the URL. The operator scope is required for
/operator/*. Operators acting on a specific merchant pass the X-Operate-As header,
which is recorded in the audit log.
store_idstringrequiredA store the caller's merchant owns. Authorized server-side against the principal; not a free-form tenant selector.
application/jsonhandlersobject[]Show propertiesHide properties
objecthandler_idstringrequiredenabledbooleanrequiredparametersobjectProcessor/gateway parameters; secret fields are write-only and never echoed back.
Updated configuration.
store_idstringhandlersobject[]Show propertiesHide properties
objecthandler_idstringnamestringenabledbooleanconfiguredbooleanAll required parameters/secrets present.
config_statusstringnot_startedincompletereadyRequest body failed validation.
errorobjectrequiredShow propertiesHide properties
codestringrequiredmessagestringrequireddetailsobject | null