Skip to main content
PUT

Gateway Credentials Guide

Store and manage payment gateway credentials
If you try to store credentials with an ID that already exists in your user in PCI Booking, the new set of credentials will overwrite the stored ones. This cannot be undone.

Error Responses

Parameter Constraints

  • credentialsId: Required string. Used as the unique identifier for this credential set.
  • Request body: Must be valid JSON containing either a paymentGateway or virtualCardProvider top-level key.
  • Name (inside provider object): Required, non-empty string matching a supported gateway.
  • Credentials (inside provider object): All property names must match the gateway’s expected credential field names (see Retrieve Credential Structure).

Parameters

Headers

Authorization
string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. See the Authentication guide.

Path Parameters

credentialsId
string
required
The unique ID for this set of credentials. You will reference this ID when sending a request through the Universal Payment Gateway.

Request Body

PaymentGateway
object
A custom object specifying the name of the payment gateway and its credentials.

Response