{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","settings":"","results":{"codes":[]},"params":[]},"next":{"description":"","pages":[]},"title":"Fraud Errors","type":"basic","slug":"fraud-errors","excerpt":"","body":"When a transaction triggers fraud rules, BlueSnap returns the following error:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"Code\",\n    \"h-1\": \"Name\",\n    \"h-2\": \"Description\",\n    \"0-0\": \"15011\",\n    \"0-1\": \"FRAUD_DETECTED\",\n    \"0-2\": \"The fraud error message includes a `fraud-events` resource with the following information:\\n  * an ID for the fraud event\\n  * an indication of what fraud rule or configurable threshold was triggered and why\\n  * an indication of whether the transaction was declined or held for review\"\n  },\n  \"cols\": 3,\n  \"rows\": 1\n}\n[/block]\nIf 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.\n\nFor a complete description of the `fraud-events` and `fraud-event` resources and the values that can appear in each, see:\n  * [fraud-events](doc:fraud-event) \n  * [fraud-event](fraud-event#fraudevent) \n\nMerchants 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](/docs/fraud-prevention).\n\n###Sample fraud error messages\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\" standalone=\\\"yes\\\"?>\\n<messages xmlns=\\\"http://ws.plimus.com\\\">\\n    <message>\\n    \\t<error-name>FRAUD_DETECTED</error-name>\\n      <code>15011</code>\\n      <description>\\n      The request cannot be fulfilled for the current shopper. Please contact BlueSnap support for further details.\\n      </description>\\n      <fraud-events>\\n       <fraud-reference-id>3565</fraud-reference-id>\\n       <fraud-event>\\n          <fraud-event-code>billShipAddressNotMatchDecline</fraud-event-code>\\n          <fraud-event-decision>D</fraud-event-decision>\\n          <fraud-event-expression>billing_address != shipping_address</fraud-event-expression>\\n       </fraud-event>\\n    \\t<fraud-event>\\n           <fraud-event-code>blacklistshippingcountrydecline</fraud-event-code>\\n           <fraud-event-decision>D</fraud-event-decision>\\n           <fraud-event-expression>AD is in list</fraud-event-expression>\\n    \\t</fraud-event>\\n    </fraud-events>\\n    </message>\\n</messages>      \",\n      \"language\": \"xml\",\n      \"name\": \"Multiple fraud events\"\n    },\n    {\n      \"code\": \"<?xml version=\\\"1.0\\\" encoding=\\\"UTF-8\\\" standalone=\\\"yes\\\"?>\\n<messages xmlns=\\\"http://ws.plimus.com\\\">\\n  <message>\\n    <error-name>FRAUD_DETECTED</error-name>\\n    <code>15011</code>\\n    <description>\\n      The request cannot be fulfilled for the current shopper. Please contact BlueSnap support for further details.\\n    </description>\\n    <fraud-events>\\n      <fraud-reference-id>3565</fraud-reference-id>\\n    </fraud-events>\\n  </message>\\n</messages> \",\n      \"language\": \"xml\",\n      \"name\": \"Single fraud event\"\n    }\n  ]\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"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.\",\n  \"title\": \"Note regarding multiple fraud events\"\n}\n[/block]\n##Kount error messages\nThe following error messages may be returned by Kount.\n\nKount&nbsp;RIS Response&nbsp;Key | Kount&nbspError | BlueSnap Fraud Error | BlueSnap Fraud Error description\n--- | --- | --- | ---\n323 | Bad Site | Invalid Site | Site ID in the API request does not match a website ID in the Agent Web Console\n399 | Bad Optn | Invalid UDF | UDF in the API request does not match a UDF in the Agent Web Console","updates":[],"order":10,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"5ed5174637c3c607440c0a34","project":"57336fd5a6a9c40e00e13a0b","version":{"version":"8976-XML","version_clean":"8976.0.0-XML","codename":"3.34.0 Release","is_stable":false,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["5ed5174637c3c607440c098b","5ed5174637c3c607440c098c","5ed5174637c3c607440c098d","5ed5174637c3c607440c098e","5ed5174637c3c607440c098f","5ed5174637c3c607440c0990","5ed5174637c3c607440c0991","5ed5174637c3c607440c0992","5ed5174637c3c607440c0993","5ed5174637c3c607440c0994","5ed5174637c3c607440c0995","5ed5174637c3c607440c0996","5ed5174637c3c607440c0997","5ed5174637c3c607440c0998","5ed5174637c3c607440c0999","5ed5174637c3c607440c099a","5ed5174637c3c607440c099b","5ed5174637c3c607440c099c"],"_id":"5ed5174637c3c607440c0a3c","project":"57336fd5a6a9c40e00e13a0b","__v":0,"forked_from":"5e5d3a02fb6fb40050cb3c15","createdAt":"2018-04-24T15:24:22.608Z","releaseDate":"2018-04-24T15:24:22.608Z"},"category":{"sync":{"isSync":false,"url":""},"pages":[],"title":"Errors","slug":"errors","order":13,"from_sync":false,"reference":false,"_id":"5ed5174637c3c607440c0996","version":"5ed5174637c3c607440c0a3c","project":"57336fd5a6a9c40e00e13a0b","createdAt":"2015-10-15T16:21:09.840Z","__v":0},"user":"5beb1b96bc2003003ecd645e","createdAt":"2020-02-28T20:31:39.386Z","__v":0,"parentDoc":null}

Payment API (XML)

Card/Wallet Transactions

PayPal Transactions

ACH/ECP Transactions

SEPA Direct Debit Transactions

Local Bank Transfer transactions

Batch Transactions

Refunds

Vaulted Shoppers

Subscriptions

Fraud Review

Marketplace

Wallets

Errors

Resources

Test Data & Codes

Guides & Tools

Mobile SDK

Fraud Errors

When a transaction triggers fraud rules, BlueSnap returns the following error:

Code
Name
Description

15011

FRAUD_DETECTED

The 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

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

Multiple fraud events
Single fraud event
<?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-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-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&nbspError 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
399 Bad Optn Invalid UDF UDF in the API request does not match a UDF in the Agent Web Console