> 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/guides/feature-implementation-guides/guide-claim-subscription-ownership-after-guest-checkout.md).

# Guide: Claim subscription ownership after guest checkout

*Available from Release 115 onwards.*

### The big idea

Limio supports a **claim ownership** flow that lets a customer link a subscription bought via guest checkout to their authenticated identity. Once claimed, the subscription appears in their self-service portal and behaves exactly like one they purchased while signed in. They can update payment, switch plans, see invoices, or cancel online.

This pairs with Limio's support for **guest checkout** so you can reduce friction at the point of sale without leaving customers stranded post-purchase.

Why do it

* Give end users full self-service for subscriptions they didn't (or couldn't) buy while signed in.
* Support B2B scenarios where the buyer is a different person from the end user.
* Reduce support load by letting customers manage their own subscriptions instead of contacting you.

### What the customer experiences

1. **Purchase**: a buyer places an order through [anonymous checkout](https://docs.limio.com/product/authentication/authentication-provider-per-page/configuring-anonymous-authentication-for-your-checkout-flow). The subscription is created with no authenticated owner; only the customer email and details are recorded.
2. **Notify**: the customer is shown the subscription reference (for example `A-S00012345`) on the [order-complete page](https://docs.limio.com/product/checkout/how-to-configure-the-order-complete-page) and/or in their order confirmation email.
3. **Sign in**: the end user signs in or registers an account on your [Limio MMA portal](https://docs.limio.com/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account).
4. **Claim**: a custom component calls `claimSubscriptionOwnership()` with the subscription reference. If their email matches the email on the subscription's customer record, ownership transfers in real time.
5. **Self-service**: the subscription appears in their [Self-Service portal](https://docs.limio.com/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account). They can manage it like any other subscription they own.

### Constraints

* **Email must match.** The authenticated user's email must match the email on the subscription's customer record (case-insensitive). If they differ, the claim is rejected.
* **Guest purchases only.** A subscription already owned by another authenticated user cannot be claimed.
* **Authenticated session required.** The user must be signed in before the claim is attempted.

When the claim succeeds, all related records (orders, offers, add-ons, payment methods, addresses, schedules) transfer to the authenticated user along with the subscription. The call is idempotent: calling it again on a subscription the user already owns returns success without side effects, so it's safe to retry.

### How to enable

This feature is currently available **only via the SDK**. Your developers will need to build a custom component (typically a form or prompt on an MMA page) that calls `claimSubscriptionOwnership` from `@limio/sdk`.

Share the [SDK reference for `claimSubscriptionOwnership`](https://docs.limio.com/developers/limio-sdk/user#claimsubscriptionownership) with your dev team.

### Related

* [Configuring Anonymous Authentication for Your Checkout Flow](https://docs.limio.com/product/authentication/authentication-provider-per-page/configuring-anonymous-authentication-for-your-checkout-flow)
* [Self-Service Overview](https://docs.limio.com/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account)
* [SDK reference: `claimSubscriptionOwnership`](https://docs.limio.com/developers/limio-sdk/user#claimsubscriptionownership)


---

# 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/guides/feature-implementation-guides/guide-claim-subscription-ownership-after-guest-checkout.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.