One-time orders vs subscriptions
Pocketsflow tracks two kinds of paid transactions, and it’s worth understanding the difference because they surface in different places:One-time orders
A buyer pays once for a product (course, download, bundle, upsell). It
produces a single order and, if configured, may include an upsell.
Subscriptions
A buyer starts a recurring plan. This creates a subscriber record plus a
payment every billing cycle — the first (initial) charge and one for
each renewal after it.
initial or renewal) and
point at the subscription plan instead of a one-time product.
The Orders page and its two tabs
The Orders page is split into two tabs so recurring revenue never gets mixed in with one-off sales:1. Orders tab (one-time)
Lists your one-time product transactions only — subscription charges are deliberately kept out of this list (they have their own ledger). For each order you’ll typically see:- Order reference and date.
- Buyer (email / name).
- Product purchased, plus any upsell attached to the order.
- Gross amount and currency.
- Net amount (after tax, fees, and any affiliate cut).
- Tax collected and the buyer’s country.
- Status — completed, refunded, or disputed.
2. Subscriptions tab
Lists your subscribers — one row per active or historical membership rather than one row per payment. For each subscriber you’ll see the plan, the buyer, the current status, and the billing details. This is the roster of who is subscribed; the individual recurring charges live in the subscription’s payment history (below) and in the subscription-transactions ledger.There is also a subscription-transactions ledger — the per-payment view of
every subscription charge (initial + renewals) across all subscribers,
mirroring the one-time Orders tab. Use the subscriber roster to answer “who is
subscribed?” and the transactions ledger to answer “which charges happened?”.
Subscription status
Every subscriber carries a live status, kept in sync by the payment provider’s webhooks. The ones you’ll see most often:How a subscription becomes past_due
How a subscription becomes past_due
When a renewal charge fails, the provider fires a payment-failed event and
the subscriber flips to
past_due. Billing keeps retrying; if it recovers,
the status returns to active, otherwise it ends up canceled.How a subscription becomes canceled
How a subscription becomes canceled
Either you cancel it, the buyer cancels from their billing portal, or the
membership is deactivated (e.g. after exhausted retries). A cancel-at-period-
end request keeps the member active until the end of the paid period.
Active subscriptions in analytics
Active subscriptions in analytics
Only
active and trialing subscribers count toward active-subscription
and MRR figures in Analytics.Opening a subscription
Click into a subscriber to open its detail. This is where you see the customer plus the full payment history of that one membership:1
Subscriber & plan
The buyer (email, name, country), the subscription plan they’re on, the
price and billing frequency, and the current status.
2
Payment history — initial + renewals
Every successful charge recorded for this membership, newest-first: the
initial payment that activated it and each renewal after it. Each
row is a real transaction you can open. (Charges are matched to the
subscriber both by its stored id and by its plan id, so the very first
payment is included even though it can arrive moments before the subscriber
record is finalized.)
3
Actions
From here you can cancel the subscription or refund it (which refunds
the paid invoices and cancels the membership).
A single payment’s detail
Opening any transaction — a one-time order or a subscription payment — shows its full detail.Quick-copy IDs
At the top of every order or subscription detail page, you’ll find quick-copy chips for the relevant IDs:- Order ID / Subscription ID — the unique identifier for the transaction or subscriber record.
- Product ID / Customer ID — click to copy the ID for API calls or support lookups.
- Portal link (subscriptions) — copy the subscriber’s billing-portal URL to share with them directly.
Payment breakdown
The payment breakdown shows the complete money flow:- Customer paid — the total amount charged to the buyer.
- Sales tax — collected from the buyer and remitted to tax authorities (not part of your earnings).
- Payment infrastructure fee — charged by banks and card networks to move the money, screen for fraud and chargebacks, provide dispute prevention, and pay out your balance. Pocketsflow doesn’t take any of this.
- Pocketsflow fee — our flat 2% platform fee. No monthly fees, no setup costs, no hidden charges.
- You receive — your net payout after all fees, added to your balance.
Other details
- Buyer / customer — email and linked customer record.
- What was purchased — the product (for one-time orders) or the subscription plan (for subscription payments); one-time orders also show any upsell and its metadata.
- Billing reason — for subscription payments, whether this was the
initialcharge or arenewal. - Status flags — refunded / disputed.
- Review — if the buyer left one linked to this sale.
Customers
The Customers view aggregates activity at the buyer level. A customer record is created (or reused) the first time someone buys from you, keyed by their email, so repeat buyers stay as a single customer. Typical fields:- Name and email.
- Country.
- First and most recent purchase.
- Total spend, products owned, and any active subscriptions.
Searching, filtering & exporting
Both Orders and Customers support:- Search by email, name, or ID.
- Filters by date range and product (subscriptions can filter by plan).
- Pagination for large accounts.