Subscription or paid-pass signup

Use Recued's Seller acquisition workflow for the public signup, checkout, provider verification, and access issue - on Stripe, Paddle, or Lemon Squeezy alike. A subscription runs through the provider's open-subscription-access-order workflow and its Seller Subscription Payment Events pack; a pass through open-pass-order and the Seller One-Time Pass pack (each with the provider's suffix, -paddle or -lemonsqueezy, outside Stripe). Once the order is complete, run this recipe with the order's oh_... handle. The order must have originated from a Reception submission, name an entitlement key, and link a Seller customer. This recipe re-reads the accepted form response only to recover the normalized email and then writes the minimum student record. It cannot turn an unpaid order into a student.

Which class the student joins

The roster, the assessments, and the scorecards all key on class_key. By default it is the order's tier key, which is the class whenever the tier is named after the class: a manual pass tier, or a Stripe entitlement feature. A Paddle or Lemon Squeezy subscription tier is keyed by the provider's product id (pro_..., or a number), so set Class key on this dish to the class the free enrolment form uses; the tier key is still recorded on the student as entitlement_key. The two enrolment paths then meet on one roster.

Where the student is stored

One student record owned by this pack (D-221), keyed by a collision-safe sha256(canonical-json([class_key, customer_id])) - the same identity the free-enrollment template writes, so a student who moves between the two paths keeps one row rather than gaining a second. The write is an upsert, so re-running the same order handle is safe.