How is a secure download issued on payment (token, limits, expiry)?

When a digital product is paid for, the system issues a DigitalDownload — a per-purchase grant carrying a secure token, a download-count limit, and an expiry — derived from the product's DigitalDetail (download limit and license days). The customer receives a tokenized link (e.g. /DigitalDownload/Get?token=…) rather than a direct file URL. This means access is tied to the specific…

When a digital product is paid for, the system issues a DigitalDownload — a per-purchase grant carrying a secure token, a download-count limit, and an expiry — derived from the product's DigitalDetail (download limit and license days). The customer receives a tokenized link (e.g. /DigitalDownload/Get?token=…) rather than a direct file URL. This means access is tied to the specific purchase, time-bounded, and capped, rather than a permanent public link anyone could share indefinitely. Issuance happens automatically on payment, as one of the hooks that fire when an order is marked paid.