Proof points, starting with MRR
A coupon proves the discount. It does not prove that anyone is paying, that the site stays up, or that anyone visits. Those are different facts, and early adopters look for them before they paste a code.
Dealpuffin calls them proof points. A proof point is a reading from a provider, shown on the listing, marked verified by that provider. The founder does not type the number in.
MRR from your billing provider
MRR is monthly recurring revenue read from a billing provider: Stripe, Paddle, Polar, RevenueCat, Lemon Squeezy, or Dodo Payments.
For Stripe, Paddle, Polar, Lemon Squeezy, and Dodo Payments, the reading is the sum of active subscription prices (or recurring amounts), normalized to one month, before discounts where the provider exposes that. Metered or one-off lines are left out where the API makes that clear. If the account bills in more than one currency, the total that is shown is the currency that adds up to the most. Dealpuffin does not convert it into dollars and pretend that was the reading. RevenueCat uses the project overview MRR metric instead of recomputing from receipts.
You connect a read-only key (or V2 secret for RevenueCat). It is stored separately from the key that imports coupons. Publishing a coupon does not reveal MRR. Connecting MRR does not publish a coupon. The first read happens when you connect. After that you pick daily, weekly, or monthly, and an hourly job reads the connections that are due.
If a provider returns more than one sync can read, that sync saves nothing. A partial total is not presented as the revenue.
Exact, or a band
For each proof point you turn on, you choose what other people see.
Exact shows the figure. A band shows a range and a color. The range for MRR runs from 0–1k through 1M+. The stored reading is still the exact value, including when the public choice is a band. Seekers and their agents do not receive the number, or how far it moved. They receive the band, the currency, the provider, when it was last read, how often it is read, and whether the trend is up, down, flat, or new.
You still see the latest number on your own product page.
You set the order. A catalog card shows the first three. The product page shows every one. The line on the listing says verified by that provider, with the provider mark. It is a reading, not a rank, and Dealpuffin does not pay anyone a commission for it.
Other people see this on a public https listing that is not hidden. Ownership verification is optional.
The same shape, for other facts
MRR is not the only fact an early adopter asks about.
Uptime comes from Better Stack, CloudWatch, or Google Cloud Monitoring. Traffic comes from Google Analytics. Each of those is the same kind of object as MRR: a provider you connect, a field that provider can read, a cadence, and a choice between the exact reading and a band. The founder still does not type the number. The listing still says which provider verified it.
Coupons stay the reason to start. Proof points are the reason to believe the product is already a product. The rules for the reading, the band, and the keys are in Proof points.
Frequently asked questions
Do I have to show MRR?
No. Nothing is shown until you connect a billing provider as a proof-point provider and turn MRR on.
Can seekers see the exact dollar figure?
Only if you choose exact. A band shows the range. The number stays on your side of the product page.
Is the coupon key the same as the MRR key?
They are stored as two connections. The key can be the same string if it has both permissions. You paste it in each place.
What comes after MRR?
Uptime and traffic already use the same proof-point shape. More fields can follow without changing how exact, band, and do not show work.