Glossary

Stripe Customer-Chosen Price (custom_unit_amount)

A Stripe customer-chosen price is a one-time Price with custom_unit_amount enabled, so the customer types the amount on a Checkout page or Payment Link, optionally starting from a preset and kept between a minimum and a maximum you set.

Also called: custom_unit_amount, pay what you want, Customer chooses price

14-day free trial · card required · cancel anytime

Definition

Most Stripe Prices fix the amount when you create them. A customer-chosen price fixes everything except the amount. You create it once, on a Product, and every customer who pays through it decides what the line is worth.

In the API it is the custom_unit_amount object on the Price. Stripe’s API reference describes it as configuration “for the amount to be adjusted by the customer during Checkout Sessions and Payment Links.” In the Dashboard the same pricing model is called “Customer chooses price”, and Stripe’s guide to it is titled “Let customers decide what to pay”.

Stripe lists three uses for it: to “collect a tip for a service provided, accept donations for a cause, or give your customers the option to pay what they want for your product or service.” The common thread is that the amount is the customer’s decision, which is exactly what makes these payments different from everything else in your revenue once they reach the books.

Key points

  • +Set on the Price as custom_unit_amount, with enabled (required) and three optional fields: preset, minimum and maximum.
  • +A Price needs one of unit_amount, unit_amount_decimal or custom_unit_amount, unless it is tiered.
  • +Stripe: this pricing model “is only compatible with Checkout and Payment Links.”
  • +One-time only. Stripe states it does not support recurring payments.
  • +The line must be the only line item, with a quantity of 1.
  • +No promotion codes or discounts can be applied to it.
  • +The minimum “Must be at least the minimum charge amount.”

Preset, minimum and maximum

The custom_unit_amount object has four fields. enabled is required: Stripe says to “Pass in true to enable custom_unit_amount, otherwise omit custom_unit_amount.” The other three shape what the customer sees.

preset is “The starting unit amount which can be updated by the customer.” It is the number already in the box when the payment page loads, so it works as a suggested amount. minimum is “The minimum unit amount the customer can specify for this item”, and Stripe adds that it “Must be at least the minimum charge amount”, the smallest charge Stripe will process in that currency. maximum is “The maximum unit amount the customer can specify for this item.”

All three are integers in the smallest currency unit, the same convention as unit_amount. A preset of 2500 on a USD price is 25.00 USD. Like every Price amount setting, they are fixed once the Price exists: Stripe allows only a Price’s metadata, nickname and active fields to change after creation, so a new suggested amount means a new Price.

Where a customer-chosen price works, and where it does not

Stripe’s product guide is explicit that this pricing model “is only compatible with Checkout and Payment Links”, and that “Customer chooses price supports only one-time prices.” You can’t subscribe a customer to it, add it to an invoice you send, or charge it from your own payment form.

The pay-what-you-want guide lists the limits that apply inside Checkout: “You can’t add any other line items and the quantity can only be 1.” “You can’t use promotion codes or discounts with them.” “They don’t support recurring payments or optional items.”

That makes a customer-chosen price a single-purpose page: one product, one amount, one payment. If you want a suggested tip on top of a fixed-price purchase, or monthly giving at an amount the donor picks, it is not the tool. Monthly giving is usually built from a few fixed recurring prices instead.

Customer-chosen price compared with an inline price

Stripe’s guide points to a second way to charge a variable amount: inline pricing, where you pass price_data with the amount when you create the Checkout Session. The difference is who picks the number. With an inline price your code sets it before the page loads. With a customer-chosen price the customer sets it on the page.

Stripe also notes that “you can’t reuse or update inline prices, and they’re only available through the API.” A customer-chosen price is a normal, reusable Price on a Product, which means every payment through it shares the same Product ID and Price ID no matter what amount was entered.

Why every sale lands at a different amount

With a fixed price, the amount tells you what was sold: 49.00 USD is the starter plan. With a customer-chosen price that link is gone. Five supporters of the same project might pay 5, 12, 25, 25 and 140 USD, and all five are the same product.

Anything in your books that identifies revenue by amount stops working for these payments. That includes reconciliation habits like spotting a product by its price on a bank line, reports that group by amount, and any bookkeeping rule that keys on a fixed value. What stays constant is the Product and the Price, so those are the identifiers to build around.

How customer-chosen payments reach QuickBooks with Acodei

Unless you turn on post-purchase invoices in Checkout, a payment through a customer-chosen price is a single Stripe charge with no invoice behind it. On real-time accounts, Acodei books a successful Stripe charge as a QuickBooks sales receipt by default, with line items resolved through product mapping and unmapped lines sent to the default product. Accounts on the daily balance summary get one aggregated receipt per day instead of a record per charge.

The varying amount matters for which mapping rule you use. Acodei’s Transaction Value mapping compares the gross amount to a fixed value you enter, so a payment of 12 USD and one of 25 USD on the same price can’t both match one value rule. Map these payments by Stripe Product ID instead. Without the pricing tier, every price on that Stripe product goes to the same QuickBooks product. With the pricing tier, Acodei stores both the Product ID and the Price ID, so the customer-chosen price can go to its own QuickBooks product. If a payment matches no rule, it uses 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 custom_unit_amount in Stripe?

It is the setting on a Stripe Price that lets the customer choose the amount. Stripe describes it as configuration for the amount to be adjusted by the customer during Checkout Sessions and Payment Links. It has a required enabled flag and optional preset, minimum and maximum amounts, all in the smallest currency unit.

Can I use a pay-what-you-want price on a Stripe subscription?

No. Stripe states that customer-chosen prices support only one-time prices and do not support recurring payments. To let supporters give monthly, create a few fixed recurring prices, such as 10, 25 and 50 USD a month, and let them pick one.

Can I add a customer-chosen price to a cart with other items?

No. Stripe’s pay-what-you-want guide says you can’t add any other line items and the quantity can only be 1. Promotion codes and discounts can’t be used with it either, so it works best as a dedicated page for a tip, a donation or a single pay-what-you-want product.

What is the lowest minimum I can set?

Stripe requires the minimum to be at least the minimum charge amount for the currency, the smallest amount Stripe will charge. If you leave the minimum unset, that floor still applies. The preset is only a starting suggestion, and the customer can change it within your minimum and maximum.

How do I map pay-what-you-want payments to a QuickBooks product?

With Acodei, map them by Stripe Product ID rather than by transaction value. Transaction Value mapping compares the gross amount to a fixed number, so it can’t match amounts that change with every payment. Product ID mapping with the pricing tier can also send the customer-chosen price to its own QuickBooks product.

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