Merchant Insights

Description

Merchant Insights provides deeper insights into your customers who have visited your physical or online stores. By analyzing the acquiring data, Merchant Insights can provide you with quality data about your customers, such as where they're from (country or postal codes), how many times and how often they shop with you, and the average spending power of their visits.

Get to know the details of your business performance and the customers shopping with you. Merchant Insights provides unique insights by adding an analytics layer to the acquiring data of all sales channels, and is available through our API, so you can get insights that fit your business and use case.

Combine Merchant Insights with Market Insights to benchmark against the general market or a specific industry. For example, you can find out the general trends in commerce in your industry, what types of customers are high spenders in your shop's area, where people are shopping in a specific area, and how you are performing in relation to current market benchmarks.

 

Resources

A list of resources bellow maps the API’s endpoint hierarchy. Find out more details on information pages made for each resource.

 

Filters

Name of the filter in parentheses.

  • Outlet location ZIP code (outlet_zipcode) - Filter by outlet zip code(s).

    • Use this filter to see only outlets located in a specific ZIP code. To filter on multiple ZIP codes, define this filter multiple times with different ZIP code values.

  • Outlet location municipality (outlet_municipality_code) - Filter by outlet municipality(ies).

    • Use this filter to see only outlets located in a specific municipality. To filter on multiple municipalities, define this filter multiple times with different municipality values.

  • Outlet location region (outlet_region_code) - Filter by outlet region(s).

    • Use this filter to see only outlets located in a specific region. To filter on multiple regions, define this filter multiple times with different region values.

  • Outlet location country (outlet_contry_a3) - Filter by outlet location country(ies).

    • Use this filter to see only outlets located in a specific country. To filter on multiple countries, define this filter multiple times with different country values.

  • Outlet location name (outlet_name) - Filter by part of outlet name.

    • Use this filter to see only outlets where part of the outlet name contains a specific input.

  • Outlet location ID (outlet_id) - Filter by outlet ID(s).

    • Use this filter to see only outlets with a specific ID. To filter on multiple IDs, define this filter multiple times with different ID values.

  • VAT code (vat_code) - Filter by company VAT code(s).

    • Use this filter to see only outlets belonging to a specific VAT code. To filter on multiple VAT codes, define this filter multiple times with different VAT code values.

  • Terminal ID (terminal_id) - Filter by terminal(s).

    • Use this filter to see only specific terminals belonging to a specific terminal ID. To filter on multiple terminals, define this filter multiple times with different terminal values.

  • Issuer country (issuer_country_a3) - Filter by issuer country(ies).

    • Use this filter to only focus on cards issued in a specific country. To filter on multiple countries, define this filter multiple times with different country values.

  • Domestic or International (domestic_international)- Filter by domestic or international card spending.

    • Use this filter to only focus on domestic or international card spending.

  • Estimated residence municipality (estimated_residence_municipality_code) - Filter by estimated residence municipality(ies) of consumers.

    • Use this filter to only focus on consumers estimated to live in a specific municipality. To filter on multiple estimated municipalities, define this filter multiple times with different municipality values.

  • Estimated residence region (estimated_residence_region_code) - Filter by estimated residence region(s) of consumers.

    • Use this filter to only focus on consumers estimated to live in a specific region. To filter on multiple estimated regions, define this filter multiple times with different region values. Don't put multiple region values into the single filter query parameter.

  • Estimated residence country (estimated_residence_country_a3)- Filter by estimated residence country(ies) of consumers.

    • Use this filter to only focus on consumers estimated to live in a specific country. To filter on multiple estimated countries, define this filter multiple times with different country values. Don't put multiple country values into the single filter query parameter.

  • Regional Local (is_regional_local) - Filter by regional or not regional local transactions.

    • Narrow your search by looking at regional local or not regional local (same as non-local) transactions. Regional local transactions correspond to the estimated residence region of a cardholder being the same as the region of the outlet where the transaction occurred.

  • Municipality Local (is_municipality_local) - Filter by municipality or not municipality local transactions.

    • Narrow your search by looking at municipality local or not municipality local transactions. Municipality local transactions correspond to when the estimated residence municipality of a card matches the municipality of a merchant, and not municipality local transactions are the case in which we estimate the cardholder to come from another municipality than the location of the merchant.

  • Business or Private (business_private) - Filter by business or private card spending.

    • Use this filter to only focus on business or private card spending.

  • Online or Physical (online_physical) - Filter by e-commerce (ECOM) or physical (POS) transactions

    • Use this filter to only focus on e-commerce or physical card spending.

  • Scheme (card_scheme) - Filter by card scheme(s).

    • Use this filter to only focus on specific card spending scheme. To filter on multiple schemes, define this filter multiple times with different scheme values.

  • Transaction type (is_refund) - Filter by refund or regular transactions.

    • Use this filter to only focus on refund or regular transactions.

  • Currency (currency) - Get turnover in specific currency.

    • Use this filter to get turnover results in a specific currency (Default : EUR)

  • Date range (date_range_start + date_range_end) - Get result for a specific date range.

    • Use this filter to only focus on transactions during a specific date range.

  • Hour range (hour_range_start + hour_range_end) - Get result for a specific hour range.

    • Use this filter to only focus on transactions during a specific hour range.

  • Week range (week_number_range_start + week_number_range_end) - Get result for a specific week range.

    • Use this filter to only focus on transactions during a specific week range.

  • Month range (month_range_start + month_range_end) - Get result for a specific month range.

    • Use this filter to only focus on transactions during a specific month range.

  • Year range (year_range_start + year_range_end) - Get result for a specific year range.

    • Use this filter to only focus on transactions during a specific year range.

  • Group By (group_by) - Group the response as wanted. See more in general

    • Use this filter to structure the response in as wanted. It's possible to group the response in many ways depending on resource.

 

Refunds

The fields that reflect the sum of transactions - number of transactions (number_of_transactions), number of cards (number_of_cards) and card turnover (card_turnover) - are affected by the presence of refunds. A method of calculating the sum has been chosen to accurately represent the value net of refunds. The calculations are as follows:
Card Turnover
  • The value of each refund is subtracted from the total value of transactions.
  • If the value of refunds exceeds the value of sales, the card turnover will be negative.
Number of transactions
  • Positive for refunds - each refund is counted as a transaction, adding one to the total number of transactions. This isn't the same as a reversal, which won't count as a transaction.
  • The number of transactions is thus always positive.
Number of cards
  • Negative for refunds - each refund is counted as one fewer card, subtracting one from the total number of cards.
  • The number of cards is always positive as an absolute value is taken.

 

Important notes on the data

  • The same cardholder can have multiple cards, so be aware that the number of cards doesn't equal the number of consumers.

  • Some weeks can be pay week one year and not the other year, which could lead to wrong conclusions on trends, so be aware of holidays, pay weeks, seasonality, incomplete periods, etc.

  • The area of residence of a card is only an estimate based on previous transaction patterns. Therefore, this should only be used as an indicator.

  • The residence area of some cards can't be estimated if they have had too few transactions in the past 6 months, so only the estimable cards are accounted for in this analysis.

  • If you are using the benchmarking resource, we unfortunately don't have all merchants as customers, so these numbers serve only as indicators of the whole market trend.

Go to API