Skip to content
Creem
Back to blog

Pay as You Want Pricing: A Practical Guide for Sellers

Pay as you want pricing guide: floor, anchor, and customer choice explained.

Table of Contents

Pay as you want pricing lets the customer choose the payment, and that can include zero when the seller allows it. Generosity alone rarely carries the model. A survey of field experiments from 2009 to mid-2015 by Greiff and Egbert found average payments below $10 in all but a few studies and often below $1, with zero-payment shares as high as 46.5%.

Sellers often hear, “Let customers pay what feels fair,” as though generosity does the commercial work. For a digital product, the more important question is how the checkout defines “fair” before the buyer types anything. One buyer has a limited budget, another is purchasing for a business, and a third wants to support an independent maker. A single fixed price can lose some of those buyers. An unstructured payment field can lose the seller.

So decide your controls before launch: a minimum, a suggested price, or neither. Know who carries the tax on each sale. Then test net revenue per visitor against a fixed price.

What Pay as You Want Really Means

Start with three fields. Only the customer's chosen amount is part of the model itself. The minimum and the suggested price are controls the seller adds on top.

The minimum price is the floor. It defines the least the seller will accept for access, a download, a license, or another digital entitlement. The floor can protect payment-processing costs, support obligations, and the basic economics of delivering the product.

The suggested price is the anchor. It gives the customer a reference point for interpreting the product's value. Without an anchor, buyers must invent their own reference, often by comparing the product with something cheaper, free, or unfamiliar.

The chosen amount is the customer's decision. It can equal the minimum, match the suggestion, or exceed it. That amount isn't merely a payment. It can also reveal how different segments perceive the product, provided the seller analyses the full distribution rather than relying only on an average.

A coffee shop makes the structure easy to see. A sign that reads, “Latte, pay $3 or more, suggested $5,” is running pay as you want pricing. The cafe isn't operating a charity jar. It has established a revenue floor, offered a social reference, and allowed customers to reward the experience with a larger payment.

Pay as you want pricing illustration 1

Why each lever matters

The floor is a margin guard. It filters out payments that can't support delivery or administration, although a high floor may discourage price-sensitive visitors.

The anchor is a perception lever. It tells customers what a normal or fair payment might look like, reducing uncertainty and influencing the amount they enter.

The chosen amount is a market signal. It shows what customers pay when the seller offers flexibility, but it must be interpreted carefully. A low payment can indicate low perceived value, a constrained budget, a weak anchor, or a buyer who would never have purchased at the fixed price.

That last point prevents a common analytical mistake. A customer who pays a small amount under PWYW isn't necessarily a lost full-price sale. The relevant comparison is the revenue and strategic value of the flexible offer against the fixed-price alternative, including conversion, support costs, refunds, and future purchases.

Central principle: Pay as you want outcomes are engineered through the floor, anchor, and customer choice. They aren't generated by generosity alone.

A Brief History of Pay as You Want

Pay as you want pricing became widely visible through high-profile launches, but those examples can make the model look easier than it is. Radiohead's In Rainbows brought flexible payment into mainstream discussion, followed by platforms such as Humble Bundle and experiments from independent software makers. Each case paired the payment choice with a particular audience, product, story, or reference point.

The wider research record is large but lopsided. A review of empirical PWYW research identified 72 empirical studies across 97 independent datasets published between 2006 and 2016, and the 96 datasets that reported sample sizes covered 30,634,507 transactions. 98.7% of those transactions came from two studies: Bourreau et al.'s music-album sales and Gneezy et al.'s roller-coaster ride photos.

The payment distribution also matters more than the headline question of whether customers pay. Buyers usually paid something, yet payments were often modest. Individual studies recorded zero-payment shares of 19.3%, 20.0%, 21.5%, 34.8%, and 43.0%.

The same body of findings includes outcomes closer to ordinary pricing. In Kim, Natter and Spann's three field studies, consumers paid about 86% of their own reference price on average, meaning what they normally paid for such items. Against the regular price, results ranged from 10.62% above for hot beverages to 28.72% below for cinema tickets and 19.37% below for restaurant buffet lunch. The survey of PWYW findings reports these comparisons.

Real-world pay as you want outcomes

CaseYearModelAverage paidZero-payment or anchor effect
Radiohead, In Rainbows2007Flexible digital album pricingNot established by the verified data providedZero-payment result is often discussed, but the specific figure isn't used here because it isn't included in the verified data
Humble BundleFrom 2010 onwardTiered digital bundle with flexible paymentNot established by the verified data providedCharity and tier structure are commonly discussed, but no verified average or distribution is supplied here
Field experiments in the research literature2006 to 2016 study windowPay what you wantOften below 10, and frequently below 1Individual studies recorded zero-payment shares from 19.3% to 43.0%
Reviewed field-study outcomesNot specified in the verified dataFlexible payment compared with regular priceAbout 86% of regular price on averageResults varied by product, from above to below the regular price

The evidence shows that context changes the economics of PWYW outcomes. Identity, community, charity, novelty, and a strong reference price can encourage payment. A generic digital product without trust, a clear anchor, or a reason to support the seller faces a harder test. For an indie software founder, the practical historical lesson is straightforward: famous launches demonstrate a payment environment, not a universal pricing formula. The floor, suggested anchor, and surrounding choice design determine whether flexibility produces useful revenue.

How the Pricing Mechanics Actually Work

Treat the checkout as a single design system, not as three unrelated settings. The floor determines who can complete the purchase, the anchor shapes what the payment feels like, and an optional ceiling defines how far the buyer can go.

The floor is the simplest control. A zero floor maximizes openness but allows zero-payment transactions, and the checkout then has to grant access without attempting a $0 card charge. A positive floor should cover direct costs, processing fees, and a refund buffer. The right floor depends on the product, the payment method, customer support burden, and whether the offer is a campaign or a permanent catalogue item.

Small payments lose a large share to fixed fees. At Creem's rate of 3.9% + 40¢ per successful transaction, a $1 payment pays $0.44 in fees, about 44% of the sale, while a $3 payment pays $0.52, about 17%. Delivery, support, and refunds come out of what remains. For a software seller, a test of $0, $1, and $3 floors starts there: begin with unit economics, then test whether the extra friction from a higher floor costs more conversions than it protects in revenue.

The suggested anchor works differently. It doesn't force a payment, and it doesn't change the minimum. It gives the buyer a benchmark, such as the product's former fixed price, a comparable competitor price, the cost of producing the product, or a rounded amount the seller considers fair. Sellers looking for a broader framework can compare this choice with guidance on how to price digital products, especially when deciding whether flexibility should replace or complement a fixed tier.

Pay as you want pricing illustration 2

The ceiling is optional

A ceiling limits the highest amount a customer can enter. Most digital sellers won't need one because an unrestricted upper amount creates optionality for supporters who want to pay more. A cap can make sense for a time-limited edition, a coordinated campaign, or a setting where unusually high payments would create accounting or fulfilment complications.

Each lever creates a different tradeoff:

  • Raise the floor: You may increase revenue per completed transaction, but some price-sensitive visitors may leave.
  • Raise the anchor: You may shift customer expectations upward, but an arbitrary reference can reduce trust.
  • Add a ceiling: You can make the offer feel controlled, but you compress the upside from high-intent supporters.

A checkout review should answer five questions:

  1. What direct costs must every completed transaction cover?
  2. Does the minimum clearly appear before the customer enters payment details?
  3. Why is the suggested price credible for this product and audience?
  4. Would an upper bound protect the offer, or just limit upside?
  5. Which result matters most, conversion, net revenue, data quality, or audience growth?

For SaaS teams comparing flexible pricing with metered alternatives, the distinction is also important. Usage-based pricing for software charges according to product consumption, while PWYW lets the customer choose the payment for access or delivery. They solve different pricing problems.

PWYW doesn't remove ordinary tax and consumer-protection duties. A digital seller still needs to determine whether a transaction creates sales-tax, VAT, GST, or income-tax obligations, and the answer can depend on the buyer's location, product classification, seller status, and registration position.

For a paid transaction, indirect tax is generally connected to the amount charged, not the suggested anchor. Article 73 of the EU VAT Directive bases the taxable amount on what the supplier receives from the customer, and the UK VAT guide calculates VAT on the value of the supply. A suggested price is a reference point, not automatically the taxable consideration. A zero-payment transaction can still create record-keeping and entitlement questions even when no payment is collected, so sellers shouldn't assume that setting the amount to zero makes compliance irrelevant.

Registration thresholds create another trap. Micropayments can feel too small to matter individually, but sellers need a jurisdiction-specific review of cumulative sales, customer location evidence, invoicing, and filing obligations. The table below is a high-level comparison, not legal advice.

Tax treatment of PWYW transactions by jurisdiction

JurisdictionTax applied toThreshold to registerReporting rule
EU VATThe actual consideration for a taxable digital supply, subject to the applicable place-of-supply rulesDepends on the seller's establishment, scheme, and applicable registration rulesMaintain transaction, location, and tax records and report through the applicable national or special scheme
US sales taxThe taxable selling price where the seller has the required nexusVaries by state and seller activityCollect and remit according to each relevant state's filing and reporting requirements
UK digital servicesThe taxable consideration for a relevant digital service, subject to UK rulesDepends on seller status, establishment, and applicable registration requirementsKeep evidence and report through the applicable UK tax process

Consumer wording and refunds

Be precise with the word free. If a customer must pay a minimum, “free” can misdescribe the offer. Use language such as “choose your price, minimum required,” and show the floor beside the amount field rather than burying it in terms.

Refund policies should apply consistently whether the buyer paid $0, $1, or $20. A customer-selected amount doesn't eliminate disputes, chargebacks, or obligations created by consumer law, so keep your own refund policy separate from the rights the law already gives the buyer. A $0 order has no payment to return, but access still needs handling. Define whether a refund returns the payment, revokes the license, or handles a partial refund, and make those terms visible before purchase.

A merchant-of-record workflow can reduce operational complexity, but it doesn't replace product-specific legal review. Sellers comparing their options may also consult this sales tax internet sales compliance guide before launching across jurisdictions.

Pros and Cons for Digital Product Makers

PWYW wins when market structure gives flexibility a specific role. For a digital maker, that role may be reach, learning, or supporter participation. A buyer who rejects a fixed price may still download, use, and recommend the product when the payment barrier is lower. The resulting audience can provide feedback and reveal which users attach meaningful value to the work.

The model also exposes information that one fixed price conceals. A seller can examine how payments cluster around the minimum, suggested amount, and higher values, then compare those patterns across acquisition sources or customer types. The average payment is only part of the picture. The distribution shows whether the floor is carrying the offer, the anchor is shaping choices, or a smaller group of supporters is lifting revenue.

Pay as you want pricing illustration 3

The upside case

  • Lower entry friction: Visitors can choose an amount that fits their circumstances rather than accepting one fixed price.
  • Broader discovery: A flexible offer can attract curious buyers who are unwilling to make a full-price commitment.
  • Useful willingness-to-pay data: Chosen amounts can indicate whether an audience sees the product as a utility, community project, or premium tool.
  • Goodwill and sharing: Customers who feel respected may become advocates, especially when the product has an identity or mission beyond the transaction.
  • Campaign flexibility: PWYW can serve as a launch mechanism, experiment, donation-adjacent offer, or audience-building event.

The financial trade-off is uncertainty. Cash-flow forecasts become less reliable when payment patterns shift with traffic source, audience composition, season, or anchor wording. A low average can also hide two different groups: high-paying supporters and many users who contribute little or nothing.

The downside case

  • Zero-payment exposure: Field research reviews report recurring zero-payment outcomes, showing that non-payment is a design risk rather than a rare edge case.
  • Unstable revenue: A seller may gain users while receiving less dependable revenue per visitor.
  • Weak or arbitrary anchors: An unexplained suggested amount can seem manipulative or meaningless.
  • Refund ambiguity: A named price does not resolve disputes when the product fails to meet expectations.
  • Messy SaaS metrics: ARPU, LTV, and expansion analysis become harder to interpret when customers choose materially different entry payments.

PWYW often fits a short campaign better than an evergreen default. A campaign can give the floor and anchor a defined purpose, audience, and measurement window. A permanent catalogue needs unit economics that tolerate users who never become meaningful sources of revenue. The model pays off when its choice architecture produces useful reach or learning without allowing the lowest payment option to determine the business by accident.

How to Set Up Pay as You Want for Your Product

Begin with a product-fit audit. PWYW is easier to test when digital delivery has low marginal cost, the audience already trusts the maker, and the product has a natural path to upgrades, services, subscriptions, or community participation. It's harder when every customer creates substantial support work or when the product looks interchangeable with lower-priced alternatives.

Build the offer before the checkout

Set the minimum from costs, not optimism. Include payment-processing fees, delivery expenses, customer support, refunds, and a modest margin buffer. If a zero floor is strategically important, label it as an intentional acquisition cost and measure whether those users create later value. Don't disguise a required minimum as “free.”

Choose a suggested anchor with a reason buyers can understand. A previous fixed price, a comparable product, or a clearly described supporter amount is more credible than an unexplained number. Test different anchors against a fixed-price control where your traffic and experiment design allow it, and avoid changing the floor and anchor at the same time if you want to learn which lever caused the result.

Here is wording you can adapt for each kind of anchor:

Anchor basisCheckout wording you can adaptWhat makes it credible
Former fixed priceMinimum [minimum]. Suggested [suggested amount], the price this sold for before.The product really sold at that price, for the same files and access. Skip any savings claim.
Comparable productMinimum [minimum]. Suggested [suggested amount], in line with similar products of this scope.The comparison is to products with the same scope, and you can name them if a buyer asks.
Voluntary supporter amountPay [minimum] for the full product. Pay [suggested amount] or more if you want to support future updates.Paying more is optional and the product is identical at every amount. No guilt prompts.

The checkout should place the amount field beside a clear statement such as “minimum required”, and show the suggested amount as a suggestion, apart from the minimum. Show what the customer receives, whether the amount is one-time or recurring, and what happens after payment. If a higher payment unlocks a bonus such as extra files, list what each level adds before the buyer pays. A vague field creates hesitation, while a transparent field lets the buyer make an informed choice.

Connect operations to measurement

Tax collection requires more than adding a payment button, and who carries it depends on the model behind your checkout. Tax-calculation software calculates and collects tax for you, but you stay the seller of record, so registration and filing stay with you. A merchant of record becomes the legal seller on each transaction and takes those duties on.

Creem works this way. It calculates, collects, files, and remits VAT, GST, and sales tax, issues the buyer's invoice, and handles fraud and chargebacks. You can see how that fits a store in Creem's digital product store and checkout automation. You still build, deliver, and support the product, check how it is classified for tax, and keep your own income tax.

Log the complete payment distribution. Capture the minimum, the suggested amount, higher payments, zero-payment attempts if permitted, completed purchases, refunds, chargebacks, acquisition source, and product usage after purchase. If you allow a zero minimum, record each completed $0 checkout as a completed purchase with an amount of zero, and count visitors with the same eligibility rules and observation window for the PWYW offer and the fixed-price control. The mean alone can hide whether most buyers paid near the floor or whether a small supporter group produced the revenue.

Use a practical measurement checklist:

  • Conversion: Track two rates. Checkout conversion is completed purchases divided by checkout visitors, and offer conversion is completed purchases divided by all eligible offer visitors.
  • Payment distribution: Review median, modes, floor concentration, and higher-payment frequency.
  • Net revenue per visitor: Divide net revenue by the eligible visitors assigned to that offer. Net revenue is what's left after fees, refunds, taxes borne by the seller, and support costs.
  • Retention signals: Track activation, repeat purchases, upgrades, and subscription starts.
  • Audience segments: Separate buyers by payment behavior and acquisition source for later nurture campaigns.

Run the test long enough to observe different traffic sources, but stop if the floor fails to cover the basic economics. PWYW isn't a permission to postpone measurement.

When Pay as You Want Beats Fixed Pricing

PWYW doesn't win because customers admire generosity. It wins when the market structure gives flexibility a job to perform.

Three conditions usually point toward a worthwhile pilot. First, the seller needs a high-traffic top of funnel, because low payments require enough visitors to create meaningful aggregate revenue. Second, the purchase context should be partly non-transactional, such as an experiment, donation-adjacent project, awareness campaign, or community-driven release. Third, distribution should be inexpensive and the product should offer distinctive value rather than competing as a commodity.

Academic work supports a conditional interpretation rather than a universal one. The foundational marketing research on PWYW describes a model in which buyers commonly pay something and sellers can generate positive revenue, but later reviews and newer theory emphasize that zero-price behavior and market structure remain central to the outcome. The foundational PWYW marketing research is a useful starting point for that more cautious view.

Two products, opposite decisions

Consider a $9 indie SaaS tool with a small audience and a direct transactional use case. If the product already converts visitors at a healthy fixed-price rate, replacing the price with an open field may trade reliable revenue for uncertain payment amounts. The seller may be better served by a free trial, a low-cost entry tier, or usage-based billing.

Now consider a viral creator with 500,000 newsletter readers distributing a distinctive digital asset. The creator has a large audience, low delivery cost, and a community context that can make voluntary support meaningful. PWYW still needs testing, but the model has a plausible strategic role because the seller can use access, sharing, and supporter payments together.

A fixed control remains essential because a higher number of downloads doesn't automatically mean higher net revenue.

Signals for a pilot

Pilot PWYW when:

  • your audience has a strong relationship with the maker or mission;
  • the product is distinctive and cheap to distribute;
  • you want willingness-to-pay data, not only immediate revenue;
  • you can define a floor without damaging the offer;
  • the checkout can test anchors against a fixed alternative;
  • your team can handle refunds, taxes, support, and payment analytics.

Avoid switching the entire catalogue at once. Run a controlled experiment with one product, a clear minimum, a defensible suggested amount, and a fixed-price comparison. Measure net revenue per visitor and the full payment distribution before deciding whether pay as you want belongs in your permanent pricing strategy.

Creem puts checkout, one-time payments, subscription billing, receipts, and digital delivery in one platform. As the merchant of record, Creem is the legal seller and handles the tax on every sale.

Pay what you want on Creem works on one-time products, not subscriptions. The product price is the minimum, an optional suggested price at or above it pre-fills the checkout, and buyers pick Choose price to enter their own amount. If you're testing pay as you want pricing, set your floor and your suggestion, and let Creem carry the tax side of each sale.

Frequently Asked Questions

Yes. You can sell a lawful product using pay as you want pricing. Describe what the buyer gets, state the payment terms, and honor mandatory consumer rights as well as your refund policy.

Can the minimum price be zero?

Yes, a pay as you want offer can allow $0. A free order still needs delivery and a record, so your checkout should send the product and log each $0 order as a completed purchase in your reports.

Is tax charged on the amount paid or the suggested price?

For a taxable digital sale, tax is based on the amount the buyer actually pays, not the suggested price. A merchant of record applies the relevant tax rules to that chosen amount.

Can pay as you want work for subscriptions?

Not on Creem. Creem's pay what you want setting works on one-time products only. Some platforms let buyers choose a recurring amount, but on Creem a subscription keeps a fixed price.

How do I choose a credible suggested price?

A credible suggested price rests on something the buyer can check: a price the product really sold at, similar products of the same scope, or a clearly optional supporter amount. Test it against a fixed-price control.

Can I call the offer free if there's a minimum?

No. An offer with a required minimum above zero isn't free, so calling it free misleads the buyer. Show the minimum next to the amount field and describe the offer as pay what you want from that price.

Share this article

Help us spread the word.

Your product is ready.
Make it a business.

Build with AI. Sell with Creem. Set up with a single prompt, sell in 190+ countries and only pay when you earn.