Introduction to Chargebacks

Analyse if the customer had chargebacks because their account was not funded.

This report is appropriate for B2B and B2C use cases.

What it solves

To find out how reliable a customer is, chargebacks are a good indication. Through this information, it is possible to find out whether the customer is keeping track of his finances and regularly meeting his financial obligations. Does it happen that direct debits cannot be executed because there is not enough money in the account – and if so, how often?

Chargeback Report

The analysis shows returned direct debits that occurred due to insufficient funds or that were initiated by the end user.

Chargeback transactions are split into:

CHARGEBACKS_ACTIVE (actual chargeback transactions of the account)
CHARGEBACKS_PASSIVE (chargeback transactions for 3rd parties, like customers)
CHARGEBACKS_OBJECTION_INCOME (an objection against the validity of a chargeback)
CHARGEBACKS_OBJECTION_SPENDING (if a company, an objection against the validity of a chargeback of the 3rd parties, like customers against the company)
CHARGEBACKS and CHARGEBACK_FEE (transactions that do not have enough information to be considered in the other categories)

In addition, further reports can be created based on an initial report. These continuous reports can then be provided with triggers that always compare the values of the previous report with the current one and look for defined changes.

This is useful if you have access to the client's account data over a longer period of time.

It is important that not only days, but ideally months are considered.

Aggregations

A Chargeback Report can be generated as an Aggregation with the following query:

JSON

{
  "aggregations": [
    {
      "alias": "Chargebacks",
      "includeLabelGroup": [
        "CHARGEBACKS_ACTIVE"
      ]
    }, 
    {
      "alias": "ChargebacksPassive",
      "includeLabelGroup": [
        "CHARGEBACKS_PASSIVE"
      ]
    },
    {
      "alias": "ChargebacksObjection",
      "includeLabelGroup": [
        "CHARGEBACKS_OBJECTION_INCOME"
      ]
    },
    {
      "alias": "ChargebacksObjectionPassive",
      "includeLabelGroup": [
        "CHARGEBACKS_OBJECTION_SPENDING"
      ]
    },
    {
      "alias": "ChargebacksUndefined",
      "includeLabelGroup": [
        "CHARGEBACKS",
        "CHARGEBACK_FEE"
      ]
    }
  ]
}

Used data fields

All transactions of the customer are used for this purpose. This includes data like IBAN, account holder name, counterpart name, purpose, amount, and so on.

The report response itself is divided into the following sections.

Main Section

The main part of the report can be found at $.reports.chargebacks and the type will be CHARGEBACKS.

This gives you a quick overview of the transactions used in the report through aggregated values that can serve as a summary.

A full API schema can be seen here: https://docs.finapi.io/?product=di#get-/cases/-caseId-/reports

Field	Description	Mandatory
`creationDate`	Timestamp of when the report was created, in the format '`YYYY-MM-DD HH:MM:SS.SSS`' (CET Europe / Berlin).	yes
`caseId`	ID of the case in which the report was created.	yes
`type`	Defines the type of the report.	yes
`startDate`	Timestamp of the start date of the reporting period under review in the format '`YYYY-MM-DD HH:MM:SS.SSS`' (CET Europe / Berlin).	no
`endDate`	Timestamp of the end date of the reporting period under review in the format '`YYYY-MM-DD HH:MM:SS.SSS`' (CET Europe / Berlin).	no
`daysOfReport`	The number of full days, that the reporting period under review contains.	no
`transactionsStartDate`	Timestamp of the date, when user's first transaction took place in the report period under review in the format '`YYYY-MM-DD HH:MM:SS.SSS`' (CET Europe / Berlin). This field takes into consideration all the transactions of the user, irrespectively of the assigned to them label.	no
`totalTransactionsCount`	The number of the user transactions, that took place in the report period under review. This field takes into consideration all the transactions of the user, irrespectively of the assigned to them label.	no
`countIncomeTransactions`	The total count of positive transactions in the report.	yes
`countSpendingTransactions`	The total count of negative transactions in the report.	yes
`totalIncome`	The total income.	yes
`totalSpending`	The total spending.	yes
`totalBalance`	The total balance.	yes
`accountData`	List of accounts-related data with the relevant transactions information.	no
`childReports`	List of reports, created automatically with the specified frequency (defined by `interval` and `intervalPeriod`) once the parent report is defined as a continuous one.	no

Account Data Section

The account data section can be found under the accountData field.
It contains data about the account at the first level.
If more than one account is included in the report, they will be displayed individually in the list.

Field	Description	Mandatory
`bankName`	Name of the bank.	yes
`bankId`	Unique identifier of the Bank, generated by finAPI.	yes
`accountIban`	IBAN of the bank account.	no
`accountId`	Unique identifier of the bank account belonging to the imported bank connection.	no
`transactionsStartDate`	Date of the account first transaction, regardless of the report period under review, in the format '`YYYY-MM-DD`' (CET Europe / Berlin). This field takes into consideration all the transactions of the account, irrespectively of the assigned to them label.
`accountType`	Type of the account. Can be: `CHECKING` `SAVINGS` `CREDITCARD` `SECURITY` `LOAN` `POCKET` `MEMBERSHIP` `BUILDING_SAVINGS`
`transactions`	List of transactions related to the chosen report type.	no

Transactions Section

This section displays the transactions used in the report and can be found under the accountData element in the field transactions.
Please note that this list may be very long, especially for business accounts.

Depending on what the report is used for, the transactions can be retrieved for later review or documentation, or they can be turned off. The latter would be the case, for example, if you only want to do a quick check of the overall data and do not need any details.

If transactions are not of interest, you can also disable this section by giving the query parameter withTransactions=false to the report.

The transactions include the following values.

Field	Description	Mandatory
`valueDate`	Value date in the format '`YYYY-MM-DD HH:MM:SS`' (CET Europe / Berlin).	yes
`bankBookingDate`	Bank booking date in the format '`YYYY-MM-DD HH:MM:SS`' (CET Europe / Berlin).	yes
`amount`	Transaction amount.	yes
`purpose`	Transaction purpose.	no
`transactionId`	Transaction UUID.	no
`counterpartName`	Counterpart name.	no
`counterpartAccountNumber`	Counterpart account number.	no
`counterpartIban`	Counterpart IBAN.	no
`counterpartBlz`	Counterpart BLZ.	no
`counterpartBic`	Counterpart BIC.	no
`counterpartBankName`	Counterpart bank name.	no
`labels`	A list of labels assigned by the system. This does not contain the complete label structure in the sense of level of detail.	no
`overdraftInformation`	Extracted details for transactions with related to overdraft interests. It includes an object that contains fields such as the overdraft amount and the period of the overdraft.	no
`seizureInformation`	Extracted details for transactions with related to wage seizure. It contains the seizure amount extracted from the purpose, when possible.	no
`chargebackInformation`	Chargeback amount extracted from the transaction’s purpose. When it is possible to extract the chargeback amount, the extracted value is used in the calculations of the other fields and monthly objects. When extraction is not possible, the amount of the transaction is used instead.

Monthly Data (Aggregations)

Monthly Data are aggregations generated over the report period for specific sub-aspects of the report.
These are reported on a monthly basis and made available as a summary.

Field

Description

Mandatory

completeMonths

This field contains a list of months for which finAPI has complete records available. This automatically means that the first and the last month of the report period are omitted from the list.

no

monthlyData

Monthly aggregations of various data are listed under this field. These reflect the monthly development of certain criteria in the transactions.

The month, the value, the number of transactions, and the list of transaction ids behind it are always indicated.

If showOnlyCompleteMonths=false, the list of months is calculated between transactionsStartDate of the report and endDate of the report, hence both complete and incomplete months are included.

If showOnlyCompleteMonths=true, only the list of complete months between transactionsStartDate of the report and endDate of the report, is included.

All accounts are taken into consideration for the monthly objects.

no

Subelements of Monthly Data

This section describes the subfields of the Monthly Data section that can appear in the report.

Additionally, aggregations are provided for the sections behind the subelement, which include values such as totalMonthlyAmounts, minTotalMonthlyAmount, maxTotalMonthlyAmount, averageTotalMonthlyAmount,medianTotalMonthlyAmount,totalTransactionsCount and totalTransactionsAmount.

Here we take into consideration the data from both complete and incomplete months inside the report period under review.

Field	Description	Mandatory
`chargebacks`	Chargeback-related amounts, organized by months.	yes
`chargebacksPassive`	Chargebacks transactions for 3rd parties, like customers, organized by months.	no
`chargebacksObjection`	Objections against the validity of a chargeback, organized by months.	no
`chargebacksObjectionPassive`	For a company - objections against the validity of a chargeback of the 3rd parties, like customers against the company, organized by months.	no
`chargebacksUndefined`	Possible chargebacks transactions: that do not have enough information to be considered in the other categories, organized by months.	no