Plan trials

Configure the Product's Free Trial and finish the Stripe/quote setup from the purchase guide. Trial availability follows server eligibility and returned terms.

Free Trial belongs to a Product and uses its Entitlements. Trial eligibility, payment-method requirement, duration and end policy are commercial terms; there is no separate trial Entitlement version or group-owned automatic-trial policy.

• Configure Free Trial on the Product and preview it through the current Stripe previewAttach flow. Show actual duration, subsequent charge and payment-method requirements.
• Execute attach after explicit confirmation; card-required trials use Stripe Checkout. A trusted backend can explicitly start a no-card trial, and an eligible paid default Product with a no-card trial can start during new Customer initialization without a paid Invoice.
• Eligible free default Products can initialize independently. Empty holdings are valid. Registration time or the browser clock cannot establish trial start/end.

Trials deduplicate by Customer and Product; unique_fingerprint additionally uses the host's stable signal across Customers. Explicit trusted custom days retain their existing exemption. An unavailable paid default trial falls through to a free default in its group, when present; an explicit start returns a generic conflict. Retain X-Request-Id for server-side diagnosis.

Related:Stable signal integration and lifecycle

Related:Purchase and verified results

Call trial start/extension/end or existing-subscription changes only when enabled by your deployment. A method signature does not mean all management operations are available. Apple/Google purchase and restore need their matching store runtime; compilation, store sheets and device callbacks do not establish delivery.