Credential settings

Discover what they are, what is their purpose, and how to configure your credentials in merchants that do not use the hierarchy logic.

 

With the creation of a merchant, by default, a public and private credential is created and assigned. You can find these credentials within your console in the Developers > Credentials module.

 

What is the purpose of these credentials?

• Public API key: it identifies your merchant in Kushki, and it serves to authenticate your transactions.
• Private API key: it serves to authorize your transactions; so please keep in mind that it should not be shared.

⚠️Important: Please avoid exchanging the Public API key and Private API key between different merchants, as it could create errors when making transactions and issues when creating reports from your Console.

 

Credentials for merchants that do not use the hierarchy logic

🚨 Warning: Keep in mind that the configuration detailed below only applies to merchants that do not use the hierarchy or submerchant logic. Please remember that, for merchants that use the hierarchy logic, this categorization is not used. If you need to know the process to check the credentials of your branch offices or submerchants, please check our available guide on How to check the credentials of my branch offices or submerchants.

There are two credential concepts for merchants that do not use the hierarchy logic, which are: 

1. The master credential, which is assigned to your main merchant. It can only be managed by a Credential Master user. 
2. Secondary credentials are assigned to your affiliate or secondary merchants. These credentials can be created by a Master user. 

ℹ️ Notes: The difference between master credentials, secondary credentials, or other credentials only applies to merchants that do not use hierarchy logic. Meanwhile, for those customer accounts that do use the hierarchy logic, this categorization is not used. The Customer Master user is only available on demand. If you would like to receive more information on how to enable it, please contact us.

 

Steps to create secondary credentials in the Console

⚠️Important: Keep in mind that the configuration detailed below only applies to merchants that do not use the hierarchy or submerchants logic.

To generate secondary credentials for your merchant, you can log in with your master user to the Developers > Credentials module and follow the instructions shown below:

1. On the credentials dashboard, click the Add credential button.
2. Enter a Name for the credential you are creating.
3. Click the Add button.
4. The screen will display a confirmation message, and the new credentials will appear on the dashboard. You will be able to identify them by the name you defined in step 2.

ℹ️ Note You can create or add credentials by using our API. To do this, review our Create a credential endpoint in the documentation.

 

 

Activate, edit, regenerate or delete credentials

In addition of assigning a master credential and creating secondary credentials, you can also:

 

Activate and deactivate credentials

⚠️Important: Keep in mind that the configuration detailed below only applies to merchants that do not use the hierarchy logic.

The needs of your secondary merchants may vary, and from your Administration Console in the Developers > Credentials module, you can activate or deactivate the credentials you use to carry out your transactions.

 

Instructions:

1. In the Credentials dashboard, you will see the list of credentials associated with your merchant. At the far right of each row, the more actions icon will be enabled .
2. Select the Deactivate option for the credential you wish to make inactive. Confirm the action by pressing the Deactivate button in the pop-up box. 
3. To reactivate a disabled credential, press the more options button again and click Activate .

 

ℹ️ Notes When you deactivate a credential, it will appear marked in yellow and its Status will change to Deactivated. You can enable or disable credentials by using our API. To do this, check our Activate or deactivate endpoint.

 

 

Regenerate and edit credentials

⚠️Important: Keep in mind that the configuration detailed below only applies to merchants that do not use the hierarchy or submerchants logic.

When a change of personnel is made in your merchant, the best practice would be to update the credentials with which they integrate into Kushki services. Through the Administration Console in the Developers > Credentials module, you can recreate or renew public and private keys to carry out your merchant transactions securely.

 

Instructions:

1. In the Credentials dashboard, locate the row of a credential and press the more action button
2. To edit the name of a credential, press the Edit alias option. Enter a new name or correct the previous one and press Edit .
3. Choose the Renew key option to reset a credential; then click Regenerate key with the pop-up box.

ℹ️ Notes You can regenerate credentials through our API. For this, check our Regenerate a credential endpoint.

 

 

1. In the Credentials dashboard, locate the row of a credential and press the more action button.
2.  Choose the Remove option.
3. In the pop-up confirmation window,click the Remove button.

ℹ️ Note: You can remove your credentials by using our API. To do this, check our Delete credential endpoint.