Your dashboard's member list: every member you have ever had, with their tier, status, renewal date and whether the Discord role is on. Above it sit tiles for monthly revenue and active subscribers, and below, where your invite-page visitors came from.
Your dashboard has a table of everyone who has ever joined, paid or free. Each row gives you the member, the tier they are on, their status, the date their current period ends, and whether their Discord role is actually on — with a retry control on that last one if it is not.
The table lists every membership; the count beside its title tells you how many of them are active right now. Those two being different numbers is normal — people cancel, and the row stays.
Active and trialing both mean the member holds the role and everything is as it should be.
Past due means a renewal failed and Stripe is retrying the card. The member keeps the role while that happens — an expired card is the usual reason a renewal fails.
Paused and canceled both mean no role and no billing. A paused member still has a subscription and can resume it themselves; a cancelled one does not.
Monthly revenue and active subscribers sit above the table, with collected-this-month beside them and a free-member count wherever you run a free tier. Free members are shown because they are your community, and marked as not counted against your plan because they are not.
Monthly revenue is worked out from your tier prices, less any permanent discount code a member is on, so a comped member counts at nothing while still appearing as a subscriber. Stripe’s own dashboard is the authority on money collected.
Whether somebody counts toward your plan is a narrower question than whether they are in the table — the cap page states the rule, and it is the same rule everywhere in flatpass.
Under the members list is your invite page’s traffic for the last month: visitors, page views, and the share of them who subscribed. Below that, four breakdowns — the tag you put on the link yourself, the site the browser says the click came from, the region, and the device.
The tag is the useful one, and it is the only one you control: add ?ref= and a word of your own to any copy of your invite link and every visit through it is counted separately. Buttons on the Discord card already arrive tagged. Why a Discord invite link cannot carry a tag is the longer version.
All of it is counted by flatpass from visits to your own invite page. It is not Google Analytics, there is no tag to install, and nothing about your server is visible to anyone else.
Nothing for 7 days — signups keep working and the dashboard counts down. Only then do new checkouts pause; existing members are never touched.
In your own Stripe dashboard — the charge was direct, so flatpass has no refund button. A full refund ends the membership and takes the role off; a partial one changes nothing.
Edit the tier and save the new amount. Members already subscribed keep the price they signed up at; only new checkouts pay the new one.