X-Payments:KOUNT Antifraud screening - Revision history

Dohtur at 15:01, 11 April 2020

2020-04-11T15:01:32Z

Dohtur at 06:33, 19 July 2019

2019-07-19T06:33:01Z

Dohtur at 06:21, 19 July 2019

2019-07-19T06:21:37Z

Dohtur at 11:26, 12 July 2019

2019-07-12T11:26:29Z

Dohtur at 16:57, 11 July 2019

2019-07-11T16:57:54Z

Dohtur at 13:21, 11 July 2019

2019-07-11T13:21:50Z

Ambal at 08:28, 22 April 2019

2019-04-22T08:28:26Z

Dohtur at 13:46, 19 December 2018

2018-12-19T13:46:49Z

Dohtur at 12:56, 1 October 2018

2018-10-01T12:56:44Z

Dohtur at 18:44, 29 September 2018

2018-09-29T18:44:15Z

@@ Line 27: / Line 27: @@
 Once Kount antifraud screening has been configured and enabled for a specific payment configuration, any new payment transactions for this payment configuration will be screened by Kount.<br /><br />'''Important:''' Kount will not screen transactions made using a previously saved credit card.<br /><br />
-What happens when a buyer submits their credit card info to pay for an order in a store accepting payments via X-Payments and protected by Kount?<br />
+What happens when a buyer submits their credit card info to pay for an order in a store accepting payments via X-Payments and protected by Kount?<br /><br />
-Technically, the process involves three steps:
+Technically, the process involves three steps:<br /><br />
 At the first step, X-Payments makes a call to Kount to invoke Kount’s risk check service. In this call, information about the payment transaction (including the IP address, email address, shipping address, card details, billing info, order details, etc.) is submitted to Kount. This happens for each new card prior to contacting the payment gateway.<br />
-Kount’s risk check service checks the information submitted to it using Kount's proprietary algorithms and applies the custom rules configured for the merchant's account. Kount account settings provide substantial flexibility for configuring the rules, which means you can fine-tune the rules to your needs with precision - to the degree where you can specify that a transaction should be declined if initiated by a buyer of a certain name, or be declined if the risk score generated by Kount based on its internal algorithms exceeds a certain value. In practice, Kount will consider a lot of factors such as the buyer's country, how far the buyer's location is from the location of the store where the purchase is being made, whether the buyer is telling the truth about their location (based on whether the address submitted by the buyer matches the geolocation info collected by the service regarding the IP address from which the purchase is being made), the type of products being purchased (for example, if the buyer has a history of consistently using the card to buy car parts and suddenly pays for $2000 worth of makeup and beauty products) and so on. As a result, Kount's risk check service responds with a risk decision, which includes a risk score and a decision as to what should be done about the transaction in question (whether the transaction looks safe and should be processed, or whether it looks suspicious and should be declined or suspended for manual review by the merchant). X-Payments will honor the risk decision returned by Kount’s service. If the decision is to process the transaction, X-Payments will continue with the transaction processing by submitting the details to the payment gateway. If the risk decision is to decline the transaction, X-Payments will block the transaction and not contact the payment gateway. This way high risk transactions are blocked automatically before they become a problem, and the merchant does not have to pay the payment processor for processing a card that might have been stolen.<br />The setting "If Kount Declines" determines whether a transaction recommended for blocking should be blocked at once or should be suspended for manual review by the merchant. (In the latter case, the merchant will be able to review the transaction details and decide whether they want to decline the transaction or accept the risks associated with processing the card).<br />
+Kount’s risk check service checks the information submitted to it using Kount's proprietary algorithms and applies the custom rules configured for the merchant's account. Kount account settings provide substantial flexibility for configuring the rules, which means you can fine-tune the rules to your needs with precision - to the degree where you can specify that a transaction should be declined if initiated by a buyer of a certain name, or be declined if the risk score generated by Kount based on its internal algorithms exceeds a certain value. In practice, Kount will consider a lot of factors such as the buyer's country, how far the buyer's location is from the location of the store where the purchase is being made, whether the buyer is telling the truth about their location (based on whether the address submitted by the buyer matches the geolocation info collected by the service regarding the IP address from which the purchase is being made), the type of products being purchased (for example, if the buyer has a history of consistently using the card to buy car parts and suddenly pays for $2000 worth of makeup and beauty products) and so on. As a result, Kount's risk check service responds with a risk decision, which includes a risk score and a decision as to what should be done about the transaction in question (whether the transaction looks safe and should be processed, or whether it looks suspicious and should be declined or suspended for manual review by the merchant). X-Payments will honor the risk decision returned by Kount’s service. If the decision is to process the transaction, X-Payments will continue with the transaction processing by submitting the details to the payment gateway. If the risk decision is to decline the transaction, X-Payments will block the transaction and not contact the payment gateway. This way high risk transactions are blocked automatically before they become a problem, and the merchant does not have to pay the payment processor for processing a card that might have been stolen.<br />The setting "If Kount Declines" determines whether a transaction recommended for blocking should be blocked at once or should be suspended for manual review by the merchant. (In the latter case, the merchant will be able to review the transaction details and decide whether they want to decline the transaction or accept the risks associated with processing the card).<br /><br />
-At the second step, X-Payments contacts the payment gateway for order processing. This, of course, does not happen for transactions that have been blocked.
+At the second step, X-Payments contacts the payment gateway for order processing. This, of course, does not happen for transactions that have been blocked.<br /><br />
 At the third step, X-Payments once again contacts Kount to find out the transaction result, including the results of the CVV и AVS checks. Kount's risk check service  also stores this information for future use.
 <br /><br />

@@ Line 13: / Line 13: @@
 # Configure KOUNT for the current payment configuration:
 ## Click <u>Configure</u>.<br />[[File:Kount_configure.png|668px|border]]<br />The KOUNT settings page for the current payment configuration opens:<br />[[File:Firstdata_kount.png|668 px|border]]<br />
-## Adjust the KOUNT settings:<br />[[File:Xp_kount_settings.png|668px|border]]<br />
+## Adjust the KOUNT settings:<br />[[File:Xp_kount_settings1.png|668px|border]]<br />
 ##* '''Status''' (Not configured / Enable / Disable): This setting indicates whether KOUNT module is active. For now just leave it as is. After you provide the rest of the required settings (below) and save the changes, KOUNT module will be enabled automatically. You will then be able to use this setting to disable/re-enable KOUNT for your current payment configuration as you require.
 ##* '''Merchant ID''': Specify your Merchant ID as was provided to you by Kount.

@@ Line 8: / Line 8: @@
 # Sign up for a Merchant account with Kount at [http://www.kount.com/?utm_source=x-cart&utm_medium=home&utm_campaign=partner http://www.kount.com]. You will be provided with some credentials that you will need to configure Kount fraud screening in X-Payments: your Merchant ID and your Site ID. Take note of this information.<br />
 # In the Kount Agent Web Console (AWC), create your API Key(s).<br />[[File:Kount_api_keys.png|668px|border]]<br />API Keys are required to authenticate to Kount. Note that Kount has separate environments for testing and production, and API Keys must be created and used for each of the environments separately. Kount's instructions for creating API Keys can be found here: [https://support.kount.com/s/article/Create-an-API-Key https://support.kount.com/s/article/Create-an-API-Key].<br />
-# In the Kount Agent Web Console (AWC), configure customized credit card validation rules for your online store to match the unique needs of your business.<br />Be sure to adjust the setting "If Kount Declines"; this setting determines what happens if Kount recommends that a transaction should be declined: should the transaction be declined at once, or should the merchant be given a chance to review the transaction manually and possibly accept it.
+# In the Kount Agent Web Console (AWC), configure customized credit card validation rules for your online store to match the unique needs of your business.
 # Log in to X-Payments and locate the payment configuration for which you want to use Kount fraud screening. For the sake of example, we are going to enable KOUNT for the payment configuration "First Data Payeezy Gateway (ex- Global Gateway e4)".<br />[[File:Firstdata_pconf.png|668 px|border]]<br />Open the details of the chosen payment configuration for editing.
 # In the payment configuration details, check the '''Antifraud service''' setting. If you haven't been using any antifraud service for the current payment configuration so far, this field will be set to "Not enabled".<br />[[File:Antifraud_service.png|668 px|border]]<br />Reset this field to "KOUNT Antifraud screening".<br />[[File:Kount_selected.png|668 px|border]]<br />Click '''Save''' to save the changes.<br />
@@ Line 17: / Line 17: @@
 ##* '''Merchant ID''': Specify your Merchant ID as was provided to you by Kount.
 ##* '''Site ID''': Specify your Site ID.
 ##* '''Test/Live mode''': Use this to set the operation mode for Kount fraud screening service - ''Test'' or ''Live''. For access to the Kount AWC in Live mode use the address https://awc.kount.net, in Test mode - the address https://awc.test.kount.net.
 ##* '''Description of products''': Common name of the products sold by your store.<br />
 ##* '''Mode for RIS update request''': Choose one of the available options (''X: Update data and re-validate transaction against rules'' or ''U: Update transaction data only''). Mode X is recommended if rules are based on the AVS information returned from the payment gateway. Note that additional charges may apply for Mode X.
-##* '''API key''': Enter the API key you have created in the AWC. It will be used for authentication.<br />Note that Kount API has been updated and, starting with X-Payments 3.1.4, Kount certificates (RIS Certificates) are no longer supported. You must use an API key. You must also obtain a Configuration key for the field below.
+##* '''Configuration key''': This setting is only available in X-Payments Enterprise. Specify your Configuration key; this one needs to be obtained from Kount.
-##* '''Configuration key''': Specify your Configuration key; this one needs to be obtained from Kount.
+##* '''If Kount declines''': This setting determines what happens if Kount recommends that a transaction should be declined: should the transaction be declined at once, or should the merchant be given a chance to review the transaction manually and possibly accept it.
 ## Click '''Save''' to save your settings.
 # Make sure Kount fraud screening is enabled:<br />[[File:Kount_enabled.png|668px|border]]<br />
@@ Line 29: / Line 30: @@
 Technically, the process involves three steps:
 At the first step, X-Payments makes a call to Kount to invoke Kount’s risk check service. In this call, information about the payment transaction (including the IP address, email address, shipping address, card details, billing info, order details, etc.) is submitted to Kount. This happens for each new card prior to contacting the payment gateway.<br />
-Kount’s risk check service checks the information submitted to it using Kount's proprietary algorithms and applies the custom rules configured for the merchant's account. Kount account settings provide substantial flexibility for configuring the rules, which means you can fine-tune the rules to your needs with precision - to the degree where you can specify that a transaction should be declined if initiated by a buyer of a certain name, or be declined if the risk score generated by Kount based on its internal algorithms exceeds a certain value. In practice, Kount will consider a lot of factors such as the buyer's country, how far the buyer's location is from the location of the store where the purchase is being made, whether the buyer is telling the truth about their location (based on whether the address submitted by the buyer matches the geolocation info collected by the service regarding the IP address from which the purchase is being made), the type of products being purchased (for example, if the buyer has a history of consistently using the card to buy car parts and suddenly pays for $2000 worth of makeup and beauty products) and so on. As a result, Kount's risk check service responds with a risk decision, which includes a risk score and a decision as to what should be done about the transaction in question (whether the transaction looks safe and should be processed, or whether it looks suspicious and should be declined or suspended for manual review by the merchant). X-Payments will honor the risk decision returned by Kount’s service. If the decision is to process the transaction, X-Payments will continue with the transaction processing by submitting the details to the payment gateway. If the risk decision is to decline the transaction, X-Payments will block the transaction and not contact the payment gateway. This way high risk transactions are blocked automatically before they become a problem, and the merchant does not have to pay the payment processor for processing a card that might have been stolen.<br />The Kount setting "If Kount Declines" determines whether a transaction recommended for blocking should be blocked at once or should be suspended for manual review by the merchant. (In the latter case, the merchant will be able to review the transaction details and decide whether they want to decline the transaction or accept the risks associated with processing the card).<br />
+Kount’s risk check service checks the information submitted to it using Kount's proprietary algorithms and applies the custom rules configured for the merchant's account. Kount account settings provide substantial flexibility for configuring the rules, which means you can fine-tune the rules to your needs with precision - to the degree where you can specify that a transaction should be declined if initiated by a buyer of a certain name, or be declined if the risk score generated by Kount based on its internal algorithms exceeds a certain value. In practice, Kount will consider a lot of factors such as the buyer's country, how far the buyer's location is from the location of the store where the purchase is being made, whether the buyer is telling the truth about their location (based on whether the address submitted by the buyer matches the geolocation info collected by the service regarding the IP address from which the purchase is being made), the type of products being purchased (for example, if the buyer has a history of consistently using the card to buy car parts and suddenly pays for $2000 worth of makeup and beauty products) and so on. As a result, Kount's risk check service responds with a risk decision, which includes a risk score and a decision as to what should be done about the transaction in question (whether the transaction looks safe and should be processed, or whether it looks suspicious and should be declined or suspended for manual review by the merchant). X-Payments will honor the risk decision returned by Kount’s service. If the decision is to process the transaction, X-Payments will continue with the transaction processing by submitting the details to the payment gateway. If the risk decision is to decline the transaction, X-Payments will block the transaction and not contact the payment gateway. This way high risk transactions are blocked automatically before they become a problem, and the merchant does not have to pay the payment processor for processing a card that might have been stolen.<br />The setting "If Kount Declines" determines whether a transaction recommended for blocking should be blocked at once or should be suspended for manual review by the merchant. (In the latter case, the merchant will be able to review the transaction details and decide whether they want to decline the transaction or accept the risks associated with processing the card).<br />
 At the second step, X-Payments contacts the payment gateway for order processing. This, of course, does not happen for transactions that have been blocked.
 At the third step, X-Payments once again contacts Kount to find out the transaction result, including the results of the CVV и AVS checks. Kount's risk check service  also stores this information for future use.

@@ Line 8: / Line 8: @@
 # Sign up for a Merchant account with Kount at [http://www.kount.com/?utm_source=x-cart&utm_medium=home&utm_campaign=partner http://www.kount.com]. You will be provided with some credentials that you will need to configure Kount fraud screening in X-Payments: your Merchant ID and your Site ID. Take note of this information.<br />
 # In the Kount Agent Web Console (AWC), create your API Key(s).<br />[[File:Kount_api_keys.png|668px|border]]<br />API Keys are required to authenticate to Kount. Note that Kount has separate environments for testing and production, and API Keys must be created and used for each of the environments separately. Kount's instructions for creating API Keys can be found here: [https://support.kount.com/s/article/Create-an-API-Key https://support.kount.com/s/article/Create-an-API-Key].<br />
-# In the Kount Agent Web Console (AWC), configure customized credit card validation rules for your online store to match the unique needs of your business.<br />
+# In the Kount Agent Web Console (AWC), configure customized credit card validation rules for your online store to match the unique needs of your business.<br />Be sure to adjust the setting "If Kount Declines"; this setting determines what happens if Kount recommends that a transaction should be declined: should the transaction be declined at once, or should the merchant be given a chance to review the transaction manually and possibly accept it.
 # Log in to X-Payments and locate the payment configuration for which you want to use Kount fraud screening. For the sake of example, we are going to enable KOUNT for the payment configuration "First Data Payeezy Gateway (ex- Global Gateway e4)".<br />[[File:Firstdata_pconf.png|668 px|border]]<br />Open the details of the chosen payment configuration for editing.
 # In the payment configuration details, check the '''Antifraud service''' setting. If you haven't been using any antifraud service for the current payment configuration so far, this field will be set to "Not enabled".<br />[[File:Antifraud_service.png|668 px|border]]<br />Reset this field to "KOUNT Antifraud screening".<br />[[File:Kount_selected.png|668 px|border]]<br />Click '''Save''' to save the changes.<br />

@@ Line 26: / Line 26: @@
 Once Kount antifraud screening has been configured and enabled for a specific payment configuration, any new payment transactions for this payment configuration will be screened by Kount.<br /><br />'''Important:''' Kount will not screen transactions made using a previously saved credit card.<br /><br />
+What happens when a buyer submits their credit card info to pay for an order in a store accepting payments via X-Payments and protected by Kount?<br />
 <br /><br />
-In the store where the transaction originated, the order to which the transaction pertains will be marked with an icon. For example, here's an order list from an X-Cart 5 based online store with an order of Aug 30, 2018 screened by Kount:<br />
+In the store where the transaction originated, the order to which the transaction pertains is marked with a special icon. For example, here's an order list from an X-Cart 5 based online store with an order of Aug 30, 2018 screened by Kount:<br />
 ::[[File:Kount_orderlist.png|668px|border]]<br />
-If Kount identifies a transaction as potentially fraudulent, it will provide a warning so you can decide whether you wish to accept or decline this transaction. Here's what it looks like on the payment details page in X-Payments:
+For transactions suspended for manual review, X-Payments provides a warning so the merchant can decide whether they wish to accept or decline this transaction. Here's what it looks like on the payment details page in X-Payments:
 ::[[File:Kount_warning.png|668px|border]]<br />
 A similar warning appears in the store. For example, here's what it looks like in an X-Cart 5 store:
 ::[[File:Kount_warning_xc.png|668px|border]]<br />
-You will be able to view the results of screening by Kount on the Payment details page in X-Payments:
+The results of screening by Kount can be viewed on the Payment details page in X-Payments:
 ::[[File:Kount_passed.png|668px|border]]
-It is also possible to view the results of screening by Kount on the order details page in the store:
+and on the order details page in the store:
 ::[[File:Kount_results_xc.png|668px|border]]
 [[Category:X-Payments User Manual]]

@@ Line 4: / Line 4: @@
 To help you protect your business against fraud, X-Payments versions 2.1 and later provide integration with a powerful fraud detection and prevention solution by [http://www.kount.com/?utm_source=x-cart&utm_medium=home&utm_campaign=partner Kount]. Kount delivers an all-in-one, SaaS model fraud and risk management platform for merchants operating in card-not-present (CNP) environments and looking to root out fraudsters and increase revenue. For each transaction, Kount’s real-time "decisioning" engine analyzes hundreds of relevant variables and activity across the globe. Kount applies a multitude of proven and patented technologies including Multi-layered Device Fingerprinting®, Proxy Piercer® geolocation tools, statistical scoring, rules-based fraud detection, cross-merchant linking, and Persona behavioral modeling. Kount's proprietary technology has reviewed hundreds of millions of transactions and provides maximum protection for some of the world's best-known brands.
 <br /><br />
 To start using Kount for online payment fraud screening in X-Payments, complete the following steps:<br />