Access is part of the order
The same event that marks an order paid enrols the student. There is no second system of record for who should be in the course.
Refunds unwind themselves
Refund the order and the enrolment is revoked. You are not remembering a reverse automation at 11pm.
Payment plans stay honest
A failed charge can pause access until the plan is healthy again. The student is not left in the classroom, and you are not left explaining a hole.
The sale is not finished at the card
A course is not a file in a thank-you email. It is a seat in an LMS, sometimes a bundle, sometimes a plan that bills four times. Fulfilment is the work of making that seat match the order, every time, including the times the order goes backwards.
Creators end up with Zapier because the cart and the LMS do not share that job. One zap enrols. Another is supposed to un-enrol. A third tells a spreadsheet. It works until a filter changes or a task is turned off, and then you find out from a student who paid and cannot log in.
What the engine actually does
You map a RobinCart product to the thing it delivers. On payment, RobinCart tells the LMS to open it for that email. On refund, cancellation, or a failed payment plan, RobinCart tells the LMS to close it. Bumps and upsells can carry their own mappings, so the workbook course and the main course do not depend on a single brittle task.
When this is the page you wanted
Use this if your support inbox contains “I paid but I’m not in the course,” or if you are afraid to refund because you are not sure access will actually stop. If the classroom is Thinkific, read the integration next. If the other leak is a countdown that does not belong to the person looking at it, read evergreen deadlines.