Check what your store tells visitors about currency and pricing

Follow the public currency statement to the charge

Collect the currency wording beside product prices, in the cart, at the final payment step, in price FAQs, and in any currency selector. Include inherited theme text and translated versions. A currency symbol alone can be ambiguous; use a clear currency identifier where visitors need to distinguish which currency the amount means. Record whether the page presents a converted display as an estimate or as the amount that will actually be charged.

WooCommerce’s general settings select one default store currency and control currency display options. That setting is a starting point for the review. It does not explain every theme label or extension that may change displayed prices. If a currency plugin is installed, record its name and the actual behavior at each step rather than attributing the additional behavior to WooCommerce core.

Use an existing real order and its matching provider payment to compare the currency and total that reached the payment system with the representation made at checkout. Preserve the distinction between the current page and any historical wording retained with that order. Today’s storefront cannot prove what a buyer saw before an earlier edit. No new transaction is needed simply to fill this comparison.

Separate the buyer’s charge from the merchant’s settlement

Stripe distinguishes the currency of the customer’s payment method, the presentment currency of the charge, and the settlement currency the business receives. These are different parts of the transaction. A price statement needs to identify the buyer’s charge clearly; it does not need to present the merchant’s settlement currency as though the buyer paid in it.

When a charge and settlement use different currencies, a conversion can explain why the business receives a different figure. That belongs in the internal reconciliation. It does not justify changing the public charge label to the bank account’s currency. Conversely, if the store displays one currency but actually submits a different charge currency, the buyer-facing journey needs an explanation and potentially a configuration correction before the label can be treated as accurate.

The buyer’s issuer may apply conversion or other charges under its own terms. Stripe’s currency documentation notes potential issuer foreign-exchange charges when currencies differ and possible charges when the payment method and business are in different countries. Do not promise that matching a displayed currency to a visitor’s location prevents every issuer charge. The store does not establish the buyer’s account currency or issuer terms from location alone.

For another provider, use its actual definitions and the merchant’s charge record. Neither Stripe’s currency support nor a working currency selector establishes that a provider has approved this research-only business or the markets it serves.

Compare tax and duty wording with what the checkout actually collects

Copy each existing claim about tax inclusion, taxes added later, duties, and charges payable on delivery. Compare it with the visible item price and separate lines in the real checkout and order. The immediate representation question is whether the promised inclusion or exclusion matches the amounts the store collects. Do not treat a tax label as evidence of the correct legal amount.

WooCommerce documents the store address as the seller location used for tax and shipping calculations. A configured address is an input to software; it is not a conclusion about tax registration, liability, or the customs treatment of an order. If the address or calculation context does not describe the real operation, assign that configuration discrepancy to its authorized owner.

For a duty-paid or all-charges-included statement, ask the operations owner for the existing shipping arrangement and records that substantiate what the business actually undertakes to pay. An absent duty line in checkout is not proof that no duty can arise. If the business cannot substantiate a public assurance, mark the wording unresolved for the content owner and a qualified tax or customs adviser as needed. Do not replace uncertainty with a universal claim that the buyer always owes the charge either.

Keep the scope of the finding narrow: the page says one thing, the charge or collection arrangement establishes another, or the supporting record is missing. This review does not calculate a duty, choose a tax rate, or decide which party is legally liable.

Correct the statement at the point where buyers rely on it

If the label is ambiguous but the displayed and charged currencies agree, clarify the currency beside the amount and in the relevant price statement. If an inherited “prices in” sentence names a different currency from the live charge, correct the sentence wherever that version appears. If a selector changes only an indicative display, make the actual payment currency clear before the buyer commits; do not describe a display conversion as a confirmed charge.

When the text accurately describes the business’s intended pricing but the payment uses a different currency, assign the mismatch to the integration owner as well as the content owner. Changing copy alone may leave the intended offer unimplemented. When a tax or duty claim lacks support, obtain the relevant operational or professional decision before publishing replacement assurances. Record which page, setting, and statement changed, then check the affected buyer-facing step.

For a Prism website-review consultation, bring the public URLs, the contradictory wording, and a non-sensitive description of the currency or inclusion difference. Prism’s published scope includes marketing claims and store policies. Agree the pages and questions, reporting, any implementation responsibilities, fees, and terms before work. Keep full orders, bank details, and customer records outside the public inquiry.

Currency display statement check

Complete the final column from current public pages, actual settings, and existing charge records. Mark each statement supported, contradicted, or unverified and name its correction owner. Keep merchant settlement information as internal context; do not turn it into the buyer’s charge currency.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.