# What are products and prices?

> These are the ODUS guides for Core API v2. Core API v1 and Checkout SDK versions before 1.12.0 stop working at 00:00 UTC on 4 November 2026. See [Upgrading from v1 to v2](https://docs.odus.com/docs/guides/upgrading/v1-to-v2.md). Every page is listed in [llms.txt](https://docs.odus.com/llms.txt). To read your own ODUS data, [connect your AI assistant to the ODUS MCP server](https://docs.odus.com/docs/guides/ai-connector.md).

In ODUS, **products** and **prices** are the building blocks for billing. Before you can create a subscription or charge a customer, you need at least one product with at least one price attached to it.

## Products

A product represents a sellable item or service in your catalog — for example, a SaaS plan, a physical product, or a content subscription. A product does not contain any billing information on its own. It has a name, an optional description, and an optional statement descriptor.

The statement descriptor is the text that appears on a customer's bank statement when they are charged. It is limited to 22 characters.

A product can also have a **statement descriptor suffix**: a short text that some gateways add after your account's own descriptor instead of replacing it. See [Statement descriptors](#statement-descriptors).

## Prices

A price defines the billing terms for a product. Every price belongs to exactly one product and specifies:

* The **amount** to charge, in the smallest currency unit (for example, cents for USD).
* The **currency** to charge in.
* The **type** of charge: either `one_time` or `recurring`.

### One-time prices

A one-time price charges the customer a fixed amount exactly once. This is suitable for setup fees, lifetime access purchases, or any charge that is not repeated.

### Recurring prices

A recurring price charges the customer on a repeating schedule. The price's `amount` is what each billing cycle charges, in the smallest currency unit, and its `recurringSchedule` sets how often:

| Field           | Description                                                                                     |
| --------------- | ----------------------------------------------------------------------------------------------- |
| `intervalUnit`  | The unit of time for the billing interval: `minute`, `hour`, `day`, `week`, `month`, or `year`. |
| `intervalCount` | The number of units between each charge. For example, `1` with `month` means monthly.           |
| `trial`         | Optional. A first cycle with its own `intervalUnit`, `intervalCount` and `amount`.              |

For example, a monthly plan at $29.99 has `amount: 2999` and `recurringSchedule: { "intervalUnit": "month", "intervalCount": 1 }`. See [Attaching a recurring price](https://docs.odus.com/docs/guides/products/creating-products-and-prices.md#attaching-a-recurring-price) for a full request.

## Multiple prices per product

A product can have more than one price. This is how you offer different billing options for the same service. For example, a "Pro Plan" product might have a monthly price and an annual price. When creating a subscription, you specify which price to use, not just which product.

This also makes it possible to add new pricing options later without touching existing subscriptions. Existing subscriptions keep their original price until you explicitly change them.

## Products, prices, and subscriptions

When a customer subscribes to something, you create a subscription by referencing a price. ODUS looks up the product and recurring schedule from that price automatically. The subscription then renews according to that schedule.

This relationship can be summarised as:

* A **product** describes *what* is being sold.
* A **price** describes *how* it is billed.
* A **subscription** is a specific customer's active agreement to be billed according to a price.

## Names shoppers see

Price and product names are not internal labels. Every line item in a payment has a description that is sent to the payment provider as the item name, so shoppers can see it, for example on PayPal order sheets and wallet screens. When you create a payment without a `description` on a line item, ODUS fills it in from a name:

| Line item description setting | The shopper sees     |
| ----------------------------- | -------------------- |
| **Price name** (default)      | The price's `name`   |
| **Product name**              | The product's `name` |

Name your prices the way you want shoppers to read them. If your price names are internal labels such as `Monthly USD Tier 2`, switch the [Line item description](https://docs.odus.com/docs/guides/dashboard/merchant-configuration.md#line-item-description) setting to **Product name**, or send a `description` on each line item.

A product's `description` is never shown to shoppers.

note

Renaming a price or product, or changing the setting, does not change payments already made: each line item keeps the description it was created with. A subscription renewal is a new payment, so it shows the name and setting in effect when it is charged.

## Statement descriptors

Card statements show at most 22 characters, and gateways build that text in one of two ways. That is why a product has two descriptor fields:

| Field                       | What the gateway does with it                     | Used by                                                           |
| --------------------------- | ------------------------------------------------- | ----------------------------------------------------------------- |
| `statementDescriptor`       | Replaces your account's descriptor with this text | Adyen, Checkout.com, and Stripe by default                        |
| `statementDescriptorSuffix` | Adds this text after your account's descriptor    | PayPal, and Stripe when the gateway profile's suffix option is on |

Write the suffix to be read after your account's descriptor, and keep it short. The gateway shows your account's descriptor, a separator, then the suffix, and cuts the line at 22 characters. For example, with the account descriptor `ACME`, the suffix `PRO PLAN` reads `ACME* PRO PLAN` on a Stripe statement.

* **PayPal** sends the suffix when the payment has one, and the full descriptor otherwise.
* **Stripe** sends the full descriptor unless you turn on **Send the statement descriptor suffix instead of the full descriptor** on the gateway profile; see [Stripe](https://docs.odus.com/docs/guides/integrations/gateways/stripe/.md#statement-descriptors).

A payment takes both values from the product of its first cart item. You can override either one when you create the payment, and each falls back to the product separately. Subscription payments take them from the subscribed product.
