Prepared by: Robert Caldwell rhcaldwell@g2llc.com
G2 Web Services User Guide
FraudFile
- Company Confidential - 2
FraudFile Overview
G2’s FraudFile helps you identify fraudulent merchants at boarding and persistently monitor your portfolio for fraudulent merchants to avoid losses, chargebacks, and other financial damage. The G2 FraudFile service analyzes your potential merchants at boarding against our exclusive G2 FraudFile database for links to fraudulent merchants. Importantly, the G2 FraudFile service also alerts you any time one of your existing or historical merchants is reported for fraud by any other participant in the program.
G2’s FraudFile program offers:
A FraudFile check at boarding that compares the prospective merchant to G2’s FraudFile database
Continuous monitoring of your merchant base for relationships to new FraudFile database submissions
Continuous monitoring of your submitted fraudulent merchants for re-entry to the payment system Secure and privacy-protected storage and usage of your fraud data for community benefit
The FraudFile program has the following process flows which are detailed throughout this document.
FraudFile Check at Boarding
Continuous Merchant Base Monitoring
Client Submit merchant data via email G2 Process merchant s against the G2 FraudFile database G2 Deliver FraudFile check results via email Client Review report and apply results to boarding decision Client Submit merchant base or use your Persistent Monthly Monitoring MB G2 Process merchants against the G2 FraudFile database Deliver Initial Report G2 Send Active Fraud Alerts whenever fraud relationships are discovered Client Review report and apply results existing merchant base Client Update merchant base each month as accounts change
Reported Fraudulent Merchants
G2 FraudFile Database:
The G2 FraudFile Database is comprised of the Reported Fraudulent Merchant (RFM) and the Potentially Fraudulent Merchant (PFM) data sets.
Reported Fraudulent Merchant. This set includes merchants that have been reported for committing fraud against acquirers that are members of FraudFile. Merchants associated with RFM records will be flagged as Fraud Type of “Fraudulent Merchant”.
Potentially Fraudulent Merchant. This set includes merchants that are potentially fraudulent, such as the following types:
o Inconsistent Representation. This type represents domain names that have more than one merchant account and more than one merchant name on file indicating potential application fraud.
o Fraudulent Merchant – No Loss. This type represents merchants that were terminated for fraudulent activity that did not result in a financial loss to the acquirer.
Client Submit history for Fraudulent Merchants via FraudFile Portal G2 Process merchants against all FraudFile merchant bases G2 Send Re-Entry Alerts when a related merchant is put through a FraudFile Check at boarding Client Submit newly discovered Fraudulent Merchants via FraudFile Portal
- Company Confidential - 4
FraudFile Check at Boarding
Submit Merchant DataYou may submit your merchant data by providing a spreadsheet via email to anti-fraud@g2llc.com. Upload a Boarding Request Spreadsheet:
To ensure that your submission is in the correct format, please use the FraudFile - Boarding Request Template (Excel file). Fill in as much data as possible as it will increase FraudFile’s ability to find connections between the prospective merchant and merchants in the FraudFile database.
When you are ready to upload, save the template using the naming convention “FraudFile - Boarding Request – [Org Name] – [YYYY-MM-DD]”.
Boarding Results
When complete, your boarding reports will be delivered to an email address of your choosing with the following pieces of information:
The data you submitted about the prospective merchant(s)
The fraudulent event data found to be related to the prospective merchant(s) including:
o Fraud Type
o Fraud Loss Amount
o Fraud Loss Currency
o Termination Date
The data fields that were matched between the prospective merchant(s) and the FraudFile database
1 2
Spreadsheet Best Practices: More than one merchant can be
submitted in the same request template (1).
If a single merchant has multiple URLs, such as Sonic Supplies, Inc., enter each URL on a separate line and copy the merchant data (2) so that each individual row is as complete as possible.
Continuous Merchant Base Monitoring
Submit Merchant DataYou may submit your merchant data by providing a spreadsheet via email to anti-fraud@g2llc.com. Upload a Merchant Base Spreadsheet:
To ensure that your submission is in the correct format, please use the FraudFile - Merchant Base Submission Template (Excel file). Fill in as much data as possible as it will increase FraudFile’s ability to find connections between your merchant base and merchants in the FraudFile database.
When you are ready to upload, save the template using the naming convention “FraudFile - Merchant Base Submission – [Client Name] – [YYYY-MM-DD]”.
If you would like to use the same merchant base as you are using for the G2 Persistent Monthly Monitoring solution, please let G2 Client Services know: clientservices@g2llc.com.
The first time you submit your merchant base, you will receive a FraudFile Initial Report that contains definitions of fraud types, a measurement of the completeness of your data set, and an initial fraud evaluation. Below are examples from an initial report:
1 2
Spreadsheet Best Practices: More than one merchant can be
submitted in the same request template (1).
If a single merchant has multiple URLs, such as Sonic Supplies, Inc., enter each URL on a separate line and copy the merchant data (2) so that each individual row is as complete as possible.
- Company Confidential - 6
Active Fraud Alerts:
After the Initial Report is delivered, your merchant base will be under continuous monitoring. Every time a merchant is added to the FraudFile database, it will be checked against your merchant base. If any relationships are found, you will be alerted immediately via an Active Fraud Alert email (see below). This alert identifies related merchants that may have fraudulent activity in progress, allowing for proactive review by your fraud team. Alerts will be delivered from the anti-fraud@g2llc.com email alias.
300 40 10,000
Fraud Types
Identified (by
merchant count)
Inconsistent Representati on Fraudulent Merchant $‐ $200,000 $400,000 $600,000 $800,000 $1,000,000 $1,200,000 1 2 3 4 5 6Total Fraud Loss
Amount
Reported Fraudulent Merchants
The upload of Reported Fraudulent Merchant data is handled through the G2 portal.
To access FraudFile, log into the G2 NetView Portal - http://www.g2netview.com using your Username (1) and Password (2). If you have forgotten your password you may have instructions to change it sent to your email address on file (3).
If you do not have a username or password to log into G2 NetView Portal, you may request a username and password from clientservices@g2llc.com
- Company Confidential - 8
On the FraudFile RFM upload page, the menu bar links allow you to return to Global Boarding (1), other G2 NetView Portal resources (2), or to exit the portal (3).
To submit your RFM data, begin by downloading the latest copy of the RFM template (4). Save the template to your local computer and enter your fraudulent merchant data. Please fill in as much data as possible as the more information you put the greater the benefit to FraudFile community.
To submit your file either select it through the file navigator (5) or by dragging and dropping the file into the dotted box (6).
If you have any questions about the data fields, the template, or the RFM File Submission page, please contact G2 Client Services (7).
Please use your standard internal fraud type names for submitting RFM records. G2 Client Services and FraudFile teams will work with you to understand the meaning of each type you submit. G2 will evaluate your records against the FraudFile program definition of fraud (below) to determine which records should be used for the RFM and which should be used for the PFM.
The objective of this definition is to promote a very high quality of fraud data in the Reported Fraudulent Merchant set, with meaning to all FraudFile members. A merchant must meet the following criteria in order to be submitted to the Reported Fraudulent Merchant set as Fraud Type of “Fraudulent Merchant”:
Submitting acquirer must be confident of and have evidence to support that the merchant perpetrated fraud from which it received financial benefit
The merchant was terminated as a result of the fraudulent activity The acquirer suffered financial loss because of the fraudulent activity The acquirer is prepared to defend the above criteria
The merchant meets the definition of a bust-out merchant stated in MasterCard QMAP
Re-Entry Alerts:
After the initial RFM history is delivered, it will be under continuous monitoring. Every time a merchant is put through a FraudFile check at boarding, it will be checked against your RFM records in the FraudFile database. If any relationships are found, you will be alerted immediately via a Re-Entry Alert email (see below).
This alert identifies related merchants that are applying for merchant accounts at other FraudFile member organizations. Alerts will be delivered from the anti-fraud@g2llc.com email alias.