Merchant Configuration Callbacks

Configure your merchant instantly!

As you move from validating your integration, to boarding merchants, you should determine how you want to receive and configure your merchant’s API and public keys.

The easiest, most secure and reliable way is for the Clearent system to send them directly to your system. This removes human mistakes (i.e: copy and paste errors) . All you need to do is stand up an SSL endpoint and be able to accept the below payload. Then take the keys for each merchant account and push them into your system.

Expected Payload

Example of callback using single product


{
    "externalIdentifier": "Unique identifier given from Partner",
    "merchantAccountNumber": "Merchant Number",
    "keys": [
        {
            "type": "cnp",
            "productName": "Your Product Name- CNP",
            "apiKey": "Your Merchant's Card Not Present API Key",
            "terminalId": "11111234",
            "publicKey": "Your Merchant's Card Not Present Public Key"
        }
    ]
}

Example of callback using multiple products


{
    "externalIdentifier": "Unique identifier given from Partner",
    "merchantAccountNumber": "Merchant Number",
    "keys": [
        {
            "type": "cnp",
            "productName": "Your Product Name- CNP",
            "apiKey": "Your Merchant's Card Not Present API Key",
            "terminalId": "11111234",
            "publicKey": "Your Merchant's Card Not Present Public Key"
        },
        {
            "type": "cp",
            "productName": "Your Product Name- CP",
            "apiKey": "Your Merchant's Card Present API Key",
            "terminalId": "11111234",
            "publicKey": "Your Merchant's Card Present Public Key"
        }
    ]
}