LifterLMS Stripe records every transaction as an llms_order post with postmeta keys for _llms_total, _llms_currency, _llms_payment_gateway, _llms_status and the recurrence flag. Subscription renewals create child transactions linked to the parent order. The orders table in WP Admin is correct, but a course site that does any volume needs to see active subscriptions, MRR, plan mix and gateway success rate on a dashboard rather than as a list.

Stripe's own dashboard knows the payment but not the course. It groups by Stripe product ID, not by the LifterLMS course or access plan. A team that wants to see whether the monthly or annual plan carries the business has to map Stripe product IDs to LifterLMS access plans by hand every time. The information is split, and the join lives in a spreadsheet.

SleekView Charts reads the LifterLMS side. A Number card counts active subscriptions filtered by _llms_status. A Pie splits revenue across access plans. A Bar ranks plans by gross sales. An Area trends MRR over the last twelve months against churn from the order_status column. The whole subscription picture lives on one screen, refreshes against the live llms_order table, and replaces the monthly export ritual with a dashboard URL.

LifterLMS and Stripe each hold half the subscription picture. Stripe knows the gateway success rate and the payment timing. LifterLMS knows the access plan, the course and the learner.

The Stripe dashboard groups by product ID, the LifterLMS orders screen groups by order post, and the join between the two lives in a quarterly spreadsheet that goes stale the day it is sent. Putting llms_order on a chart dashboard inside WP Admin closes the gap. Active subscriptions, MRR, plan mix and gateway success rate sit on one screen, in access-plan terms, refreshed against live data.

Finance gets a per-plan CSV that means something. Programme owners get a monthly review that takes seconds rather than days. The data does not change.

The friction between the LifterLMS side and the Stripe side disappears, and the team stops emailing exports to each other to answer questions the dashboard could have answered first.