Skip to content

Methodology

Exactly how we work out each figure on a certificate. For the same thing in plain words, see how verification works.

Where the numbers come from

Every figure is computed from payments read directly from the seller’s own Stripe account, through read-only access the seller grants. Sellers can’t type, upload or edit a number. We work the figures out once a day, for the 90 days ending yesterday (UTC), so a certificate never changes more than once a day.

What counts as revenue

  • Counts: successful, captured live-mode charges, at the amount captured.
  • Taken off: refunds (full and partial), and the disputed amount while a dispute is open or lost. A dispute the seller wins is added back.
  • Never counts: payouts, transfers, top-ups, Stripe Capital and other financing, application fees, test-mode payments, and payments that were never captured or were cancelled.
  • Stripe’s processing fees are not taken off: figures are net of refunds and disputes, before processing fees. Revenue isn’t profit.

Net revenue, monthly average

For each charge: net = captured − min(refunded + disputed amount if the dispute is open or lost, captured) Net (90 days) = Σ net of charges created in the last 90 days Net revenue, monthly average = Net (90 days) ÷ 3

This is the headline figure. It’s corrected every day as late refunds and disputes arrive: each night we re-read the last 120 days of payments.

Bands

Unless a seller chooses exact figures, the monthly average is shown as a band, in the seller’s display currency: under 1k, 1k–5k, 5k–10k, 10k–25k, 25k–50k, 50k–100k, 100k–250k, 250k–500k, and 500k+ a month. Net revenue over the last 12 months (the same formula over 365 days) is shown as a band too: under 12k, 12k–60k, 60k–120k, 120k–300k, 300k–600k, 600k–1.2M, 1.2M–3M, 3M–6M, and 6M+.

Refund rate and dispute rate

Refund rate = Σ refunded on charges created 31–120 days ago ÷ Σ amount of those charges Dispute rate = number of those charges with a formal dispute ÷ number of those charges

Refunds and disputes usually arrive weeks after a payment. Measuring them on the last 30 days would make every seller look better than they are, so the rates use charges that have had a month or more to mature. A formal dispute is one that needed a response, was under review, or was won or lost; early warnings that closed without one don’t count. Sellers can’t hide either rate while their certificate is published.

Refund rate (12 months) = Σ refunded on charges created 31–395 days ago ÷ Σ amount of those charges Dispute rate (12 months) = number of those charges with a formal dispute ÷ number of those charges

The same rates over 12 months are worked out too. A certificate shows them, marked “12 months”, only when the 31–120 day window has no payments yet. The leaderboards use them for sellers with fewer than 10 customers in 90 days (see below).

Months with revenue

Of the last 12 calendar months (the current one included), how many had net revenue above zero, out of the months since the seller’s first payment. A seller who started 5 months ago shows “Revenue in 5 of the last 5 months” at most. It shows steadiness: one big launch and nothing since reads differently from revenue every month.

Customers and concentration

Customers (90 days) = number of distinct customers whose net payments in the last 90 days are above zero Concentration = the largest single customer's net ÷ Net (90 days)

A customer is the Stripe customer, or else the billing email, or else the card. Each is turned into a keyed hash that’s different for every Stripe account, so we never store a customer’s name, email or card. Stripe sends the billing email with each payment: we use it only for this, and to spot payments from the seller’s own address, then let it go. When concentration is over 50%, the certificate says “Most revenue comes from one client.”

History, currencies and several accounts

  • Revenue history since: the month of the earliest successful live charge we read (we read up to 24 months back).
  • Currencies: each charge is converted to the display currency (dollars, pounds or euros) at the reference rate for the day it was made. The rates are stored, so every figure can be worked out again.
  • Several Stripe accounts: a seller can connect up to five. Their payments are added together; the same account can’t be connected twice, or by two sellers.

When figures show

  • Verification in progress: we’re still reading the account’s history.
  • Verified: the last successful read was under 72 hours ago.
  • Verification paused: no successful read for 72 hours, or Stripe stopped our access. Figures show, with the date of the last read.
  • No longer verified: disconnected, or no successful read for 14 days. Figures are hidden.
  • Under review: an Earncrest admin suspended the certificate while we check it. Figures are hidden. It isn’t a finding against the seller.

The two ticks

Revenue verified needs all of these: a live-mode Stripe account read in the last 72 hours, its full history read, at least 30 days of payment history, and no unresolved critical finding from our fraud checks. A finding is critical when an admin marks it so, or straight away when someone tries to connect a Stripe account that’s connected to another profile or held back from a deleted one.

Owner verified needs, for every Stripe account behind the figures, proof the seller controls it and a match between it and their business, plus at least one social account. A certificate says “Verified” only with both ticks.

How the leaderboard ranks

  • Only sellers who choose to appear are listed, and only while their certificate is published and Revenue verified.
  • It ranks three ways: by revenue, by refund rate and by dispute rate. Every row shows all three, so revenue never stands on its own.
  • Revenue: by the band of net revenue, monthly average, highest first; within a band, the longest revenue history first. Never by an exact figure. A seller who hides their revenue keeps their real place, with the figure blurred.
  • Refund rate and dispute rate: lowest first, among sellers with at least 10 customers in the last 90 days, on their 90-day rates. A seller with fewer than 10 customers in 90 days but at least 10 in the last 12 months is ranked on their 12-month rates instead, marked “over 12 months”, so a high-ticket seller with few clients a month can appear. Nobody with fewer than 10 customers in either window is ranked, so a handful of customers can’t top a board. Equal rates go to the seller with more customers in the window used.
  • Each row shows customers in the window its rates use. The leaderboard can be split by seller type, and narrowed by niche once 25 sellers are on it. Its search finds any published certificate by name, handle, website or social handle, with the seller’s place when they have one. Each seller’s band is in the currency they chose for their certificate, and bands rank by their numbers whatever the currency. We never show one seller’s band in several currencies, because together they would give away more than the band.
  • Sellers can hide their revenue, wherever it would show, and blur their name on the leaderboard. Either is drawn blurred from placeholder characters, so the page never holds what’s hidden. A blurred name’s row has no photo or link, a search never finds it, and nothing else shows that seller’s place. Refund and dispute rates always show.
  • Until 10 sellers are on it, it doesn’t rank them: they show as founding sellers, without places, in the order the revenue ranking gives them. The three rankings start at 10.
  • The leaderboard updates once a day, with the figures. Nobody can pay to appear, to rank higher or to be left off.

Founding 100

The first 100 sellers to have both ticks on a published certificate are numbered, in the order they first published. The number never changes, and a deleted account’s number isn’t given again. The certificate shows “Founding verified seller” only while both ticks hold. It records when a seller joined, not how much they earn, and it doesn’t affect any figure or place. It’s separate from the selling tools’ 100 free places.

What we count about visits

For each seller’s dashboard we count, per day, how many people viewed their certificate and badge, clicked “Work with me”, or saw them in a Check a sales coach result. Each visitor counts once a day, robots and the seller themselves don’t count, and nothing about the visitor is stored: they’re told apart for the day by a keyed code held only in our server’s memory. The home page counts searches as a single number a day.

When a search finds no one, we count the name searched for (never an email address or a long number) for 90 days, so a seller who later joins can see that buyers were looking. An “Ask them to get verified” link keeps that name too, for 90 days, and nothing about who made it.

Fraud checks

Every day we look for patterns that can mean figures are being inflated, such as sudden spikes driven by new customers, payments from the seller’s own address, or one card paying as many customers. A finding is reviewed by a person before anything changes; we don’t publish the exact thresholds, so they can’t be worked around.

This is the seller's own business revenue. It is not a promise or prediction of what you will earn, and it is not an endorsement by Earncrest.