LearnDash Stripe stores transaction details in wp_usermeta keys (Stripe customer id, subscription id, last payment id, status) and grants course or group access by writing to LearnDash's standard enrollment surfaces. The default LearnDash admin shows enrollments and the Stripe dashboard shows payments, but neither lets you audit the join: which payment granted which access, which subscriber is past due, which enrollment is orphaned from a payment.

SleekView reads the Stripe meta keys and LearnDash activity rows together so finance and program teams can build the audit views their reconciliation workflows need. A per-payment table joins each Stripe transaction with the resulting course or group enrollment. A renewal queue surfaces subscriptions expiring soon. An orphan report finds enrollments without a matching active payment.

Inline status edits route through LearnDash and Stripe's webhook handler functions where supported so the same hooks fire as for a real payment event. Direct meta edits skip hooks by design for back-fill scenarios. Multisite installations get per-subsite scoped views automatically.

Payment and access live in two different systems for any LearnDash course business that bills with Stripe. Stripe holds the source of truth for who paid; LearnDash holds the source of truth for who can access. LearnDash Stripe stitches the two together with meta keys in wp_usermeta and access writes through the standard enrollment path.

The stitching usually works. The day it does not, the operational cost is high: a refunded payment whose access did not revoke is a small revenue leak; a past-due subscription whose access stayed live is a bigger one; a renewed payment that did not trigger access is a support ticket. The default LearnDash admin shows enrollments without payment context; the Stripe dashboard shows payments without enrollment context.

SleekView turns the meta keys and the activity table into one workspace: per-payment audits, renewal queues, orphan-enrollment reports, refund-and-revoke views. Finance, registrars, and support all work from the same row-shaped surface, and the gap between paid and entitled stops being a guessing game.