Fraud Errors

When a transaction triggers fraud rules, BlueSnap returns one of the following errors:

Code	Name	Description
15011	`FRAUD_DETECTED`	This fraud error message includes a `fraud-events` resource with the following information: an ID for the fraud event an indication of what fraud rule or configurable threshold was triggered and why - an indication of whether the transaction was declined or held for review
15011	`FRAUD_ERROR`	This error can indicate an invalid card or an invalid site is being used for the transaction. This fraud error message includes a `fraud-events` resource containing an ID for the fraud event.

If a transaction triggers multiple fraud rules, then multiple fraud-event resources (one for each triggered fraud rule or threshold) may be sent within the fraud-events resource for that transaction. See the Multiple fraud events example below.

For a complete description of the fraud-events and fraud-event resources and the values that can appear in each, see:

Merchants who enroll in the Merchant Configurable fraud prevention service will receive additional fraud detail if an order triggers one of the rules they have configured. For information about fraud prevention service levels supported by BlueSnap, see Fraud prevention.

Sample fraud error messages

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<messages xmlns="http://ws.plimus.com">
    <message>
    	<error-name>FRAUD_DETECTED</error-name>
      <code>15011</code>
      <description>
      The request cannot be fulfilled for the current shopper. Please contact BlueSnap support for further details.
      </description>
      <fraud-events>
       <fraud-reference-id>3565</fraud-reference-id>
       <fraud-transaction-id>DSYK0G9YPJYS</fraud-transaction-id>
       <fraud-event>
          <fraud-event-code>billShipAddressNotMatchDecline</fraud-event-code>
          <fraud-event-decision>D</fraud-event-decision>
          <fraud-event-expression>billing_address != shipping_address</fraud-event-expression>
       </fraud-event>
    	<fraud-event>
           <fraud-event-code>blacklistshippingcountrydecline</fraud-event-code>
           <fraud-event-decision>D</fraud-event-decision>
           <fraud-event-expression>AD is in list</fraud-event-expression>
    	</fraud-event>
    </fraud-events>
    </message>
</messages>

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<messages xmlns="http://ws.plimus.com">
  <message>
    <error-name>FRAUD_DETECTED</error-name>
    <code>15011</code>
    <description>
      The request cannot be fulfilled for the current shopper. Please contact BlueSnap support for further details.
    </description>
    <fraud-events>
      <fraud-reference-id>3565</fraud-reference-id>
      <fraud-transaction-id>DSYK0G9YPJYS</fraud-transaction-id>
    </fraud-events>
  </message>
</messages>

📘
Note regarding multiple fraud events
In the multiple fraud events example above, the second fraud-event was the triggering of the shipping country blacklist (the value of the fraud-event-code is blacklistshippingcountrydecline). This fraud-event-expression property says that this rule was triggered because AD is in list. That means that the shopper entered Andorra (country code AD) as the shipping country, and that Andorra is on the blacklist.

Kount error messages

The following error messages may be returned by Kount.

Kount RIS Response Key	Kount Error	BlueSnap Fraud Error	BlueSnap Fraud Error description
323	Bad Site	Invalid Site	Site ID in the API request does not match a website ID in the Agent Web Console
332	Bad Card	Invalid Card	Card used in the API request is not valid

Sample fraud error messages

📘Note regarding multiple fraud events

Kount error messages

📘
Note regarding multiple fraud events