> For the complete documentation index, see [llms.txt](https://docs.tiun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiun.io/reference/generic/products.md).

# Products

Everything you sell on tiun is modeled as a **product**. Every product combines a **product type** — what you're selling, which determines how it's taxed — with a **pricing model**, which determines how and when the customer is charged. There are three pricing models available today, each matching a different access pattern, with **usage-based billing** on the way.

You set both in the same form when you create a product. Picking a pricing model changes the fields below it — an interval, a price and an optional trial for a subscription; a single price for a one-time purchase; an interval fee and a monthly limit for time-based billing.

|                  | **Subscription**                                                  | **One-time purchase**                                               | **Time-based billing**                                  |
| ---------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------- | ------------------------------------------------------- |
| **Interval**     | A count plus a unit — day, week, month, or year                   | —                                                                   | Minutes only                                            |
| **Amount**       | **Price**, charged at the start of each interval                  | **Price**, charged once                                             | **Interval fee**, charged at the start of each interval |
| **Spending cap** | —                                                                 | —                                                                   | **Monthly limit**, per calendar month                   |
| **Trial**        | Optional — **trial length** and **trial amount**, charged upfront | —                                                                   | —                                                       |
| **Access**       | Continuous while the subscription is active                       | Permanent, or a set time with **limited access**                    | While the billing session is active                     |
| **You call**     | `tiun.checkout({ productId })`                                    | `tiun.checkout({ productId })` — plus a `referenceId` if repeatable | `tiun.start()`                                          |

Every amount is in your account's [currency](#currency). Each pricing model is described in full below.

***

## Subscription

Subscriptions charge users on a **fixed schedule**. You set the **interval** as a count plus a unit — day, week, month, or year — so *every 1 month* and *every 3 months* are both valid. The **price** is charged at the start of each interval.

A **trial period** is optional. When you enable it you set a **trial length** (a count plus a unit) and a **trial amount**, charged upfront: enter `0` for a free trial, or anything below the subscription price for a discounted one. The full price applies from the first interval after the trial.

Subscriptions fit SaaS, membership sites, and any product where access is continuous and priced like a membership.

Subscription products integrate through `tiun.checkout({ productId })`. See [Checkout / How it works](/reference/checkout/how-it-works.md) and [Subscriptions](/reference/checkout/subscriptions.md) for the flow.

***

## One-time purchase

One-time purchases charge a **single price**, paid at checkout, with no interval, no trial, and no renewal. Besides the **price**, two optional settings change how a purchase behaves:

* **Limited access** — access ends a set time after each purchase: a count plus a unit (day, week, month, or year). When it's off, access never expires.
* **Repeat purchases** — customers can buy the product any number of times, paying the price each time. Each purchase is tied to a **reference ID** your app passes to checkout. When it's off, each customer can buy the product once, or again after limited access ends.

One-time products fit consulting engagements, lifetime licenses, and a single course or report. Repeatable ones fit things bought again and again — single articles, bookings, tickets — and limited access fits passes that last a set time. See [repeatable one-time purchases](/guides/one-time-purchases/repeatable-one-time-purchases.md).

One-time products integrate through `tiun.checkout({ productId })` — the same call as subscriptions. See [Checkout / How it works](/reference/checkout/how-it-works.md) and [One-time purchases](/reference/checkout/one-time-purchases.md) for the flow.

***

## Time-based billing

Time-based billing charges for **time spent** with your content rather than a flat membership. Billing is metered in **minutes** — the only interval unit for this pricing model. You set the **interval fee**, charged at the start of each interval, and a **monthly limit** capping what a user can be charged in a calendar month.

Time-based products fit news, podcasts, video streaming, magazines — anywhere value tracks engagement.

Time-based products integrate through `tiun.start()`. See [Time-based / How it works](/reference/time-based/how-it-works.md) for the flow.

***

## Currency

Every price you set — a subscription price, a one-time price, a trial amount, an interval fee, a monthly limit — is denominated in **your account's currency**. You choose it during onboarding — it defaults to the currency of your business's country — and the new-product form shows it next to each amount rather than asking again per product.

This is separate from your **payout currency** — the currency your revenue is paid out in — which you set as **Payout currency** when you [enable payouts](/guides/getting-started/enable-payouts.md).

You do not set a currency per product, and you do not price the same product in several currencies. See [creating a profile](/guides/getting-started/create-a-profile.md) for where this is chosen.

***

## Tax category

Every product is filed under a **tax category** when you create it — the **Product type** field in the new-product form, described there as determining how tax is applied at checkout. tiun is the Merchant of Record for your sales, so this is what determines how the product is taxed in each jurisdiction — see [Tax and Compliance](/faq.md) in the FAQ for what that means for you.

The dashboard shows the available types as cards with a short description, and guidance on where each one ends behind the info icon. Pick the one your product **genuinely** belongs to rather than the closest-looking match.

The list is **closed** — it is not free text, and there is no default.

If nothing on it fits what you sell, choose **Not on the list? Tell us what you sell** below the types in the new-product form at [my.tiun.business](https://my.tiun.business/) and describe your product; tiun reviews it and gets back to you rather than you filing it under an approximate category. **This is dashboard-only.** It is not offered over the [MCP server](/guides/agent-integration/agent-integration.md), so an agent cannot send it on your behalf. When no category fits, an agent should stop and hand that step back to you rather than settling for the nearest match.

{% hint style="warning" %}
**A tax category is permanent.** It is fixed when the product is created and cannot be edited afterwards — not in the dashboard, and not through the [MCP server](/guides/agent-integration/agent-integration.md). The only way to correct one is to archive the product and create a new one, and archiving cannot be undone: there is no restore. Get it right at creation.
{% endhint %}

***

## Tax behavior

Subscription and one-time products include a **tax behavior** field. **Automatic** is the default: tiun uses the end customer's location and applies the usual pricing convention for that region — tax-inclusive or tax-exclusive.

**Include tax** means the price shown includes tax. **Exclude tax** means tax is added on top at checkout.

***

## Product IDs

Every product gets a **unique product ID** like `p-live-pro`. The ID is stable and used everywhere you reference the product: `tiun.checkout()`, entitlement checks, analytics correlation.

Live and sandbox are **independent parallel catalogs** — you create products in each environment separately, and IDs never cross over. Product IDs are prefixed by environment: `p-live-...` for live and `p-test-...` for sandbox. See [Sandbox](/reference/generic/sandbox.md) for how the two environments work.

Find a product's ID on its detail or edit page in the [my.tiun.business dashboard](https://my.tiun.business/).

***

## Mix and match

A single tiun account can include **multiple pricing models** at once — for example a subscription for your core SaaS, a one-time purchase for a lifetime license, and a time-based offering for premium media. Each product is configured and called independently.


---

# 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.tiun.io/reference/generic/products.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.
