Payment Credentials lets you programmatically manage the API key pairs associated with your merchant account. You can create additional credentials for different integrations or locations, search existing ones, activate or deactivate them, update their metadata, and regenerate their keys if they are compromised.
Master credential required
All endpoints in this section require a master credential (Credential Master user). This role is available on demand — contact your Kushki account manager to enable it.
The response returns a data array and a total count.
Advanced Search
Searches credentials by keyword across their fields (alias, IDs). Useful for finding a specific credential quickly.Request fields:
Field
Description
searchTerm
Keyword to search across credential fields
merchantId
Restrict results to a specific merchant ID
Activate or Deactivate
Enables or disables a credential identified by its credentialId (path parameter).Request body:
Field
Required
Values
action
✅
"ACTIVATE" or "DEACTIVATE"
Deactivated credentials immediately stop accepting API requests. Reactivate them at any time with "ACTIVATE".
Update a Credential
Updates the alias or metadata of an existing credential. The credential ID is passed as a path parameter.Request fields:
Field
Required
Description
merchantId
✅
Your merchant ID
alias
New human-readable label
metadata
Updated metadata object
Regenerate a Credential
Generates new public and private keys for a credential identified by its public_credential_id (path parameter).
⚠️ The old keys are immediately invalidated. All integrations using the old keys will stop working. The new keys replace the old ones automatically wherever the credential is referenced in Kushki's system.
Use this endpoint if a credential is compromised or you want to rotate keys as a security measure.
Delete a Credential
Permanently deletes a credential. The credentialId is passed as a path parameter.
⚠️ Deletion is irreversible. Any integration using the deleted credential will immediately stop working.