Stripe is a global online payment platform that allows businesses to accept and process payments securely, effortlessly enabling e-commerce transactions. It provides tools for managing subscriptions, building marketplaces, and handling complex payment flows, making it a popular choice for businesses of all sizes.
Whether you’re building a marketplace, mobile app, online storefront or subscription service, Stripe has the features you need to accept payments online and within mobile apps.
With Databox, your most important Stripe KPIs will be transformed into meaningful insights and delivered to your mobile, Apple Watch, TV display or Slack channels. One of the key benefits of Databox is the ability to combine multiple data sources in one place.
Learn more about the integrations
Show more...
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:
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:
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.
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.
This error may occur if there is a large amount of data in the Stripe source and it needs to be synced into Databox. The error will appear on the Metric Insights or Forecasts page. Databox needs some time to fetch and process all the data from the source following pagination and rate limit rules set by Stripe API. When that time exceeds the timeouts for the Metric Insights and Forecasts query, the ‘We are experiencing some temporary issues. Please try again in a minute.’ error message will be displayed.
The workaround is to check the same metric insight or forecast later – up to a few hours, as Databox will continue the fetch the data in the background after the error message appears. Additional fetch duration optimization can be done in cases where the specific Stripe metric is already in use in the Databox account, as the past historic data will be stored in the Databox warehouse.
Usage Upgrades or downgrades are tracked when they actually happen. For example, if a user moved from PlanA ($59) to PlanB ($119) today, an upgrade of $60 will be tracked. The same logic will apply to downgrades.
In cases where the user would switch back and forth, every upgrade and downgrade would be tracked and would influence the upgrade or downgrade amount in Databox. Therefore, Databox suggests using the Calculated Metrics to track the Net New Upgrade or Downgrade values.
Below is an example of the MRR Upgrades metric and the same logic will apply for other Upgrades and Downgrades metrics.
Net New MRR Upgrades = MRR Upgrades – MRR Downgrades
Limitation To calculate upgrades, downgrades, and reactivations we use the /events endpoint. In accordance with the Stripe API documentation, Databox can collect only 30 days of historical data through this API endpoint. For example, if an upgrade occurred 31 days ago, it would not be pushed to and visible in Databox today.