Fraud events
Fraud event: an occurrence that is suspected or confirmed to be fraudulent.
Members and their users can submit data related to these fraud events, called contributions, to help identify and prevent future fraudulent activities. By sharing information and collaborating with other participants on the Exchange, contributors can help create a more secure and trustworthy ecosystem that is resistant to fraud and other types of malicious activities.
Types of fraud events
Any given fraud event is of one of the following types. The API takes and returns the name in the first column, spelled exactly as shown:
| Name in the API | Fraud type | Description |
|---|---|---|
Wangiri | Wangiri | The "missed call scam". Usually detected by a fraud management system, which uploads the details of the event, such as the phone number and the country codes of the parties. |
IRSF | International revenue share fraud | Fraud that inflates the volume of international traffic to a destination to generate revenue. Usually detected from unusual call patterns. |
StolenDevice | Stolen device | Any fraud that involves a stolen device. Usually reported by customers or law enforcement. |
IPFraud | IP fraud | Any fraud that involves a specific IP address. Usually detected by behavioural analysis, geolocation checks and the rate of actions of an address. |
SMSA2P | SMS A2P | Fraud that reroutes SMS through SIM boxes and disguises them as legitimate messages. Usually spotted by operators who monitor traffic patterns, contents and sending rates of a phone number. |
Flashcall | Flash call | The use of missed voice calls to deliver one-time passwords that are otherwise charged as A2P SMS. It bypasses termination charges for A2P SMS. |
Scam | Scam | Fraud that deceives users through social engineering, such as phishing messages or emails, using phone numbers, email addresses or URLs. Usually identified from unusual transaction patterns and user reports. |
Fraud event data model
Every fraud event that is submitted and stored on the Exchange adheres to the following model:
| Data | Description |
|---|---|
| Fraud Identifier | The main identifier of the fraud event. Could be one of the following:
|
| Fraud Type | The type of the fraud event. Could be one of the following:
|
| Event Origination | The two-letter code of the country the fraud event originated from (Alpha-2, ISO 3166). |
| Event Destination | The two-letter code of the country the fraud event was identified as such (Alpha-2, ISO 3166). |
| Event Contributor | The peerId of the company that contributed the data. |
| Event Status | The status of the event at the time of observing. Could be one of the following:
|
| Event Expiry Date | The exact time and date until which the event is considered relevant: 60 days after it was submitted, for every fraud type. |
| Event Timestamp | The exact time and date of when the event was submitted. |
| Event Flag Timestamp | The exact time and date of when a contribution has been flagged. Only stored if a contribution has been flagged at the time of observing. |
| Event Flagger | The unique ID of the peer that flagged the data. Only stored if a contribution has been flagged at the time of observing. |
| Privileged Status | The definition of whether a contribution is privileged. |
INFO
For a more technical outlook on what data related to any given fraud event is stored on the Exchange, see Contributions: API data structures.