Checkout reliability

A currency switcher changes the display but not the charge

Compare the amount and currency shown during an existing purchase with the saved store order and the matching provider payment. Then identify the installed currency extension, its version and its documented behavior for the checkout and gateway you use. WooCommerce core selects one default store currency; a selector alone does not establish that the currency submitted for payment changes. The comparison can locate where the values diverge, while the extension documentation determines whether that behavior is intended.

For: A research-only merchant whose WooCommerce storefront offers a currency selector but whose payment record may use a different currency.

Updated 2026-10-01

Get help with checkout

Use the same purchase at every step

Choose an existing affected order and match it to the provider payment using the references retained in the authorized systems. Record the amount and currency from each record, with its date. Use the provider’s payment amount for this comparison, not a later payout total. The immediate question is what the store sent for this purchase, rather than the currency in which the business eventually received funds.

For the displayed value, use a genuine observation from that purchase if one exists. Record whether it came from the product page, cart or final checkout summary and whether it was a unit price, subtotal or full total. A current screenshot cannot establish the currency a past buyer saw. If no historical display record exists, mark that stage unobserved; the saved order and payment can still be compared without reconstructing a buyer’s screen from memory.

Compare like amounts. Preserve the selected product option, quantity and the order’s actual discount, shipping and tax lines when explaining the total. A product price and a final payment are different scopes. Do not label the numerical difference a conversion error until you know which amounts you are comparing.

Identify which installed component claims to control currency

WooCommerce’s General settings document allows one default store currency and describes currency display options. Its system status report describes the currency setting as the currency used to display prices and process payments. That report also identifies installed WooCommerce and WordPress versions and active plugins with their versions. These are useful configuration records, but the currency field is not transaction-level evidence of what an additional converter submitted for a particular order.

Record the converter’s exact name and installed version, the payment extension and the checkout type in use. Obtain the converter’s official documentation for that combination, or a specific written vendor answer when the documentation is silent. Look for an explicit statement about displayed values, saved order currency and payment submission. A product name containing currency conversion, or a selector that visibly changes prices, does not establish all three.

Keep the vendor’s conditions with the statement. If the documentation covers a different version, gateway or checkout type, record that scope gap. Do not publish a compatibility conclusion from WooCommerce’s core settings page: it does not describe the behavior of every installed currency extension.

Interpret the boundary where the values diverge

If the observed display changes currency while the order and provider payment retain the store currency, the records locate a display-to-order difference. If the converter documentation explicitly describes presentation-only behavior for the installed setup, that difference can be consistent with its stated scope. It still leaves the merchant to check whether the final checkout clearly tells the buyer which currency will be charged.

If the order carries the selected currency but the provider payment uses a different one, give the integration owner the matched order and payment values. That discrepancy needs investigation at the order-to-payment boundary. The records alone do not identify whether the converter, gateway configuration or another component caused it.

If the order and provider payment agree but the earlier displayed price is unavailable, the correct finding is that the saved records agree and the buyer-facing display remains unverified. If all stages agree for an observed purchase, that establishes agreement for that purchase only. It does not prove compatibility for every currency, method or checkout path.

Choose the correction from the documented behavior

Where the converter is documented as presentation-only, review the buyer-facing currency explanation and final payment summary against the actual charge currency. Where it is documented to affect order or payment submission but the records disagree, ask the responsible integration owner to resolve that specific discrepancy. Where documentation does not cover the installed setup, obtain that missing behavior statement before promising that selecting a currency changes the charge.

Preserve the original order and payment while investigating. Do not edit a historical order merely to make it appear to match a new display setting, or take another payment solely to fill this worksheet. Any customer remedy for an existing discrepancy is a separate authorized decision based on the actual records.

For a Prism checkout consultation, provide the public website, research-only product types, converter and gateway names, and a sanitized description of the stage that differs. Describe the help requested so scope, responsibilities, fees and terms can be agreed before work. Provider eligibility remains separate from software functionality. The public inquiry receives email follow-up and is not an appointment, purchase or processing application.

Display-to-charge currency map

Complete this for one existing purchase using evidence already available. Enter an amount with its currency and the stage it describes; never compare a unit price directly with a full order total. Mark a missing historical display as unobserved. Classify the result as display-to-order difference, order-to-payment difference, agreement for this purchase or insufficient evidence.

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.

Display-to-charge currency map. The last column is for temporary notes.
Stage or dependencyRecord to inspectInterpretation and limitYour values and next action
Displayed amount and currencyDated observation from the actual purchase, naming product page, cart or checkout and the amount’s scope.A present-day page does not establish a past display. Preserve any missing historical evidence as unobserved.
Order currencySaved order’s currency, total and actual component lines in the authorized store record.Compare with the final displayed total when available; do not assume a product-page selector changed the saved order.
Provider amount and currencyMatching provider payment record, status and private reference mapping to the order.Use the payment amount rather than the payout amount. An unmatched payment cannot explain this order.
Conversion extensionExact installed converter and version, default store currency, gateway extension and checkout type.The system status report establishes configuration context, not every extension’s behavior on an individual payment.
Documented behaviorOfficial converter documentation or a written vendor reply naming the installed setup and its conditions.Distinguish display-only behavior from order or payment conversion. Silence about your combination leaves compatibility unresolved.
Difference and responsible ownerThe first stage where comparable amount or currency values disagree, plus the relevant documentation.Send a precise discrepancy to the owner of that stage; leave the cause unconfirmed until investigated.

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.

Limits

  • WooCommerce’s default currency setting does not establish a third-party converter’s behavior or compatibility. This page supplies no plugin-specific behavior claim.
  • No exchange rate, fee, tax liability, refund amount or provider eligibility is inferred from a display-to-payment comparison.
  • Use internal case labels and sanitized values. Keep card details, authentication codes, private payment links, API secrets, full bank details and customer records out of this worksheet and the public form.

Related guides

Sources

  • WooCommerce general settings — checked 2026-09-21. Currency options control price display and allow one default store currency. The core settings document does not establish a third-party converter’s payment behavior.
  • WooCommerce system status report — checked 2026-09-21. The currency field is described as the currency in which prices are displayed and payments processed. The report also identifies WooCommerce and WordPress versions and active plugins with versions; it does not establish an individual extension’s conversion behavior.
  • Prism solutions — checked 2026-09-21. Public support includes storefront review, processing preparation and help with provider website questions. Scope, fees and terms are discussed before work, while the provider decides eligibility and account terms.
  • Prism contact — checked 2026-09-21. The inquiry asks for the website, products and question and excludes card details, passwords and customer records. Email follow-up does not book an appointment, purchase work or submit a processing application.

Get help with checkout

Is this happening on your own store?

Get help with checkoutAll resources