Event Code 105 - Payment Manual Review Outcome

📘
Note
You must be onboarded for Scam Transaction Monitoring, and have set up scam alerts, to use this event code. For more information, speak to your Account Manager.

The 105 event code enables you to action your pending payments based on the outcome of a manual review in Fraud Transaction Monitoring. When the webhook service has been successfully set up, notifications will be sent when:

There is a payment event only. For example, a non-card event
An incident is reviewed (one message per alert reviewed) and set to Risk or No Risk

See the below example of a webhook for a 105 event code.

{
  "programManagerCode" : "TRD",  
  "productId": 12345,
  "events": [105],
  "webhookStatus": "active",  
  "config": {
    "url": "https://client_domain.com/webhook",
    "customHeaders": {
      "header1": "value_1",
      "header2": "value_2"
    }
  }
}

After the webhook has been successfully set up, when a potential scam has been flagged, a notification response is sent from the Event Delivery Service to the URL specified in the webhook. See the below example of a response.

{
  "context": {
    "programManagerId": 16,
    "eventCode": 105,
    "eventVersion": "v1",
    "notificationTime": "2024-11-24T11:20:28Z",
  },
  "payload": 
   {
      "transactionId": "123412341234",
      "eventid": "55221979-a4cd-4d7a-bb0c-1b3f0b7cb92c",
      "reviewStatus": "no-risk",
      "reviewDate": "2024-11-24T09:15:10.086Z"
   },
  "messageHeaders": {
    "schemaId": 1
  }
}

The below table describes each of the fields included in the notification response.

Field	Description
context	Object that contains the context of the notification, such as the event code.
notificationId	Unique identifier of the notification.
eventCode	The event code. In this case, the event code is 105.
eventVersion	The event version.
notificationTime	When the notification was created. Time in the UTC format of 'yyyy-MM-ddTHH:mm:ssZ'.
payload	Object that contains the payload of the notification, which is specific to the event code.
transactionId	The unique identifier for the transaction. It can be used to link different messages as part of the same transaction (for example, payment request and confirmation messages).
eventid	The unique reference for the event. This reference string should be fully unique across the entire system.
reviewStatus	The review of the potential scam from Scam Transaction Monitoring. For example, "no-risk".
reviewDate	When an analyst reviewed the potential scam in Scam Transaction Monitoring.
messageHeaders	Object containing the message headers.
schemaId	The schema identifier. This is always `1`. Note that this is a Scam Transaction Monitoring config setting passed on in the response, and no client action is needed.

Updated 4 days ago