Provide comprehensive security for your Magento or Adobe Commerce Cloud transactions by using Kount 360.
Note
The instructions in this document are demonstrated using Magento, but they apply to both Magento and Adobe Commerce Cloud.
IMPORTANT!: If you are migrating from Command and have previously configured webhooks, make sure you complete the Customize Webhooks in Kount 360 step after installing Kount 360.
In Kount 360, after you have been invited to an organization and your client is initialized, you can generate API keys to send data securely to Kount. You must have an initialized client before you can create an API key.
Note
Only users with the Owner role permissions can generate, delete, or edit API keys.
-
Sign in to Kount 360. There are two integration environments: sandbox and production. Only integrate into our sandbox environment if you are integrating a pre-production environment without production data for testing.
-
Select Admin, then Product Configuration.
-
In System Settings, select API Keys.
All initialized clients display.
-
For the client you want to create an API key for, select Generate API Key.
The new API key is generated. A prompt displays with the ability to copy the API key and add a description.
-
Copy the API key and store it in a secure location.
Note
The API key is not provided again. You must store it in a secure location for future reference. If the API key is compromised or lost, create a new API key and delete the the compromised one.
-
Enter a description detailing the store used for the API key, then select Confirm.
API keys are organized under each client on the API Keys page. Expand the client to view your API keys, the descriptions, and when client details were created.
Create a Composer script to install Kount 360 in your Magento environment. Before beginning installation, enable logging to help troubleshoot any potential issues.
Note
Go to Magento 2 System Requirements and the GitHub repository for supplemental information to complete the following steps.
From the root directory of your Magento installation, enter the following commands to install Kount 360:
composer require kount/magento2-kount360 php bin/magento module:enable Kount_Kount360 php bin/magento setup:upgrade
Configure Kount 360 in Magento Store Configuration. You must have admin access to view and configure.
-
Sign in to Magento.
-
Select Stores, then Configuration.
-
In Configuration, select Kount 360.
-
For the Enabled setting, select Yes to activate Kount 360 for you store.
-
Select and configure the following sections.
-
Account Information
-
Environment: Select TEST or PRODUCTION. This setting determines to which Kount environment the Magento instance is posting data.
Note
TEST refers to the Kount 360 sandbox environment and PRODUCTION refers to the Kount 360 production environment.
-
Client ID: Enter the client ID you have in Kount 360 for production or test, depending on which selection you made for Environments.
-
API Key: Enter the API key you generated for the client ID in Kount 360 for production or test.
-
-
Payment Review Workflow
-
Payment Review Workflow Mode: Select Pre-Authorization Payment Review or Post-Authorization Payment Review. This setting specifies when Kount is called. Pre-Authorization Payment Review calls Kount before the payment is captured and Post-Authorization Payment Review calls Kount after the payment is captured.
-
Review/Decline Action: Select Hold Order/Decline Status, Cancel Order/Void Payment, or Refund/Credit Order. If Kount marks an order as Review or Decline, this setting determines which status the Magento order should be.
-
Prevent Resetting of Order Status: Select Yes or No. The default is Yes. Selecting No can cause unexpected workflow issues. Contact your Integration Engineer for more information.
-
-
Order Settings
Kount is involved prior to or after the payment processor is queried for authorization. In the Pre-Authorization scenario, all transactions are processed by Kount. In the Post-Authorization scenario, the customer chooses whether to pass on orders that were declined by the payment processor. Based upon the rules created by the customer, the returned statuses from Kount are Approved, Declined, or Review.
-
Display on Review: Select Yes or No. When Yes is selected, orders in a Kount review status display in the customer's account.
-
Display Declined: Select Yes or No. When Yes is selected, orders in a Kount declined status display in the customer's account.
-
-
Disable Payment Methods
Disable Payment Method Codes: Select the payment method codes that you want disabled. When disabled, Kount is not called for the selected payment method codes. The default selection is None, which enables Kount for all payment methods.
-
Event Notifications (webhooks)
A webhook is a secure system that notifies you of events that have occurred in Kount 360. The event notification processor queries the event notification service to determine which events you are subscribed to. Then, for each subscription, it calls that event type to construct the response message.
Note
You must enable this setting if you want orders to be updated in Magento when they are updated in Kount 360.
-
Enabled: Select Yes to enable webhooks.
-
URL: Add domains during webhook creation in Kount 360. Webhooks are found in the Admin section of Kount 360. To create a webhook, refer to Managing Webhooks.
Note
Only add URLs for configured stores.
-
Additional IPs for Load Balancer: If your Magento is behind a load balancer or firewall that changes the IP of incoming requests to Magento, you must add the additional IPs in this section.
-
-
Logging
-
Enable Kount 360 Logging: Select Yes or No to enable or disable logging to the Kount log file at
<magento_root>/var/log/kount360.log. -
Log File: You can download the log file by selecting Download.
-
-
Admin
Enabled in Admin: Select Yes or No to enable or disable Kount 360 Integration in the Admin section. When Yes is selected, customer service representatives can submit orders in the Admin section of Magento for a customer.
-
-
Select Save Config.
Kount provides the ability to manually approve, review, or decline transactions in Kount 360, then have that action sent back to the Magento instance. This interaction is dependent upon the webhook being configured in Kount 360.
In the Kount extension, security measures are implemented to protect against unauthorized submissions. Only webhook events sent from Kount are accepted. The webhook events are queued within Kount and then pushed out to the customer.
To create a webhook in Kount 360, go to Managing Webhooks.
-
Sign in to Kount 360.
-
Create a webhook and use the website ID as the Channel Name.
Note
The Website ID is located in Magento Admin Panel > Kount 360 > Account Information.
-
For the Webhook URL field, use the Event Notifications URL found in Magento.
Note
The Event Notifications URL is located in Magento Admin Panel > Kount > Kount Integration > Event Notifications.
-
Save the configured webhook.
After the initial install, the Website ID field is set to Default. If you are configuring multiple sites for a single Magento instance where each website needs a unique value, use the unique value in the Website ID field of Magento after Configuring Multiple Websites.