Troubleshooting Checkout Currency in GT Extensions for FluentCart

  • JNext lesson
  • KPrevious lesson
  • FSearch lessons
  • EscClear search

When checkout shows an unexpected currency or amount, check the saved settings, the selected product option and the current cart before changing prices. A remembered customer choice, a fixed-price override or an unavailable conversion can explain the result.

Work through one product and one currency at a time. Keep the checkout out of public page caching, and use a new guest session when you need to separate stored browser choices from the default configuration.

Check the Currency Settings

Open FluentCart → GT Extensions → Currencies and gateways. Confirm that Multi-Currency Checkout is enabled and that your changes have been saved.

  • Accounting base currency comes from FluentCart Store Setup.
  • Default storefront currency is the fallback for an eligible cart.
  • Enabled checkout currencies determine which alternatives can be offered.
  • A customer’s manual selection takes priority over automatic location selection.
  • An issued invoice keeps its agreed currency and prices.

Check Automatic Local Currency

Automatic selection uses billing country first, then shipping country, then Cloudflare location when available. The local currency must be enabled and the cart must be priceable in it. Otherwise checkout falls back to the default storefront currency.

If the currency changes only after adding a particular product, inspect that variation’s price and missing-price behavior. If a customer previously chose a currency manually, automatic detection should not override that choice.

Check Fixed and Converted Prices

In the product editor, open Currency price book and select the relevant product option. Check whether the currency uses a fixed local price or automatic conversion.

  • A fixed price overrides conversion for that variation and currency.
  • Automatic conversion uses the rate, markup and rounding settings.
  • Missing-price behavior can prevent a purchase instead of converting.
  • Use Convert store price and save when you want to remove a fixed override.
  • Currency prices save separately from the main product form.

For example, a USD 10 price at an example INR rate of 80 converts to INR 800 before extra markup or rounding. A saved INR 799 override should still display INR 799. These example amounts are not current exchange rates.

Separate Cart State From Cached Pages

An existing cart and the browser’s remembered currency can outlive a settings change. Compare the result in a fresh guest session, then deliberately select the currency and let checkout reload.

The selector refreshes its currency context through an uncached request. If it disagrees with an item amount or total, check the cart data and price resolution as well as page caching. A mismatch alone does not prove that caching is the only cause.

After changing currency, checkout recalculates the cart and related shipping, tax and fee state. Review the final amounts before payment.

Check Missing Payment Methods

A gateway must be active in FluentCart and permitted for the selected currency. Its payment account must also support the intended transaction.

  • Review the currency-to-gateway choices and preferred gateway.
  • Treat capability hints as guidance rather than account-specific guarantees.
  • Check any gateway error returned when the order is submitted.
  • Use the gateway’s test mode for each currency and payment-method combination you intend to offer.

Confirm the Customer Path

Check the selected product option, currency selector, item amount, subtotal and final total together. Add the product that caused the problem, change quantities and confirm the available payment methods before completing a test payment.

The pricing implementation uses two-decimal amounts. Assess zero-decimal currencies separately instead of assuming they behave identically.

Use the multi-currency setup lesson for configuration and the cache-buster guide for cache boundaries.