Glossary

Stripe Inline Price (price_data)

A Stripe inline price is a price defined on the spot with the price_data parameter when you create a Checkout Session, Payment Link, subscription or invoice item, instead of referencing a saved Price by its ID.

Also called: price_data, inline pricing, ad hoc price

14-day free trial · card required · cancel anytime

Definition

Most Stripe integrations charge against a catalog: you create a Product, give it one or more Prices, and pass a Price ID whenever you sell it. An inline price skips the catalog step. Your code sends the amount, the currency and, for recurring billing, the interval inside price_data, and Stripe uses them for that one session, subscription or invoice item.

Stripe describes inline pricing as defining “the price for your customer when you create a subscription, invoice, Checkout Session, or Payment Link.” It is an API feature only. Stripe’s guide says “You can only create inline prices through the API,” so there is no inline price option in the Dashboard.

The trade-off is permanence. Stripe states: “You can’t update or reuse inline prices after you create them.” Each inline price belongs to the transaction that created it, which is exactly why it suits amounts that change every time and exactly why it complicates reporting.

Key points

  • +Passed as price_data in place of a Price ID, on Checkout Sessions, Payment Links, subscriptions, subscription schedules and invoice items.
  • +API only: Stripe says you can only create inline prices through the API.
  • +Stripe: “You can’t update or reuse inline prices after you create them.”
  • +By default the Price Stripe generates is marked active=false, which Stripe calls “effectively archived.”
  • +Generated Prices don’t appear in product searches or lists in the Dashboard.
  • +On a subscription, price_data needs an existing product ID. Checkout can also define the product inline with product_data.
  • +Each inline-priced sale carries its own Price, so the Product, not the Price, is the stable identifier.

What goes inside price_data

The fields depend on where you use it. Every version takes a currency and an amount, given as unit_amount in the smallest currency unit or as unit_amount_decimal, and an optional tax_behavior.

On a Checkout Session line item, price_data identifies the product in one of two ways: product, the ID of a Product you already have, or product_data, which defines the product inline and needs at least a name. Add recurring with an interval to make the line a subscription price.

On a subscription item, price_data requires product, the ID of an existing Product, plus recurring with an interval. There is no product_data option there, so a subscription with an inline price always points at a real Product in your catalog.

On an invoice item, price_data requires product and has no recurring settings, since an invoice item is a one-time charge.

What Stripe creates behind an inline price

An inline price is not priceless. Stripe’s guide to how products and prices work explains that using price_data “generates Price and Product objects that are relevant for the specific Checkout Session, Payment Link, or Subscription.” Invoice lines and subscription items still show a Price ID. It is simply a Price no one created in the catalog.

Those generated objects are kept out of sight. Stripe says that “While the Price objects are temporary and not visible in the Dashboard, the associated Product objects aren’t always temporary,” and that Price objects created with price_data “don’t appear in product searches or lists in the Dashboard.” Its price management guide adds that “By default, prices created with price_data are effectively archived (they’re marked as active=false).”

This is the usual explanation when someone finds a price or product ID on an invoice that they can’t find by browsing the product catalog: an integration created it inline.

When an inline price is the right tool

Stripe names two situations. One is a catalog that lives somewhere else: “you might want to use inline prices when you manage your product catalog outside of Stripe.” If your own system already holds the price list, creating and maintaining a matching Price in Stripe for every item duplicates it.

The other is an amount that is different every time. Stripe’s example is “a user-selected donation amount,” where you create the product but not a price, and pass the amount with price_data when you create the Checkout Session, Payment Link or subscription. Quotes, custom contracts and usage totals computed in your own code fit the same pattern.

If the amount is fixed and you sell it repeatedly, a saved Price is the better choice. It can be reused, shows up in the Dashboard, and gives every sale the same Price ID to report on.

Why inline prices change how you report

Reporting by Price works when every sale of a plan carries the same Price ID. Inline prices break that. Because an inline price can’t be reused, two customers on the “same” inline-priced plan carry two different Price IDs, and a report grouped by Price shows them as unrelated items.

The Product is the identifier that survives, as long as your integration passes a product ID. On subscriptions and invoice items that is required. On Checkout it is your choice, and it is the better one: pass product with the ID of a catalog Product rather than product_data, and every inline-priced sale of that item shares one Product ID.

Amounts are an even weaker key. An inline price exists because the amount varies, so a rule or report that recognizes a sale by its total will miss most of them. When an item has no stable Product either, metadata you set on the subscription or payment is the remaining way to label the sale.

How inline-priced sales reach QuickBooks with Acodei

On real-time accounts, Acodei books a successful Stripe charge as a QuickBooks sales receipt by default, with line items resolved through product mapping. Accounts on the daily balance summary get one aggregated receipt per day instead of a record per charge. With Invoice Sync on, each line of a synced invoice uses the product returned by Multiple Product Mapping, or the default product.

For inline-priced sales, choose the mapping rule by what stays the same. Stripe Product mapping without the pricing tier routes every charge and invoice for a Stripe product to the same QuickBooks product, regardless of which Stripe price was used, so it fits inline prices that point at a catalog Product. Mapping with the pricing tier stores both the Product ID and the Price ID, which is how a saved monthly Price and annual Price on one product reach different QuickBooks products. Stripe generates a new Price for every inline-priced sale, so the Product is the identifier to map on. Transaction Value mapping compares the gross amount to a fixed value, so it cannot follow amounts that vary.

Where there is no stable Product, metadata mapping is the fallback. Acodei reads metadata from the charge, the PaymentIntent, the invoice and the subscription, in that order. A sale that matches no rule goes to the default product or raises a sync error, depending on your settings.

Want to see this on your own Stripe data?

Start a free trial

14-day free trial · card required · cancel anytime

Frequently asked questions

What is price_data in Stripe?

price_data is the parameter that creates an inline price. Instead of passing the ID of a saved Price, you pass the currency, the amount and, for subscriptions, the recurring interval when you create a Checkout Session, Payment Link, subscription or invoice item. Stripe uses those values for that transaction only.

Can I reuse or update a Stripe inline price?

No. Stripe states that you can’t update or reuse inline prices after you create them, and by default the generated Price is marked active=false. To charge the same amount again, pass price_data again, or create a saved Price on the Product if the amount is fixed.

Why can’t I find an inline price in the Stripe Dashboard?

Stripe keeps them out of the catalog. Prices created with price_data don’t appear in product searches or lists in the Dashboard, although Stripe notes you can still open one directly by its URL. The generated Product may persist, and Stripe says those Product objects aren’t always temporary.

Does a subscription with an inline price need a Product?

Yes. On a subscription item, price_data requires the ID of an existing Product and a recurring interval. Only Checkout lets you define the product inline with product_data. That makes subscription inline prices easier to report on, because every sale shares the Product ID you passed.

How should inline-priced Stripe sales be mapped to QuickBooks products?

With Acodei, map them by Stripe Product ID without the pricing tier, which sends every price on that product to the same QuickBooks product. Transaction Value mapping compares the gross amount to a fixed number, so it can’t match amounts that vary. If there is no stable Product, use metadata mapping.

What customers say about running Stripe through Acodei

Stripe Verified Partner BadgeIntuit QuickBooks
★★★★★
“If you're testing out all the different Stripe/QuickBooks integration apps right now, let me save you some time. This one is the best one by far.”
RyanOwner at Indie Music Academy
★★★★★
“Works well and is really helpful for massive transactions. The support is really fast and helpful. 100% recommended.”
AndresCo-founder and CEO at Kanguro Collections and Reinsurance

Related reading

More glossary terms

See the full glossary

Ready to try Acodei?

Connect Stripe to QuickBooks Online in minutes and let the fees, refunds, and payouts land where your accountant expects them.

14-day free trial · card required · cancel anytime