Pay What You Want Pricing: Examples, Costs and a Test Worksheet

Pay what you want (PWYW) pricing lets the buyer choose the payment for a defined product or service. In pure PWYW, that can include zero. Many checkout tools also use the name for a minimum-price version: the buyer can pay more than a stated floor, but cannot pay less.

The decision is whether those payments can support your offer. Use the model comparison, worked example and worksheet below to choose a pricing rule and plan a test. More downloads or more gross revenue can still leave you with less money after delivery costs.

First, choose which pricing model you mean

State the rule where the buyer enters the amount. “Pay any amount, including $0” and “Pay at least $5.00; suggested price $12.00” describe different offers. These are illustrative labels, not recommended prices.

Platform terminology varies. For a concrete current example, Payhip's documentation distinguishes a zero-plus price, which permits a free purchase, from a five-plus price, which requires at least $5.00. Its interface is one implementation, not a universal checkout rule.

When a PWYW test may make sense

A self-serve recording, template or music download may be a better candidate than a custom service requiring hours for each customer. “Digital” does not mean cost-free: payment fees, support, delivery, licensing and refunds can still matter.

• You can tolerate the downside. If zero payments are allowed, decide how many free fulfillments you can support and the maximum test cost you will accept.

• The offer is clear. Buyers need to know exactly what they receive, whether the amount changes access, and whether the payment is one-time or recurring.

• You have a specific goal. Testing accessibility, contribution or demand leads to different decisions. An audience-building goal needs a budget; it does not make free customers automatically profitable later.

• You can measure the result. Separate free orders, paid orders, payment amounts and costs. A large download count alone cannot settle the pricing decision.

PWYW is not an automatic traffic, loyalty or profit improvement. The original three-field-study paper found that people paid more than zero and that seller revenue could increase in its settings; it also identifies payments below seller costs as a risk. A 2025 laboratory study examined market structure with Chinese undergraduate participants. Such findings help frame a test; they do not predict what your customers will pay.

A worked example: more revenue, less contribution

Illustrative scenario, not a Hyax customer result or a forecast. A creator is comparing pricing for the same downloadable workbook. Each option receives 1,000 eligible product-page visits. These invented inputs make the arithmetic reproducible:

• Fulfillment and support cost: $1.50 per completed order, including free orders.

• Payment fee: 3.00% plus $0.30 per paid order; no payment fee on a zero-payment order in this model. These are assumed fees, not any provider's quoted rates.

• Fixed test cost: $120.00 for each alternative.

• Taxes collected for others, refunds, acquisition spending, initial product development and other business overhead are excluded. Add your actual costs before making a commercial decision.

The PWYW alternative brings in more product payments and serves more people. It contributes less toward the business because free orders still require fulfillment and support. Since both alternatives received the same 1,000 visits, this is also a direct comparison of contribution from the same amount of traffic. It is not proof that a fixed price will win in a real test.

There is another reporting trap: the PWYW average payment among paying buyers is $6.00, while the average across all completed orders is $3.00. Excluding the free orders conceals part of the cost exposure.

To reproduce the calculation: contribution equals product payments minus payment fees minus fulfillment/support costs. For PWYW here: $240.00 − $19.20 − $120.00 = $100.80. Subtracting the separate $120.00 test cost gives −$19.20. This is a limited contribution model, not net business profit.

Calculate a minimum-payment version separately

A mandatory floor changes the offer: the free orders in the previous example would no longer be possible. Do not assume the same number of people will still buy.

If every completed order is paid, a simplified break-even payment for the chosen test window is:

(Cost per order + fixed payment fee + fixed test cost ÷ paid orders) ÷ (1 − percentage payment fee)

Using the illustrative costs above and assuming 80 paid orders, the calculation is ($1.50 + $0.30 + $120.00 ÷ 80) ÷ (1 − 3.00%). A practical cent-level floor is $3.41: move up to the next cent when necessary, because ordinary rounding to $3.40 would fall below this model's mathematical break-even point.

If only 25 paid orders materialize, the corresponding modeled floor becomes $6.81. Order volume is an assumption, not a promise. A higher minimum may change that volume again.

Use your actual platform and processing fees, including any minimum charges. Real per-payment fee rounding can change the totals. Refunds, taxes, discounts, currencies and different delivery costs can require a more detailed model. A suggested price is neither the minimum nor evidence that buyers will choose it.

Copy the test worksheet

Complete this before publishing the offer. Keep the same definitions when comparing results.

OFFER
Product and exact access:
Pure PWYW or minimum floor:
Zero payment allowed? Yes/No
Minimum / suggested amount:
One-time or recurring:

COST ASSUMPTIONS
Cost per free order:
Cost per paid order:
Percentage / fixed fees:
Fixed test cost:
Other costs included:
Costs still unknown:

TEST PLAN
Eligible traffic source:
Fixed-price comparison:
Start / end / review date:
Maximum loss or spend:
Support capacity limit:
Who pauses the offer:

RESULTS
Eligible visits:
Paid / free orders:
Payments / refunds:
Actual payment fees:
Fulfillment / support cost:
Contribution before fixed:
Result after test costs:
Decision and its evidence:

A genuine accessibility project may accept a lower financial contribution. If so, say what access you intend to fund, set that budget in advance and report the outcome against it. Do not quietly switch from a profit goal to a download goal after seeing disappointing payments.

Run a bounded test, then make a decision

1. Define one offer and one comparison. Keep the delivered content and traffic eligibility comparable. Changing the product, promotion and price together makes the result difficult to interpret.

2. Check the actual checkout. Test a permitted low amount, the suggested amount, a larger amount and an amount below the floor. If zero is allowed, verify its access path separately. Use the platform's supported test mode, then verify receipt and delivery behavior.

3. Publish clear terms. Explain the minimum, what different amounts buy, access limits and refund policy. Do not call a purchase a charitable donation merely because the buyer chooses the amount.

4. Respect the stop conditions. Review the planned cost and support limits during the test. Pause if they are breached; do not keep expanding the offer to chase a download count.

5. Compare like with like. A randomized split, when available, gives a cleaner comparison than different weeks. Otherwise use equal complete windows, keep the traffic filters consistent and record promotions or seasonal differences. Treat the result as directional when those conditions differ.

Continue only if the measured result serves the goal and its costs remain acceptable. Change one important assumption or pricing rule at a time. If the economics fail, a fixed price, narrower offer or separately budgeted free sample may fit better.

For selling content through Hyax, explore its monetization options. Confirm your chosen checkout's exact pricing mode, minimum and delivery behavior before planning a PWYW launch; support for digital products alone does not establish support for buyer-chosen payments.

Updated October 30, 2026. The calculations are illustrative operating examples, not measured customer results. Source and product documentation were checked for this update.