{"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 one of the following errors:\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\": \"This 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 \"1-0\": \"15011\",\n \"1-1\": \"FRAUD_ERROR\",\n \"1-2\": \"This error can indicate an invalid card or an invalid site is being used for the transaction. \\n\\nThis fraud error message includes a `fraud-events` resource containing an ID for the fraud event.\"\n },\n \"cols\": 3,\n \"rows\": 2\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-transaction-id>DSYK0G9YPJYS</fraud-transaction-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-transaction-id>DSYK0G9YPJYS</fraud-transaction-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 RIS Response Key | Kount Error | 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\n332 | Bad Card | Invalid Card | Card used in the API request is not valid","updates":[],"order":4,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"61a5208deadb750070998f31","project":"57336fd5a6a9c40e00e13a0b","version":{"version":"8976-XML","version_clean":"8976.0.0-XML","codename":"3.40 Release","is_stable":false,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["61a5208deadb750070998e87","61a5208deadb750070998e88","61a5208deadb750070998e89","61a5208deadb750070998e8a","61a5208deadb750070998e8b","61a5208deadb750070998e8c","61a5208deadb750070998e8d","61a5208deadb750070998e8e","61a5208deadb750070998e8f","61a5208deadb750070998e90","61a5208deadb750070998e91","61a5208deadb750070998e92","61a5208deadb750070998e93","61a5208deadb750070998e94","61a5208deadb750070998e95","61a5208deadb750070998e96","61a5208deadb750070998e97","61a5208deadb750070998e98","61a5208deadb750070998e99","61a5208deadb750070998e9a"],"_id":"61a5208deadb750070998f48","project":"57336fd5a6a9c40e00e13a0b","__v":0,"forked_from":"60fed269718a45001c25b4a0","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":15,"from_sync":false,"reference":false,"_id":"61a5208deadb750070998e92","version":"61a5208deadb750070998f48","project":"57336fd5a6a9c40e00e13a0b","createdAt":"2015-10-15T16:21:09.840Z","__v":0},"user":"5beb1b96bc2003003ecd645e","createdAt":"2020-02-28T20:31:39.386Z","__v":0,"parentDoc":null}
Fraud Errors
When a transaction triggers fraud rules, BlueSnap returns one of the following errors:
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
<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>
<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 |