Skip to content

Stripe analytics across your SaaS projects

Use Naarva to understand Stripe revenue and subscriptions alongside the companies, projects and operating costs in your portfolio. Assign source data to the right product before comparing performance.

What the connection brings into Naarva

The Stripe integration reads products, prices, subscriptions, payments and refunds. Naarva normalizes those records into its reporting model while preserving the original currency and source identity.

Successful subscription and one-time payments can contribute to revenue. Unpaid invoices, failed payments and test-mode transactions do not become collected revenue. When reliable tax information is available it is used; uncertain tax treatment stays visible as a limitation.

This connection imports the business data you want to analyze. It is separate from the Stripe subscription used to pay for Naarva itself.

Connect and assign your products

  1. Sign in as a verified workspace Owner or Admin and open Integrations.
  2. Choose Stripe and complete the connection flow shown in Naarva.
  3. Run or wait for the initial synchronization, then review its status and available source history.
  4. Assign Stripe products to the corresponding Naarva projects. Use supported price-level mappings where you need a more specific assignment.
  5. Review unassigned data and confirm that the selected currency and period match the comparison you want to make.

A Stripe account can contain several products. Company and project structure should reflect your businesses; it does not need to be identical to the way a payment account was originally organized. The portfolio analytics guide explains how the reporting levels fit together.

Revenue and MRR answer different questions

For an illustrative €120 annual subscription, a successful €120 payment belongs to revenue in the collection period, before any applicable adjustments. Its monthly recurring value is €10 when the full amount is an eligible fixed recurring charge, with no tax or discount adjustment required.

A one-time purchase can increase revenue without increasing MRR. A trial can appear in subscription counts without contributing paid MRR. A refund reduces revenue in its recorded period rather than reducing MRR by the refund amount.

ARR is twelve times normalized MRR. It is a recurring run rate, not a forecast or a claim that twelve months of payments have already been collected. See the complete metric definitions for status, coverage and currency rules.

Use source status to understand the limits

Synchronization and source coverage are related but different. A successful update does not guarantee that older transactions are present or that historical MRR can be reconstructed. Naarva keeps incomplete coverage distinct from a confirmed zero.

Original currencies remain separate across projects and companies. When comparing two projects, choose equivalent periods and the same currency. A workspace timezone determines where a reporting day or month begins and ends.

Changes to source records and assignments can change the resulting reports. Review synchronization warnings and unassigned items before treating a portfolio total as complete.

Add the expenses Stripe does not describe

Enter recurring and one-time project costs to see estimated profit alongside revenue. This provides operating context for hosting, tools and other expenses you choose to record. It does not replace accounting or automatically establish that every expense has been captured.

Stripe is included in the standard Naarva subscription. The price follows active project count, not revenue or transaction volume. Compare the available data sources if your portfolio also includes Paddle Billing or mobile subscriptions managed through RevenueCat.