Card Transactions

Description:
The average monthly transaction counts (swipes) a business receives from credit and debit card transactions, and a binary flag for whether there were any transactions in a given period.

See the Merchant Transaction Signals overview page for details about data sources, high-level methodology, and timeliness of this attribute.

Child attributes (and data file structure):

JSON Sample:

{
        "card_transactions": [
    {
            "end_date": "2020-08-31"
        "1m": {
                "start_date": "2020-08-01"
            "average_monthly_count": null,
            "present": true
        },
        "3m": {
                "start_date": "2020-06-01"
            "average_monthly_count": 140.25,
            "present": true
        },
        "12m": {
                "start_date": "2020-09-01"
            "average_monthly_count": 250.30,
            "present": true
        }
    }
  ]
}

Other notes and tips:

• average_monthly_count is not always an integer because Enigma applied a projection factor to the underlying panel transactions.
• card_transactions__1m__average_monthly_count is the estimated total number of card transactions in that month.
• To estimate the annual total number of card transactions of a business, multiply card_transactions__12m__average_monthly_count by 12. This equates to the trailing 12-month total from the end_date.
• To estimate the trailing 3 months number of card transactions from the end_date, multiply card_transactions__3m__average_monthly_count by 3.
• Enigma does not report transaction counts for a business in any periods where there were fewer than 30 total transactions in order to protect the privacy of consumers and card issuers. In the instance where Enigma estimates there were fewer than 30 transactions, the card transaction counts field will say “null.” However, you can still tell if it had any transactions from the card present field.
• It is common for a very small business to have a null for card_transactions__1m__average_monthly_count but not for card_transactions__12m__average_monthly_count, because the 12m average takes into account a significantly larger total number of transactions.
• When the child attributes card transactions average monthly count are null, you can use the card transactions presence child attribute to see if there were any transactions in that period
• You should specifically look if card_transactions__1m__presence is True
• If card_transactions__1m__average_monthly_amount is null but card_transactions__1m__presence is True, then the business did have a transaction in that month, but had fewer than 30 transactions
• If card_transactions__1m__average_monthly_amount is null but card_transactions__1m__presence is False, then the business did not have any transactions in that month
• If you are using the API, use the query parameter lookback_months to configure the number of months of historical data returned into the API response. Visit this section for more details.
• To estimate the monthly average transaction size, divide card revenue by card transactions. For example:
• Calculate the annual average transaction size by taking card_revenue__12m__average_monthly_amount divided by card_transactions__12m__average_monthly_count
• Calculate the quarterly average transaction size by taking card_revenue__3m__average_monthly_amount divided by card_transactions__3m__average_monthly_count
• Calculate the one month average transaction size by taking card_revenue__1m__average_monthly_amount divided by card_transactions__1m__average_monthly_count