> 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/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account.md).

# Self-Service Overview

The Limio Self-Service portal enables subscribers to manage their subscriptions. Below is a description of its standard functionalities. You can also find all the Self-Service components here:

[Self-Service Components](https://docs.limio.com/components/component-library/self-service-components)

Limio syncs every change a subscriber makes to your billing provider in real time. Which payment methods and which settlement behaviour you get depends on the provider you use:

* **Zuora** — [How Limio Events Update Zuora](https://docs.limio.com/integrations/keeping-zuora-and-limio-in-sync/how-limio-events-updates-zuora-for-commerce)
* **Stripe Billing** — [How Limio Events Update Stripe](https://docs.limio.com/integrations/keeping-stripe-and-limio-in-sync/how-limio-events-update-stripe), [Configure Payment Methods](https://docs.limio.com/integrations/stripe-billing-integration/manage-payments/configure-payment-methods), [Cancellations & Refunds](https://docs.limio.com/integrations/stripe-billing-integration/manage-payments/cancellations-and-refunds)

The rest of this page describes the subscriber journeys. They work the same way whichever provider you use.

## **View Subscriptions**

Limio allows subscribers to see 1 or multiple subscriptions stored in Limio. For each subscription, they can see key information such as their Product, Term, Start Date and Renewal Date. They can then go into different part of the self-service portal, such as the cancel or upgrade/downgrade experience.

The Limio Self-Service portal can aggregate multiple subscriptions that might sit on different accounts/systems to provide a unified view to the subscriber. Each subscription can have different level of allowed changes.

![The subscriptions view, with the actions available on each subscription](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-c46d3b28edf96cd0864f33b8d1de264d391c88f4%2Fself-service-subscriptions.png?alt=media)

## **Claim a Subscription Purchased Anonymously**

For scenarios where someone purchases as a guest and later signs in to manage their subscription, Limio supports **claiming ownership** of a guest-purchased subscription. Once claimed, the subscription appears in the self-service portal exactly like one purchased while signed in. See [Guide: Claim subscription ownership after guest checkout](https://docs.limio.com/guides/feature-implementation-guides/guide-claim-subscription-ownership-after-guest-checkout) for the full implementation pattern.

## **View and Edit Payment Methods**

Subscribers can also manage their payment methods within the Limio Self-Service Portal. Subscribers can add a payment method, delete one, and change which method is the default.

Limio can support debit and credit cards, digital wallets such as Apple Pay and Google Pay, direct debit, ACH, and PayPal. The methods a subscriber sees depend on your billing provider and payment gateway, and you can limit the methods on an individual offer. A common use is a lower price on a direct debit offer, which retains better than card.

{% tabs %}
{% tab title="Saved Payment" %}
The **Saved Payment Methods** component allows customers to view, manage, and delete their saved payment methods within a self service Finance Portal. This reduces reliance on sales or support staff and helps businesses avoid lost revenue by allowing multiple methods to be stored and a fallback method used if the default fails.

![](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-6abc8e97f5ae2f94982ab2ce468383c709bc7731%2Fimage%20\(81\).png?alt=media)
{% endtab %}

{% tab title="Payment History" %}
The **Payment History** component allows customers to view their historical payments in a self-service Finance Portal. This improves transparency and reduces support requests by letting users check payment dates, statuses, amounts, and methods directly, without contacting sales or account managers.

![](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-9ad45e4b7a816458fe23d6e2a2ec28c2ce617124%2Fimage%20\(82\).png?alt=media)
{% endtab %}

{% tab title="Self-Service Form" %}
The **Self-service Form** component allows your customers to perform a variety of self-service use cases. It is designed for use cases such as adding a new payment method and updating contact details. Unlike the Checkout Form, the Self-service Form is dedicated to post-purchase account management.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-eb2fd3c4f1f8e941915a18ebd7d3e825390c4feb%2Fimage%20(8)%20(1)%20(1).png?alt=media" alt=""><figcaption><p><a href="https://docs.limio.com/components/component-library/self-service-components/component-self-service-form">Self-service Form component</a></p></figcaption></figure>
{% endtab %}
{% endtabs %}

## **View and Pay Invoices**

Customers can view their invoices in self-service. Users can download a specific invoice, and pay any open invoices, both partially or in full. This makes it easier and quicker for users to pay outstanding balances, as well as having one central view to see all invoices.

You can set a minimum payment amount on the invoice payment modal, so a part payment must meet the threshold you choose.

![Invoice table component](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-4259a2e62a466bd905aa51fbccfcbf7cdb983ab4%2Fimage%20\(83\).png?alt=media)

## **Upgrade/downgrade subscription**

Subscribers can switch (upgrade or downgrade) their subscriptions via two dedicated flows:

{% tabs %}
{% tab title="Update Subscription (B2B)" %}
Update subscription: This flow is geared towards multi-products, hybrid pricing, concurrent changes that are typical in B2B scenarios. It could be for example an upgrade to a higher tier, a change in seats, and an add-on purchase on volume pricing. Learn more at [Create Update Subscription Experience](/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-configure-an-update-subscription-flow.md).

Subscribers can also:

* Change the quantity of a product they hold, for example the number of seats. An increase bills immediately. A decrease takes effect at the end of the term.
* Remove one offer from a subscription that holds several, without a cancellation. The subscription must keep at least one offer, and the removal takes effect at the end of the term.

{% embed url="<https://69c2cf3a42a094f3cd354b8d-hbwumtssfk.chromatic.com/?path=/story/shop-components-self-service-update-subscription-offers--default&full=1&shortcuts=false&singleStory=true&embed=true>" %}
{% endtab %}

{% tab title="Switch (B2C)" %}
Switch flow: This flow is geared towards simple, one-product changes that are typically in B2C scenarios. They could be do a different product or a change in term, for example monthly to annual. The upgrade or downgrade experience can be defined either via links between offers or via customer segmentation. Learn more at [Create Personalised Switch Experience](/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-create-a-personalised-switch-upgrade-or-downgrade-experience.md)

![](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-783242602c2ead40933139025781de5a7d783e04%2Fimage%20\(84\).png?alt=media)
{% endtab %}
{% endtabs %}

## **Buy Add-Ons**

Subscribers can add a product to a subscription without a change to the base plan. Limio shows only the add-ons that the current offer permits, and applies the charge from the order effective date.

Each offer controls its own list through the **Cross-sell add-ons** attribute. The [Compatible Add-ons](https://docs.limio.com/components/component-library/self-service-components/component-compatible-add-ons) component reads that attribute and displays the add-ons that are compatible with the plan the subscriber holds.

{% embed url="<https://69c2cf3a42a094f3cd354b8d-hbwumtssfk.chromatic.com/?path=/story/shop-components-self-service-compatible-add-ons--multiple-add-ons-available&full=1&shortcuts=false&singleStory=true&embed=true>" %}

Subscribers can:

* Buy an add-on on its own, effective immediately
* Buy an add-on at the same time as an upgrade or a downgrade
* Change the quantity of an add-on, including volume and usage pricing
* Remove an add-on

Limio keeps a compatible add-on when the subscriber changes offer. If the new offer does not list the add-on, Limio removes the add-on on the order effective date.

Add-ons use the Update Subscription flow. For the configuration steps, see [Create Update Subscription Experience](/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-configure-an-update-subscription-flow.md).

## **Cancel & Cancel/Save**

Subscribers can cancel a subscription by going into a dedicated experience. The experience can be customised to collect cancel reasons, offer special discounts, and be personalised. More details is available on [Create Personalised Cancel/Save Experience](/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-create-a-personalised-cancelsave-experience.md)

Limio can also refund the current term automatically when a subscriber cancels inside a cooling-off window. You set the window on the offer, and you set a different window for acquisition and for renewal.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-9b22714d35be5912adf18a84e3e6a445a20bd063%2Fimage%20(85).png?alt=media" alt=""><figcaption></figcaption></figure>

## **Renew subscription**

The Limio Self-Service portal can also detect subscriptions due for renewal or that are inactive and could be renewed. Learn more on [Create Personalised Renewal Experience](/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account/how-to-create-a-personalised-renewal-experience.md)

A subscriber can renew without an account, but not without a check. Limio verifies the subscriber in one of two ways:

* A link in a renewal email, which carries the hashed email address and the name
* Manual entry of the subscription reference and the postal code on your renewal page

Limio compares those values against the subscription. When the check passes, Limio issues a short-lived credential that is scoped to that one basket, and the subscriber completes the renewal.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-504cb1dfaf99985cee35371870edb58f16156bd9%2Fimage%20(87).png?alt=media" alt=""><figcaption></figcaption></figure>

## **Gift a Subscription and Redeem a Gift**

A customer can buy a subscription as a gift, and the recipient can redeem it with a gift code. The recipient does not give a payment method, because the purchaser has already paid for the term.

For the catalog and page setup, see [Guide: Sell subscription gift codes](https://docs.limio.com/guides/feature-implementation-guides/guide-how-to-sell-subscription-gift-codes-in-limio-commerce).

## **View Customer Details**

The Limio Self-Service portal can allow a customer to see and manage their personal details, such as their email, name, password and phone.

![Customer Table component](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-c7a63d079b2f1723aec5f58309a30b0f76cea836%2Fimage%20\(88\).png?alt=media)

## **View and Edit Addresses**

Billing and delivery addresses can be managed by subscribers in the Limio Self-Service Portal. Billing address will be tied to the payment methods, whereas the delivery address will only be shown for physical subscriptions.

![Edit Address component](https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-8677355344c21d93229eefa0fac79f38b6357bb8%2Fimage%20\(89\).png?alt=media)

## **Partner Self-Service**

A partner user can manage subscriptions for the customers they are responsible for. A partner can search their customers, view a customer's subscription, upgrade or downgrade it, add or remove add-ons, change quantity, cancel it, and view and download that customer's invoices.

Offers are scoped to a partner with the **Sales Channel** and **Eligible Partners** attributes, so a partner sees only the offers you permit. For the setup steps, see [Guide: Set up a Partner Portal](https://docs.limio.com/guides/feature-implementation-guides/guide-partner-portal).

## **Custom experiences**

Limio Self-Service uses the same component framework as the Limio Shop, and you can extend it to cover more use cases. Learn more at: [Custom Components](https://docs.limio.com/developers/custom-components/custom-components).

A custom component calls the same **Limio SDK** that the standard components use, so it starts from the same subscription data and submits through the same order pipeline. `initiateCheckout` opens a basket against an existing subscription for the order type you need, such as an offer change, a quantity change, an address change or a payment method change. See [Self-Service Checkout](https://docs.limio.com/developers/limio-sdk/self-service-checkout) and [Update Subscription Checkout](https://docs.limio.com/developers/limio-sdk/subscription-update-checkout).

The experiences below are not standard functionality. Limio customers built each one with custom components on the SDK. Use them as examples of what you can build.

**Account portal**

* A branded account home, with its own navigation, side panel and footer panel
* A context bar that stays on screen and shows the account name and the billing account identifier

**Renewal**

* A renewal cart and a plan overview for the next term
* An acknowledgement step that shows the new charge and the new date, with your own legal copy, before Limio creates the renewal basket
* A "renew without changes" action, for a subscriber who wants no change
* A configurable window that controls when the renew action becomes visible

**Plan and seat changes**

* Quantity steppers that bill an increase immediately and defer a decrease to the end of the term
* A page of checkboxes to remove products at renewal
* Provisioning forms that collect the data a seat change needs
* Automatic adjustment of an account-wide product when seat counts change

**Cancellation**

* A cancel journey that changes with the notice period, for example a form beyond 60 days and a modal inside 60 days
* An auto-renew switch, so a subscriber stops the next renewal instead of cancelling now
* A dialog that offers a hold, or the removal of an add-on, in place of a cancellation


---

# 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/product/self-service/what-are-the-standard-functionality-of-limio-self-service-manage-my-account.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.
