Products, prefixes and confirmed sales
Current inspected release: beta17, private Premium preview. Read the current workflow and acceptance limits. Earlier beta references describe the retained feature history, not a newer public/stable stamp.
Claim the vendor owner once and back up the complete private vault. Create a product with its human name, exact addon key or theme:key and validity days (0=lifetime). Set the desired prefix in Settings; it changes presentation for future issued codes, not ownership or existing signatures.
Under Sales connections, choose Downloads or Marketplace and the actual titled listing, then connect the product. Existing completed purchases are excluded unless you deliberately include history. Core-confirmed paid orders and provider reference/amount/state are authoritative. Process or Reconcile reads them; it does not capture money or mark an order paid. Cross-listing should not create duplicate entitlements for the same payment/product.
Pause a connection to stop new issuance without disabling existing keys or refund processing. Refunds revoke associated vendor access even while a connection is paused. Do not infer that Marketplace checkout is open merely because its table exists. Readiness checks interfaces, not live payment success.
