WooCommerce Subscriptions and Payment Links
Two common ways of running a subscription business on Stripe never create a Stripe subscription object at all. This is why SSA has to find them another way.
Why these show up as plain charges
SSA's own Pattern detection setting describes exactly this case: it exists to "detect recurring payments that do not use native subscriptions." WooCommerce Subscriptions billed through the standard Stripe gateway, and a Stripe Payment Link set to recur, are both examples of that: nothing on the Stripe side ties the repeat charges together as a subscription, so SSA reads only a series of ordinary charges.
That gap is also why a dedicated WooCommerce Subscriptions connector, which would read WooCommerce's own subscription records directly instead of waiting to spot the pattern, is planned as SSA Pro's next connector build.
What SSA does with them
SSA's pattern detector groups a customer's charges by amount and currency and looks for a regular gap between them. When it finds one, it writes a detected subscription: a synthesized row carrying the amount, the inferred billing interval and a Detected badge, so it counts in MRR, churn and retention exactly like a native subscription, while staying visibly marked as found rather than read directly. See how detection works for the full mechanism.