Start with one member
Record the affected membership, approximate purchase time and what the member can see. Avoid sharing card details or a customer database in an enquiry. Use a test account for reproduction where possible.
Match the payment to the site
Compare the payment provider event with the site transaction and subscription state. A pending, failed or unmatched transaction points to a different problem from a completed transaction with the wrong access.
Inspect the access rule
Check the purchased membership against the rule protecting the page or course. Confirm whether timing, expiry, drip settings or a second plugin changes that decision.
Follow the integration
If LearnDash or a CRM controls part of the journey, check whether the expected enrolment or tag event arrived. Do not assume a sent webhook was accepted by the receiving service.
Retest the affected states
After a scoped repair, check the intended paid state and the restricted state. Fixing access for one account should not make paid content public. Record the outcome before considering the issue closed.
For help applying this to your site, explore memberpress development.