> 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/manage-pricing.md).

# Manage Pricing

Learn how to configure pricing on Limio Offers for Stripe Billing

When using Stripe as your billing provider, Limio fully owns the pricing. Limio defines the price on each Offer and dynamically creates Stripe Prices at order time. There is no need to pre-configure prices in the Stripe Product Catalog — Limio handles this automatically based on your Offer configuration.

As a reminder:

* A **Stripe Product** represents what you sell (e.g. "Premium Digital Subscription"). You create these in the Stripe Dashboard and link them to Limio via a Product Code.
* A [**Limio Offer**](https://docs.limio.com/product/pricing/what-are-offers-and-how-to-configure-them) is the customer-facing representation of a Stripe Product, enriched with pricing, display, and checkout behaviour fields.

To configure pricing for Stripe, you will need to:

1. **Link your Limio Products to Stripe Products** — see [Stripe Product Code](https://docs.limio.com/integrations/stripe-billing-integration/manage-pricing/stripe-product-code.md)
2. **Configure the price on your Limio Offers** — see [Using Limio Price with Stripe](https://docs.limio.com/integrations/stripe-billing-integration/manage-pricing/using-limio-price-with-stripe.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limio.com/integrations/stripe-billing-integration/manage-pricing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
