> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/stripe-billing-integration/gift-subscriptions.md).

# Gift Subscriptions with Stripe

From Release 116, customers can buy and redeem gift subscriptions on tenants using Stripe Billing. A gifter pays for a subscription on behalf of someone else; the recipient redeems a gift code to activate their subscription without ever entering payment details.

The customer-facing setup is the same as for Zuora tenants — a gift offer, a [gift checkout](https://docs.limio.com/components/component-library/modular-checkout-components/modular-checkout-how-to-configure-a-gift-checkout), and a redemption page using the [Redeem component](https://docs.limio.com/components/component-library/standard-components/component-redeem). This page describes what happens in Stripe at each step and the current limitations.

## Configuration

Create a Limio gift offer (gift attribute = true) linked to a Limio product that is linked to a Stripe product. As with regular offers, the corresponding Stripe price is created automatically on the first order if it doesn't exist yet.

## What happens at purchase

When the gifter submits the order and pays:

* Payment is collected **in full at purchase**, via a one-off Stripe invoice settled by the gifter's payment. The gift code is recorded on the invoice metadata, so the transaction is traceable in Stripe.
* A unique gift code is created and linked to the order in Limio (visible in the Limio gift codes section).
* **No Stripe subscription is created yet** — for the gifter or the recipient. A Limio subscription with status `initial` is recorded against the gifter.

If payment fails, the order fails and the gift code is marked as redeemed so it cannot be used.

## What happens at redemption

When the recipient enters a valid, unused gift code, logs in, and submits the redemption checkout:

* A Stripe subscription is created for the recipient, running for the term configured on the original gift offer, starting at redemption.
* The recipient does **not** provide a payment method. The first subscription invoice is marked as settled externally ("paid out of band"), linked back to the original purchase invoice via metadata — no money moves at redemption, because it was collected at purchase.
* The gift code is marked as redeemed and cannot be used again.

At the end of the term, the gift subscription ends automatically and the recipient is not charged. If they want to continue, they can subscribe independently — the new subscription is created on the same account with all normal subscription actions.

## What recipients can and can't do

After redeeming, the recipient **can** change their delivery address and add, delete or change their default payment method. They **cannot** upgrade, downgrade, renew or cancel the gift subscription itself — it runs for its fixed term and ends.

## Current limitations

* **One gift per order.** A single order can contain one gift subscription.
* **Fixed term only.** Gift subscriptions cover a defined period and do not auto-renew.
* **Single billing period.** Gift offers billed monthly across multiple periods are not supported.
* **No gift refunds.** Refunding a gift purchase is not supported in this release.
* **No Limio for Salesforce.** Gift purchase and redemption through LFS is not supported.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.limio.com/integrations/stripe-billing-integration/gift-subscriptions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.