How to Install and Set Up the Kount Magento Extension

Copy the code below to install the Magento module and its dependencies.

    composer require kount/magento2-kount

    php bin/magento module:enable kount

    php bin/magento setup:upgrade

Fill out the Account Information section using the following information:

Enabled: Toggle the Kount extension from being Enabled or Disabled in the Magento Order Management workflow.

Merchant Number: The merchant number issued by Kount. This merchant number is the same regardless if it is in the Kount Test or Production environment.

Website ID: On the initial install this field is set as Default. This allows multiple sites within the Magento instance to be managed by Kount. Different rules and searching features can be created for different sites.

Environment: is setting determines to which Kount environment the Magento instance is posting data.

API Key: The Kount Command API key is used for authentication and is created and visible within the AWC by going to Admin and then API Keys.

Fill out the Payment Review Workflow section using the following information:

Payment Review Workflow Mode: Specify when Kount is queried.

Decline Action: The Decline Action options are specific to Post-Authorization transactions. Based on the authorization strategy a customer has chosen – whether to authorize and capture later or authorize and capture together – different decline actions are required to configure.

Hold Order/Decline Status: This places the order in a hold state but sets the status to decline within Magento. This allows customers to release the order if the transaction was a false decline without making the end user resubmit the transaction.

Fill out the Disable Payment Methods section using the following information:

Disable Payment Method Codes: If any of these payment methods are selected, a query is not sent to Kount for analysis. This functionality provides customers the ability to whitelist payment methods that they do not want to be evaluated by Kount.

We recommend that you whitelist the Kount scripts to bypass Content Security Policies (CSP), if the CSP Module is enabled.

CSP implementation example:

<?xml version="1.0" encoding="UTF-8"?>

<csp_whitelist

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 9 xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Csp:etc/csp_whitelist.xsd">

<policies>

<policy id="script-src">

<values>

<value id="kount" type="host">.kaptcha.com</value>

</values>

</policy>

<policy id="connect-src">

<values>

<value id="kount" type="host">.kaptcha.com</value>

</values>

</policy>

</policies>

</csp_whitelist>

When a customer submits phone orders with the same web page interface as an end user, the customer’s device data – not the end user’s device data – is sent to Kount. This causes order linking to occur and, in time, elevates the score of all orders associated with the persona.

Do not send Kount your internal device data. To block the device data of customer service representatives from being sent to Kount, set the Phone To Web Enable configuration to enabled by selecting Yes and then add the IP addresses associated with the customer service network(s) to the IP Address Exclude text box.

The logging functionality enables or disables logging Kount information to the server. Select Yes or No to enable or disable logging.

In order to change the module's behavior for testing purposes after logging in, create a Kount Test Portal account.

If conditions are true and the apply no decision option is selected, the end user logs in without any checks and restrictions.

If conditions are true and the block option is selected, the end user is redirected to the login page when they try to log in. This displays a message: "The sign-in is not available for your customer account."

If conditions are true and challenge is selected, then the end user is prompted with the 2FA Setup page. The Log Out link is the only available link from this page. When the user tries to log in again 2FA Setup page will be open.

It redirects to the login page and show the message: "Invalid 2FA Authentication Code. You have spent all possible tries to enter valid 2FA code. Please log in again!"

When a user tries to log in again 2FA Setup page is open. Scan QR-code (for example, via app “Google Authenticator”) and enter valid code. It can enter to customer account and show the message: "2FA successfully set up."

When a transaction is evaluated by Kount and one or more customer-created decline rule conditions are triggered, the order does not continue to the payment processor for authorization, and a failure message is presented to the end user. This allows customers to create Decline rule conditions and automatically stop transactions from being submitted to the payment processor.

Similar to when a transaction is declined by the payment processor, when transactions are declined by Kount, no reference of that transaction is found in the Magento Order Management panel. Since Kount is queried before the processor, declined transactions are displayed in the AWC..

When a transaction is evaluated by Kount and no customer-created rule conditions for Decline, Review, or Escalate are triggered, the order is flagged with a status of Approve and continues to the payment processor for authorization. The default status within Magento for a Kount Approve order is Processing.

Unlike the Pre-Authorization workflow, when a transaction is evaluated by Kount and one or more customer-created Decline rule conditions are triggered, the end user is not presented with an error popup or notification that the transaction failed.

Within Magento, the inventory is replaced. The order is then refunded if it was authorized and captured. If the order was only authorized during checkout, it is canceled.

The third option is to change the order status to On Hold.

When a transaction is evaluated by Kount and no customer-created rule conditions are triggered, the order is flagged with a status of Approved. The default status within Magento for a Kount Approve order is Processing.

An example of calling workflow methods on custom events can be seen in the

\Kount\Kount\Plugin\PayPal\Controller\Payflow\ReturnUrl class. You need to add three dependencies to the custom observer:

/**

* @var \Kount\Kount\Helper\Workflow

*/

protected $helperWorkflow;

/**

* @var \Kount\Kount\Model\Config\Workflow

*/

protected $configWorkflow;



/**

* @var \Kount\Kount\Model\WorkflowFactory

*/

protected $workflowFactory;


And use them as such:

if (!$this->helperWorkflow->isProcessable($order))

{ return $result;

}


$workFlowType = $this->configWorkflow-

>getWorkflowMode($or- der->getStoreId());

$workFlow = $this->workflowFactory-

>create($workFlowType);


$workFlow->success($order); // or $workFlow-

>failure($order);

The success() and failure() methods require a \Magento\Sales\Model\Order $order object as a parameter. The start() method requires a \Magento\Sales\Model\Order\Payment $payment object as a parameter.

Keep in mind that the custom event must call the workflow’s methods for a specific payment method only. It is possible to reuse conditional logic with a default false condition, as it is done for \Kount\Kount\Observer\PaymentPlaceEnd observer (customization for Authorize.Net DirectPost):

Note: Authorize.net direct post is no longer supported.

<virtualType

name="Kount\Kount\Model\Observer\PaymentPlaceEnd\Conditio

n" type="Kount\Kount\Model\Observer\Condition">

<arguments>

<argument name="default" xsi:type="boolean">false</argument>

<argument name="conditions" xsi:type="array">

<item name="authorizenet_directpost" xsi:type="string">Kount\Kount\Observer\PaymentPlaceEnd\Condition\AuthorizeDirectPost</item>

</argument>

</arguments>

</virtualType>

What are the RIS payment types for Magento? Kount is integrated with Magento with the following payment types supported natively within the Kount Magento Extension that provides cross-merchant linking with the Kount network: