Checkout & Licensing

Marketplace checkout turns a successful Stripe payment into package-level access enforced by the LPM.dev Registry.

After purchasing, authenticate LPM CLI with the licensed account and install the package:

lpm login
lpm install @lpm.dev/acme.ui-kit

See the LPM CLI install reference for registry routing, workspaces, lockfiles, and command flags.

Purchase Flow

Sign in on lpm.dev and open the package page.
Choose a pricing plan.
Choose yourself or an organization when the plan allows both.
For an individual organization purchase, choose between 1 and 1000 seats.
Review the subtotal and location-based tax, then complete payment through Stripe.
After Stripe confirms the settlement, the Registry creates the purchase or subscription and its entitlement.
Use LPM CLI with the licensed account or organization membership.

The package, selected version, pricing plan, license scope, quantity, currency, and platform fee are fixed when checkout is reserved. If the plan, package, available version, or seller payment account becomes unavailable before settlement, fulfillment does not proceed under different terms.

Who Receives Access

Purchase	Who receives access
Individual for yourself	The purchasing user
Individual for an organization	Members assigned to the purchased seats
Organization	All current and future members of the selected organization

An organization purchase must be made by an organization owner or admin. Organization licenses always use quantity one; individual organization plans are multiplied by the selected seat count.

Assign Individual Seats

Organization owners and admins manage individual seats from Dashboard > Organizations > organization > Licenses.

Select the purchased package.
Assign available seats to current organization members.
Ask assigned members to authenticate LPM CLI with their own LPM.dev Registry accounts.

Each assigned member consumes one seat. Assigning the same package again to an already assigned member does not consume another seat.

To reassign a seat, revoke the current assignment and assign the newly available seat to another current member. Revocation removes the assignment entitlement immediately.

Organization-Wide Licenses

Organization licenses do not use seat assignments. The Registry checks the purchaser's organization entitlement together with the installer's current organization membership.

This means:

Existing members receive access after settlement.
New members receive access when they join.
A member who no longer belongs to the organization no longer qualifies through the organization-wide entitlement.

One-Time Access

A successful one-time purchase creates a non-expiring entitlement for the package. It is not restricted to the version or major version displayed during checkout.

The buyer can install versions that remain available from the Registry. A full refund or access revocation removes the purchase entitlement and any seats backed by it.

Subscription Access

A successful subscription payment grants access through the paid billing period. Renewals extend the entitlement after Stripe confirms the next payment.

Canceling a subscription schedules cancellation for the end of the current period:

Access continues through the paid period.
The buyer can resume before cancellation takes effect.
When the subscription ends, its direct entitlement and assigned seats are revoked.
If renewal payment is not completed, access does not continue beyond the last paid period.

Archiving the pricing plan does not cancel an existing subscription.

Paid Dependencies

A Marketplace purchase covers only the selected package. If its package page lists another paid package as a separate dependency, that dependency needs its own purchase or subscription.

LPM CLI resolves the complete dependency graph, and the Registry checks access for each protected package independently. A valid license for the parent package cannot bypass a missing dependency entitlement.

Access Troubleshooting

If LPM CLI reports that a Marketplace package requires purchase, check:

LPM CLI is authenticated with the intended LPM.dev Registry account.
The purchase has completed successfully.
The account is still a member of the licensed organization.
An individual organization seat has been assigned to that account.
A subscription is still within a paid access period.
Every separately licensed paid dependency is also accessible.

See LPM CLI authentication for login sessions and registry credentials.

Refunds

Refund eligibility and requests are governed by the Marketplace Seller Agreement and applicable payment terms. When a one-time Marketplace charge is fully refunded, the Registry marks the purchase as refunded and revokes its access.