Skip to main content
PUT

Payments Library Credentials Guide

Configure credentials for Payments Library integrations
Stores a set of credentials for a digital wallet under the specified ID. You reference this ID in the AllowedeWalletAccountIds field when creating a session.
If you store credentials with an ID that already exists, the new credentials overwrite the existing ones. This cannot be undone.

Error Responses

Parameters

Authentication

API key only. This endpoint does not accept access tokens or session tokens.
string
required
Your API key prefixed with APIKEY. Example: APIKEY your-api-key. The x-pcibooking-api-key header is also accepted. See the Authentication guide.

Path Parameters

string
required
The unique ID to assign to this set of credentials. You reference this ID when creating a Payments Library session.

Request Body

string
required
The digital wallet name (e.g. GooglePay, ApplePay). Retrieve the full list of supported names using the Retrieve Credential Structure endpoint.
The remaining body fields are the credential key-value pairs required for the chosen digital wallet. Retrieve the required fields for each wallet using the Retrieve Credential Structure endpoint. For a CardPay account, only these fields are required: All other CardPay fields are optional. MerchantRequestorIdSuffix, MerchantUrl and ThreeDsBrands are used only when PCI Booking performs 3D Secure, so leave them out if you do not use it.

Response