Stripe
Dashboard and Reporting Software

Databox is using Stripe API for Data Source connection and for fetching the metrics data. Authentication is done by a Restricted API key with ‘Read Only’ access selected, as explained in the ‘How to connect Stripe to Databox‘ article. Databox is a Verified Technology Partner listed in the Stripe Partner Directory.

Some users may experience long loading times for Stripe metrics in Databox when:

• the metric is first used in Databox,
• the Date Range is changed for the metric,
• accessing Advanced Settings,
• in the Calculated Metrics preview
• reviewing the Performance Screen.

This behaviour can occur in cases when there are large amounts of data present in the Stripe account. In such cases, long loading times are expected.
Databox needs some time to fetch and process all the data from the source due to the pagination and rate limit rules set by Stripe API. In some cases, depending on the amount of data in the Stripe account, it could take up to several hours for the metrics values to load.

If your subscriptions contain multiple subscription items and a discount is applied to a subscription, this will affect the related metrics in such a way that the total value of those metrics will be higher than the total value of equivalent non-dimensional standard metric, as subscription discounts cannot be divided among multiple subscription items.

Example for ‘MRR by Plan Name’:
Each subscription has subscription items applied (products/plans etc.). When a discount is applied, it is valid across all items/products. For example, there is a subscription with the following items:

• Starter: 6x 50$
• Enterprise: 1x 250$
• 15-minute syncing feature: 1x 100$

All items above will be summed up (650$) and will count towards the total MRR (also for MRR by Plan Name metric).
Discounts can be applied only to the whole subscription, not one specific item. This means if there is s $200 discount applied to the subscription, we cannot subtract this amount from items, since there is no ‘ratio’ across subscription items. In this case, we will subtract $200 from the root MRR value ($650 – $200 = $450), while the dimensions SUM of ‘MRR by Plan Name’ will stay 650$.

This limitation applies to the following metrics:

MRR by Plan Name
New MRR by Plan Name
MRR (excl. Canceled Subscriptions) by Plan Name
Churned MRR by Plan Name
Churned MRR (Delinquent) by Plan Name
ARR by Plan Name
New ARR by Plan Name
Churned ARR by Plan Name
ARR (excl. Canceled Subscriptions) by Plan Name

If there are several purchases in different currencies in Stripe, Stripe converts and sums together those values in Stripe using estimated conversion rates – as a result data is displayed in one currency in the Stripe User Interface.
However, the Stripe API is returning raw data in the original currencies and does not include estimated currency conversions. Hence, the users who have multiple-currencies purchases enabled in their Stripe account will notice the discrepancy when comparing the Revenue-related metrics to Databox.

While the exact number as in the Stripe User Interface will not be possible to display in Databox, the workaround solution is to use calculated metrics in Databox to convert the values into one currency and sum them together.

When you first use a Stripe metric in Databox, 12 months of historical data is initially synced for all metrics with the exception of charge-related metrics and metrics of current or calculated type.

When Charge metrics are first used in Databox, 24 months of historical data is available for them. Charge metrics are:

Payments,
Gross Volume,
Successful Charges,
Failed Charges.

Metrics of Current and Calculated metric types, such as Customers and Available Balance, will have data available in Databox from the day when they are first used in the Databox app, but not for dates prior to that. The metric type information is available under the ‘Tech details’ tab of the metric description in the Metric library.

For all Stripe metrics, due to the pagination limitation of Stripe integration, the maximum number of fetched charges, subscriptions, refunds, customers, transactions, invoices, etc. is 100,000 (100k) for the selected Date Range.

Data discrepancies between Databox and Stripe’s User Interface may occur for Stripe metrics. This is due to a difference in how Databox calculates data synced from Stripe’s API vs. how data is calculated in the Stripe User Interface.

The description of each Stripe metric and how they are calculated is specified in this article.

For all ‘by Plan Name’ dimensional Stripe metrics, Databox shows the plan nickname (as received from the API response) in place of the Plan Name.
If the nickname is missing in the Stripe account for the specific plan or all plans, Databox will instead show the Plan ID, as mentioned in the help article.

Hence, it is recommended to set the nicknames for plans in the Stripe account.