Update a payment provider
Renames, enables or disables a payment provider, or replaces its configuration.
A credential sent as <stored secret> keeps the stored one. Enabling validates the settings and credentials with the store, while a disabled provider saves incomplete settings. A payment source keeps its slug. The last update wins.
Guide: Payment providers
Errors
| Status | type | code | When |
|---|---|---|---|
| 400 | invalid_request | invalid_payment_provider_configuration | When enabling a provider whose settings or credentials the store refuses. |
| 409 | conflict | payment_provider_key_taken | When another provider of the project is set up for the same app or account. |
It can also fail with the errors every operation shares, such as unauthenticated; see Errors.
More in Payment providers
Something wrong or missing on this page? Tell us by email or on Discord.