What is Verified MRR?
On Verifii, Verified MRR is a payment-backed revenue baseline calculated from completed customer payments and captured charges across an authenticated trailing 30-day window from connected Stripe and Razorpay accounts. This verification metric provides objective evidence of recent payment activity rather than relying on self-reported figures or manual screenshots.
Verified MRR on Verifii is a verification-specific metric reflecting a trailing 30-day payment baseline. It should not be interpreted as an accounting-standard calculation of contractual recurring revenue, a statutory financial audit, or a formal GAAP revenue recognition statement.
The Verified MRR Concept
In software and technology ecosystems, founders frequently share revenue figures to establish commercial credibility. Traditional Monthly Recurring Revenue (MRR) is self-reported, leaving figures susceptible to manual errors, selective reporting, or unverified claims. Verified MRR addresses this by anchoring the metric to direct, authenticated payment processor records from supported providers like Stripe and Razorpay. Rather than evaluating self-submitted spreadsheets or dashboard screenshots, the verification engine queries completed customer transactions and captured charges across an active trailing 30-day window. This produces an evidence-backed financial baseline reflecting actual customer payments received during that period. By using restricted read-only permissions and keeping proprietary customer data private, Verified MRR gives founders a dependable way to share proof of recent revenue volume with prospective customers, partners, and the broader startup community.
What Verified MRR means on Verifii
When a startup displays a Verified MRR figure on Verifii, it represents an objective, automated summary of completed transaction activity:
Payment-Backed Data
Extracted directly from connected payment providers via authenticated API connections.
Trailing 30-Day Window
Reflects completed payment volume received over the trailing 30 days.
Read-Only Security
Calculated without fund-transfer permissions or access to sensitive card details.
How Verifii calculates the metric
The calculation of Verified MRR follows an automated sequence based on live provider data:
Connect Supported Payment Provider
The founder establishes an authenticated connection to Stripe or Razorpay using restricted read-only credentials or standard OAuth permissions.
Retrieve Relevant Payment Records
The verification engine queries recent transaction records, completed charges, and payment entries directly from the connected provider API.
Select Completed/Captured Transactions
The system filters records to include only successful, captured charges and completed payment items, excluding failed authorizations and uncaptured transactions.
Aggregate the Trailing 30-Day Baseline
Total captured transaction amounts within the trailing 30-day window are summed to establish the startup's current verified revenue volume.
Normalize and Publish Verified Metric
Amounts are normalized into the platform's standard display currency and published to the startup's verified public profile and the leaderboard.
Understanding the calculation scope
To evaluate Verified MRR accurately, it is essential to understand both what the current implementation includes and its structural boundaries:
What is Included
- •Completed subscription payments collected in the 30-day window.
- •One-time captured payments and charges occurring in the 30-day window.
- •Multi-provider transaction aggregation across connected Stripe and Razorpay accounts.
- •Currency normalization into the platform's standard display format.
What is NOT Normalized
- •Annual contracts are not divided into 12 monthly accrual portions.
- •Billing intervals (quarterly, semi-annual) are not interval-normalized.
- •One-time charges are not automatically separated from subscription invoices.
- •Subscription contract proration and mid-term upgrades are not calculated.
- •Does not perform accrual accounting or formal GAAP revenue recognition.
Verified MRR vs. Self-Reported MRR
Self-reported revenue figures rely on manual disclosures, whereas Verified MRR relies on programmatic payment-provider data:
| Dimension | Verifii Verified MRR | Self-Reported MRR |
|---|---|---|
| Evidence Source | Connected payment-provider API records | Self-submitted text or screenshots |
| Payment Gateway Connection | Authenticated read-only provider integration | None required |
| Transaction Provenance | Derived from completed/captured transaction ledgers | Unverified declaration |
| One-Time Payment Treatment | Included in 30-day captured baseline | Subject to author's manual definition |
| Contract Normalization | Trailing 30-day sum (not amortized) | Manual spreadsheet normalization |
| Accounting Status | Payment verification metric (not GAAP audit) | Uncertified disclosure |
Verified MRR, ARR, and Revenue Growth
Verifii uses the verified revenue baseline to derive related secondary indicators:
Verified MRR
The primary baseline metric representing total captured payment revenue across the trailing 30 days.
Derived ARR
Calculated as an annualization of the current 30-day baseline (Verified MRR × 12), rather than contractual ACV.
Snapshot Growth
Calculated as a comparison between historical verified revenue snapshots from a stable baseline at least 24 hours old.
Supported payment providers: Stripe & Razorpay
Verifii calculates Verified MRR through read-only integrations with Stripe and Razorpay:
Stripe Revenue Baseline
Queries completed balance transactions and charges across the trailing 30-day period using restricted API permissions.
Razorpay Revenue Baseline
Queries captured payments and completed transaction orders across the trailing 30-day period using restricted credentials.
To learn how the platform integrates with startup infrastructure, see What is Verifii?. For a detailed walkthrough of the multi-step verification pipeline, read our comprehensive guide: How to Verify Startup Revenue.
Current Verifii verification eligibility
To be displayed as revenue-verified on Verifii profiles and the public leaderboard, a startup must satisfy current platform eligibility conditions:
Active Payment Connection
Startup must have a connected Stripe or Razorpay integration.
Minimum Transaction Activity
Requires at least 3 completed provider transactions.
Positive Revenue Total
Total captured volume in the 30-day window must be greater than zero.
Sync Freshness Window
Provider data must have synchronized within the past 7 days.
Privacy and security boundaries
Verifii calculates Verified MRR while maintaining strict data boundaries:
Restricted Read-Only Permissions
Verification uses restricted read-only credentials. Verifii cannot move funds or modify payment settings.
No Cardholder Information Access
The verification engine does not access or store customer credit card numbers, CVVs, or personal banking credentials.
Frequently asked questions
Common questions about Verified MRR, calculation rules, and data provenance:
What is Verified MRR?
On Verifii, Verified MRR is a payment-backed revenue baseline calculated from completed customer payments and captured charges across an authenticated trailing 30-day window from connected Stripe and Razorpay accounts. This is a Verifii-specific verification metric and should not be interpreted as an accounting-standard calculation of contractual recurring revenue.
Is Verifii Verified MRR the same as accounting MRR?
No. Conventional accounting MRR measures normalized contractual subscription value. Verifii Verified MRR measures actual captured payment volume over the trailing 30 days from connected payment gateways. It does not perform accrual revenue recognition, contract proration, or GAAP accounting.
How is Verified MRR calculated?
Verifii connects to supported payment providers (Stripe and Razorpay) via restricted read-only access, identifies completed and captured transactions in the trailing 30-day window, aggregates the total volume, normalizes the currency, and publishes the resulting baseline on the startup's verified profile.
Does Verified MRR include one-time payments?
Yes. The current verification engine aggregates all successful, completed charges and captured payments occurring within the trailing 30-day window. It does not separate one-time payments from recurring subscription invoices.
How does Verifii verify revenue from Stripe and Razorpay?
Verifii queries connected provider APIs using restricted, read-only credentials to read completed charges, captured payments, and transaction records. Verifii cannot move funds or modify payment provider settings.
How is Verified MRR different from a screenshot of revenue?
Self-reported figures and screenshots can be visually edited or misrepresent gross volumes. Verified MRR is programmatically generated from direct, authenticated payment-provider data, providing objective evidence of recent captured transactions.
Verify Your Startup's Revenue
Connect your Stripe or Razorpay account to establish a payment-backed verified revenue baseline.