Course purchases and access

Course commerce and enrolment

Contract between purchase and learning access

1. Identify the sale model and authoritative order, payment, entitlement and enrolment records. Map the offering to buyer, beneficiary, tenant, course version/policy, access period and any cohort/seat. Gifts, subscriptions and company seats apply only when requested. Resolve who receives access before fulfillment.
2. Record agreed access consequences and effective times for pending/successful/failed payment, expiry, renewal, cancellation, refund and dispute. A refund need not erase attempts or revoke certificates: access and issued evidence have separate policies.
3. Route checkout, signature verification, server-side pricing, financial idempotency and reconciliation to the available billing specialist (Blake in the default team). Inspect team/skill availability first; request missing capability through the existing workflow and report the dependency. Reuse billing-domain-state-machines, payment-security-idempotency, subscriptions-entitlements and billing-verification-reconciliation. This skill owns the LMS fulfillment contract.
4. Bind verified server-side payment evidence to the matching order and learner before granting access. A browser return URL, client amount or unverified callback grants nothing. Use one durable fulfillment identity per purchased access grant; a webhook replay and return-path reconciliation must converge on the same enrolment. Check existing manual suspension and later entitlement changes before applying delayed events.
5. Keep payment-confirmed/enrolment-pending visible and retryable without another charge. Reconcile unknown payment outcomes before repeating effects. Invoice failure must not undo payment or rerun capture. Recover finance and access separately, retaining linked evidence.

Acceptance evidence

Exercise the real application with an authorized payment sandbox when available: successful purchase reaches exactly one intended enrolment, the learner opens paid content and resumes learning. Also check declined/abandoned/pending payment, forged return URL, duplicate and delayed notifications, wrong learner/tenant/course, fulfillment failure followed by recovery, and refund or expiry under the agreed policy. Check downloads and assessment endpoints after access ends; preserve prior attempts and certificates according to their own rules.

Record event/order IDs, access transitions and observed results without secrets or learner payloads. Distinguish local simulation, provider sandbox and production evidence; unavailable provider access is a verification gap.