Skip to main content

Reports

The Fraugster Reports provides various pre-configured metrics that allow you to investigate trends and analyze your business performance. Visual diagrams and charts come directly from the data in the Fraugster Engine and get updated in real time.

Alter the report filters to change the information displayed in the report. Two filters are also available:

  • Date range
  • Merchant
info
  • Use to pin the date and merchant filters across all pages of your account where the filters apply. For the merchant filter, the pin becomes visible when you select at least one merchant.
  • Fraugster stores the report data for 1 year.
  • The data for each day is defined as account activity that takes place between 12:00am UTC and 11:59pm UTC.

Use Send report to generate a report and send it to an email address.

Use Schedule report to automatically send reports to selected email addresses on a daily, weekly, monthly, or quarterly basis. The report goes out for the fist time on the day you schedule it. To schedule a report, go to ReportsSchedule in the navigation panel on the left.

Fraugster reports have the following sections:

  • Final approval rate
  • Transactions overview
  • Approved transactions
  • Declined transactions
  • Fraud cases

Final approval rate

The final approval rate is calculated based on the status of the transaction regardless of Fraugster’s decision. That is, all transactions that received the status approved in the sync status update via the API are considered when calculating your final approval rate.

See also Final approval rate calculation for more details.

Final approval rate in reports

Transactions overview

In the Transactions overview chart you see the traffic trends that allow you to compare the minimum and maximum values for a given date range.

Transactions overview

Approved transactions

The box Total transactions represents all transactions received by the Fraugster API.

The box Approved by Fraugster includes all incoming transactions that Fraugster approved.

The information in the Final approved box is based on the status of the transactions regardless of Fraugster’s decision. That is, all transactions that received the status approved in the sync status update via the API are counted in.

Approved transactions

Declined transactions

Declined transactions are divided into 3 different sections on the page:

  • Decline: Fraugster vs. Issuer (comparison in the decline rate by Fraugster and the Issuer)
  • Decline distribution by the shipping country
  • Decline overview

Decline: Fraugster vs. Issuer

The decline rates divide into two categories:

  • Fraugster declined refers to the transactions declined by Fraugster, either by the Fraugster Engine (for Chargeback Protection and Fraud Decisions as a Service users) or the rules you created (for Fraud Management SaaS users). Therefore, the transactions contributing to this KPI are transactions that receive "fraugster_approved":0 in the API response.

  • Issuer declined refers to transactions declined by the issuer or a different payment method following Fraugster’s decision ("fraugster_approved":0).

    Read more on the API response in the API documentation.

See also Declined transactions calculation for more details.

Value and count graphs are presented as stack bars that show a total of declined transactions after both Fraugster and the Issuer declined. Value (%) and count (%) graphs the show distribution between Fraugster and Issuer declines, where 100% represents the total number of declined transactions.

Declined transactions trend

Decline distribution by the shipping country

In this section, you see the distribution of declined transactions by the shipping country. In case when the shipping country was not provided, you see n/a.

See also Decline distribution calculation for more information.

Decline distribution per shipping country

Fraud cases

To calculate fraud cases, Fraugster takes into account known fraud cases only. That is, Fraugster considers only approved transactions that turned out to be fraudulent. Declined transactions are not defined as fraudulent transactions and therefore they are not included in the fraud rate calculation.

The fraud cases are divided as follows:

  • Fraud cases by reporting date
  • Fraud cases by transaction date

See also Fraud rate calculation for more details.

Fraud cases