In this guide
The same plan is shown in different currencies and formats around the world. A wrong or confusing price is a trust problem, and in some places possibly a legal one (no legal advice here). This guide shows how to check what users actually see. Part of Testing monetization.
The rule: show the store's price, not your own
Prices come from the store for each storefront. Hard-coded strings like "$4.99/month" in your layout will be wrong somewhere. Read the localized price string the store provides and display it as given. Choosing the prices themselves is a separate topic, see Subscription pricing and trials.
Whether prices shown include tax differs by region and store. Check the current store documentation and, where it matters, a professional. This page does not say what is required where.
What to test
- Currency symbol and position. Before or after the number, with the right separators.
- Period wording. "per month", "per year", "per week" are consistent between the headline, the button and the fine print.
- Trial text uses the real price. "Then X per year" shows the localized X.
- Long strings. Some currencies and languages are longer. Check wrapping and truncation on small phones.
- Per-month equivalents. If you show "just X per month" for a yearly plan, the math is yours, so check it in each currency and mark it as an approximation if rounded.
- Discount badges. Any "save X%" is computed from the localized prices and still true there.
- Right-to-left languages. Prices and symbols do not flip or jumble.
- Missing price. If the store returns nothing, the screen shows a neutral state, not an empty or zero price. Never show "0" for a paid plan.
- Changing storefront. Switch the test account's region and relaunch; prices update.
How to test without travelling
- Use test accounts in several storefronts, where the stores allow it. Check how to set that up on the current official store pages.
- Screenshot every region and compare in one grid.
- Ask people who really live there to read the paywall and say what they think they pay. That catches wording a screenshot cannot.
Record
A small table: region, currency, string shown, correct yes/no, notes. Review it before each pricing change.
Related: paywall comprehension test, dark patterns audit.
AppReviewX testers can read your paywall and tell you what they believe it costs. Start free.