Anomaly reporting from a receipt ​

Before reading this, make sure to know how to get receipts from our API.

How to run a fraud detection ? ​

You don't have anything to do for the anomaly detection to work ! It will be triggered automatically when the receipt is sent for analysis.

The only requirement you need to look for duplicates is that the receipt must be attached to a campaign and / or an endpoint.

How do I get the result ? ​

If you have the right plan, you will be able to see the result in the usual document response, in the anomalyReport field. It will tell you which anomalies were found, and which receipts are potential duplicates of it.

Here is the content structure of the field :

{
  "anomalyReport": {
    "flags": [
      "SAME_SHOP_SAME_MOMENT",
      "EXISTING_PRODUCT_LIST",
      "HIGH_GLOBAL_CONTENT_SIMILARITY"
    ],
    "potentialDuplicateReceipts": [
      {
        "uid": "e67c9571-47a7-42cd-8439-c94bc9d5e478",
        "flags": [
          "SAME_SHOP_SAME_MOMENT",
          "EXISTING_PRODUCT_LIST",
          "HIGH_GLOBAL_CONTENT_SIMILARITY"
        ]
      }
    ]
  }
}

{
  "anomalyReport": {
    "flags": [
      "SAME_SHOP_SAME_MOMENT",
      "EXISTING_PRODUCT_LIST",
      "HIGH_GLOBAL_CONTENT_SIMILARITY"
    ],
    "potentialDuplicateReceipts": [
      {
        "uid": "e67c9571-47a7-42cd-8439-c94bc9d5e478",
        "flags": [
          "SAME_SHOP_SAME_MOMENT",
          "EXISTING_PRODUCT_LIST",
          "HIGH_GLOBAL_CONTENT_SIMILARITY"
        ]
      }
    ]
  }
}

The flags field at the root of the anomalyReport contains all the flags that were detected for this receipt.

The potentialDuplicateReceipts field stores a list of receipts that are potential duplicates. For each object of this list, you will find the uid of the potential duplicate receipt, as well as the flags that were found for this receipt in particular.