For this migration, you will use the the Kount 360 Salesforce Storefront Reference Architecture (SFRA) cartridge. This cartridge changes the base logic from the int_kount cartridge. The int_kount cartridge was previously used to integrate Command with the Salesforce Commerce Cloud (SFCC).
Workflow changes:
-
The Command RIS endpoint request has been replaced with the Payments Fraud Orders API endpoint.
-
The Kount Event Notification System (ENS) has been replaced with Kount 360 webhooks.
-
When the migration is complete, webhook calls are established from Payments Fraud to your SFCC store. The Kount360-ProcessWebhookQueue job will be periodically executed in order to process event data stored in Payments Fraud.
You must be an existing customer of Equifax and Salesforce. You must have:
-
An active Salesforce Commerce Cloud (SFCC) instance.
-
The Salesforce Storefront Reference Architecture (SFRA).
-
The latest version of the legacy Kount integration cartridges (int_kount). The cartridges must be installed, including all metadata, jobs, and services.
-
An active Kount 360 account and subscription to Payments Fraud.
-
A Kount 360 API key. If you do not have your API key, go to Generate an API Key to create a new one.
Download the latest source code from Github and add it with your existing Kount cartridges in Salesforce.
-
Go to Kount SFCC Cartridge in Github.
-
Download the latest source code from the assets.
-
Open and extract the contents of the source code zip file you downloaded from Github.
-
From the extracted files, add the
int_kount_360_sfracartridge to your Salesforce environment. Go to the Salesforce support site for more information about uploading code to Salesforce.Caution
Do not alter or delete any existing Kount cartridges in your environment. They are required for the data migration.
The new Kount 360 metadata files are in the Salesforce Commerce Cloud Integration folder with the new Kount 360 cartridge (int_kount_360_sfra).
-
Open and extract the contents of the source code zip file you downloaded from Github.
-
Search for the metadata_kount360 folder.
-
Use a file compression tool to create a new file from the metadata_kount360 folder, and then name it metadata.zip.
Note
The naming convention for the .zip file is not required, but recommended for consistency.
-
In your Salesforce instance, open SFCC Business Manager.
-
Go to Administration > Site Development > Site Import & Export, and then select Choose file.
-
Select the metadata.zip file from your local computer, and then select Upload.
-
After the upload is complete, select Import.
You must update the site cartridge path in your Salesforce Commerce Cloud (SFCC) instance to assign the cartridge to your store.
You must create a webhook in Kount 360 to receive event information. For this process, you will need the Website ID value from your Salesforce Cloud Commerce (SFCC) store.
-
In the SFCC Business Manager, select your store.
-
Go to Merchant Tools > Site Preferences > Custom Preferences.
-
Select the Kount Site Preference group.
-
Copy or otherwise note the Website ID value.
-
Go to Managing Webhooks and follow the steps to create a webhook.
Enter the following information during the creation process:
-
For Channel, enter the store Website ID.
-
For URL, enter a URL using the pattern in the following example:
https://{SFCC_STORENAME}/on/demandware.store/Sites-{WEBSITE_ID}-Site/{locale}/Kount360- Webhook
-
Update your site preferences for Payments Fraud. Because the script file only displays the default values, you must update the file manually.
-
In Salesforce, open the SFCC business manager.
-
Go to Merchant Tools > Site Preferences > Custom Site Preference Groups.
-
Select the Payments Fraud in Kount 360 group.
-
Update the following information under Site Preference:
-
Enable Payments Fraud: Enable Kount 360 for your store.
-
Auth Token API Key: Enter your Kount 360 API key.
Note
If you do not have your API key, you will need to generate a new one. For more information, go to Generate an API Key.
-
Enable Webhooks: Enable Kount 360 Webhooks functionality.
-
Webhook Public API Key: Enter the API key used to verify webhook requests. You can copy the public key from Kount 360. For more information, go to Managing Webhooks.
-
Webhook Grace Period: Enter the period of time, in seconds, for which webhook requests are accepted after being sent by Kount 360.
-
Enable Legacy ENS Storage: Disable ENS data processing for Command jobs.
-
You must move to the Sandbox environment first. After we certify your Sandbox instance, move to the production environment in Kount 360 to complete your migration.
Note
These steps apply to both the Sandbox and Production environments.
-
In your Salesforce instance, go to Operations > Services > Service Credentials >kount360.auth.credentials.
-
In the URL field, enter the URL for the authorization server.
Sandbox
https://login-uat.equifax.com/as/token
Production
https://login.equifax.com/as/token
-
Select Save.
-
Return to the Services menu, and then select kount360.api.credentials.
-
In the URL field, enter the URL for the Orders API endpoint.
Sandbox
https://api-sandbox.kount.com/commerce/v2/orders
Production
https://api.kount.com/commerce/v2/orders
-
Select Save.
Note
It might look like a password has been entered in both of these sections. You do not need to enter a password, and can ignore this field.
When migrating to Payments Fraud, some Command object properties are automatically altered to match the new logic from the API. This mapping information is provided so that you can manually change your configuration post-migration if preferred.
There are two types of mapping:
-
Transformational mappings (T): These mappings transform an entire object by using a pre-defined property mapping. This object becomes a new object that then aligns with the new workflow.
-
Custom Values mappings (CV): These mappings transform the values on some object properties by following a predefined value-to-value mapping for each of those properties.
Each custom mapping is defined with a JSON-formatted key-value definition. This definition will depend on the type of mapping.
For T mappings, the key in each definition defines a property for the transformed object. It can be flat ("sku") or nested ("items.[*].price"). The value of the property will specify the source property from the input object.
For CV mappings, the key defines the property for which the mapping will be applied. The value is an object that defines a value-to-value mapping for that property.
Custom mappings are configurable form the int_kount_360_sfra cartridge, which is found in the int_kount_360_sfra/kount360mappings folder.
|
Mapping Name |
Mapping Type |
Description |
|
|
T |
Transforms Kount Command RIS Query object into a format used for the Orders POST API request. Input Object: Kount Command RIS POST request. |
|
|
CV |
Applies custom mappings for the values of the object created by |
|
|
T |
Transforms Kount Command RIS Query object into a format used for the Orders POST API response. Input Object: Kount Command RIS POST response. |
|
|
CV |
Applies custom mappings for the values of the response object created by |
|
|
T |
Transforms a webhook event object to match the Command ENS object structure. Will be stored as an ENS record before being processed by the The Enable Legacy ENS Storage site preference must be enabled to use this mapping. Input Object: Kount 360 Webhook request body. |
|
|
CV |
Applies custom mappings for the values of the webhook event record object created by The Enable Legacy ENS Storage site preference must be enabled to use this mapping. |