Update direct payment gateway credentials
Updates only stripe, authorize_net, paypal or qpaypro for the current organization. Fields depend on name. Existing gateway IDs are organization/provider scoped. Empty credentials can remove an existing gateway; direct Stripe writes conflict with a managed Stripe connection or active link attempt. PayPal credentials are verified when both keys are nonblank. Authorize.Net can return an empty HTTP200 body after a successful save. This configures gateways and does not charge a donation. Requires permission: one of access_payment_gateways.
Authorizations
Passport bearer token authentication for legacy admin sessions.
Path Parameters
Direct gateway provider.
stripe, authorize_net, paypal, qpaypro Body
Validated request fields for this operation.
Existing current-organization gateway record ID.
42
Existing current-organization gateway record ID.
42
Existing current-organization gateway record ID.
42
Existing current-organization gateway record ID.
42
Presence enables saving direct Stripe; an empty value may remove the resulting row.
"REDACTED"
Legacy misspelled Stripe private-key field.
"REDACTED"
Stripe publishable key, Authorize.Net transaction key or PayPal client ID, depending on gateway.
"REDACTED"
Authorize.Net API login or PayPal client secret, depending on gateway.
"REDACTED"
Stripe endpoint signing secret.
"REDACTED"
PayPal webhook identifier.
"REDACTED"
Presence enables saving PayPal. Empty public and private keys remove an existing row.
"REDACTED"
Qpaypro login; all three Qpaypro fields are needed to save.
"REDACTED"
Qpaypro API secret.
"REDACTED"
Qpaypro private key.
"REDACTED"
Response
Operation result.
"Settings saved successfully."