# Saved Payment Wallet

Allows returning subscribers to reuse saved payment methods across multiple subscriptions, rather than re-entering card details for each new purchase. This component works as a subcomponent in Limio's [Modular Checkout Components](/components/component-library/modular-checkout-components.md) . 

<figure><img src="/files/1jYQ8Rx2QzBe7lQ2so8v" alt=""><figcaption></figcaption></figure>

Note only works if your connected billing system (e.g. Zuora) supports one-account-to-many-subscriptions (1-N), so a single customer account can hold multiple subscriptions with shared payment methods.

## How it works

When a customer who already has a subscription returns to purchase a second product, the checkout recognises their existing account and surfaces their saved payment methods. No re-entry of card details, no friction — just select and confirm.&#x20;

This requires the tenant to be configured in 1-N mode (one account, many subscriptions) rather than 1-1 (one account, one subscription).

## Why it matters

Reduces checkout friction for customers with multiple subscriptions. This is standard in consumer e-commerce but rare in B2B subscription platforms. For publishers and SaaS companies where customers often hold multiple products or tiers, removing the payment step on repeat purchases is a direct conversion win.

***

{% hint style="info" %}
**This is a Labs feature.** We're experimenting with this and it's not yet part of the core platform. Interested in early access or want to help shape it?

[Request access →](mailto:hello@limio.com?subject=Labs%20—%20Saved%20Payment%20Wallet)
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.limio.com/labs/labs-components/saved-payment-wallet.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.