Kount Review Queue

We can support the Review process in Kount. However, it requires an additional step to be added to your process. Below are the steps to accommodate the review process.

1. Configure Kount


You can work with your Client Success Manager to configure your Kount rules to support the Review queue and also add the VIP rule in order to bypass the Review queue when the transaction should be processed.

2. Handle and Identify “Review” in the Sales Response


When you send a Sale transaction to ConnexPay and that transaction hits the Review queue in Kount, you will see "processorStatusCode":"R" (example below - line 23)
{
"guid":"965a67b0-cd0e-4020-973b-5e0d1b4bd6e2",
"status":"Transaction - Declined",
"type":"Default",
"batchStatus":"Batch - Open",
"timeStamp":"2019-11-20T05:37:13.22-05:00",
"deviceGuid":"f758a448-7780-4b50-93a1-28329e37f94f",
"amount":100.00,
"activated":true,
"tenderType":"Credit",
"effectiveAmount":0.00,
"riskResponse":{
  "transactionId":"SKEYNWEH",
   "response":"Review",
   "reason":"User Outside US/CA/IN",
   "score":"24",
   "omniscore":"84.2"
},
"orderNumber":"HSG432",
"cardDataSource":"INTERNET",
"batchGuid":"c71d0ee6-b595-4792-b1ee-1156d28be132",
"riskProcessingOnly":false,
"processorStatusCode":"R",
"processorResponseMessage":"Risk Decline",
"wasProcessed":false,
"statementDescription":"ABC Statement Descriptor",
"generatedBy":"apiuser",
"card":{
   "first6":"456789",
   "first4":"4567",
   "last4":"4321",
   "cardHolderName":"John Doe",
   "cardType":"Visa",
   "expirationDate":"2022-12",
   "guid":"736585b2-1637-42e1-84e8-bdf6e43a3575",
   "customer":{
      "guid":"3bd93697-005a-4723-a7f8-f892577ee2bf",
      "firstName":"John",
      "lastName":"Doe",
      "dateOfBirth":"1990-12-12T00:00:00",
      "address1":"123 Test St",
      "city":"Alpharetta",
      "phone":"6124567894",
      "email":"[email protected]"
   }
},
"addressVerificationResult":"Unavailable",
"cvvVerificationResult":"Unavailable",
"walletProvider":0
}
If the transaction is Declined, the "processorStatusCode":"D" If the transaction is Approved, it would then show the status code of the transaction from the credit card processor. Usually "processorStatusCode":"A0000" for example. In this case the riskResponse would be Approved as well.

📘

The “riskResponse.response” will say “Declined” and the “status” will be “Transaction - Declined” but we’re working on changing that in the upcoming release to indicate “Review” instead.

3. Handle Resubmitting the Transaction (if it passes Review) to ConnexPay

Once the Risk team reviews the transaction in Kount, and they deem it safe to accept the consumer’s card, that transaction will need to be resubmitted to ConnexPay.

📘

When the transaction is manually approved in Kount, the transaction will need to be resubmitted to ConnexPay - that does not happen systematically between Kount’s and ConnexPay’s systems.

You will need to include a specific property in the subsequent request or the transaction will end up in the Review queue again and will not be processed. Include “[email protected]” in the “RiskData.Email” API property in your Sales request to bypass the Review queue on the subsequent request and charge the customer’s credit card.

Nothing needs to happen (in the ConnexPay system) if the Risk team does not want to proceed with the transaction.


Did this page help you?