INTEGRATION
CHARGES
DISPUTES & FRAUD
Fraud Notifications
Before a Charge is disputed for fraud reasons, the card networks mandate issuers to begin by filing a fraud notification. We provide acquirers the means to get notified when a charge has been flagged as possibly fraudulent. This information can be used to act before a fraudulent Charge is converted to a chargeback, decreasing the amount of total fraud disputes and preventing the associated operational burden.
For Visa, this is done by means of TC40 fraud notification files and for Mastercard trough the SAFE system. We receives these notifications and makes them accessible to clients through the API. It is the responsibility of the client to monitor and act upon fraud notifications appropriately.
Get Notified about Incoming Fraud Notifications
Event notifications are sent to a URL specified by the customer when creating an Event Subscription webhook with a specified source. If a Fraud Event subscription is created, events are emitted in case a new Fraud Notification object is created (inbound from the Issuer). A Fraud Event Notification contains both the Fraud Notification key
and the Charge key
. Create an Event Subscription for Fraud Notifications by doing the following request to the Create Event Subscription endpoint:
For more details please refer to the Event Notifications section.
Retrieve Fraud Notifications
The Fraud Notification object is generated when a fraudulent charge has been reported to the card networks. A Fraud Notification is directly related to a single transaction (if this transaction was processed by Silverflow it will therefore also be related to a Charge) and has a unique Fraud Notification key
. Retrieve these Fraud Notifications from the API by using the Get Fraud Notifications endpoint. Below is an example response:
This API response provides critical information regarding a fraudulent transaction, enabling businesses to identify, investigate, and take appropriate action to mitigate risks associated with fraudulent activities.
Fraud Monitoring
Certain card networks require acquirers to keep track of the number of fraud notifications (as opposed to monitoring fraud chargebacks). If certain fraud notifications ratios exceed a threshold, the schemes will fine the acquirer. Silverflow provides acquirers access to a Fraud Notification Report Endpoint to monitor the amount of Fraud Notifications.
Note: the fraud endpoints on the Silverflow API can be used to manage fraud notifications assuming that the user has access to and experience with the card network rules regarding fraud notifications. Please refer to the card network manuals for more information.