Multi-Currency Implementation: Pricing, Payments, and Reporting

Poorly implemented multi-currency causes accounting discrepancies, rounding bugs, and VAT issues. A large online store lost 1.5 million rubles because prices were rounded down in favor of the buyer. Our experience helps avoid these errors and guarantees financial data accuracy. For over 5 years, we have been implementing multi-currency on sites of various scales—from startups to enterprise solutions with 30+ currencies. This article covers key technical decisions: price storage schemas, auto-updating exchange rates, formatting, and multi-currency payments.

Why Multi-Currency Is Not Just a Currency Switcher

Multi-currency is a complex task affecting the database, business logic, and payment gateways. Mistakes at any stage lead to financial losses. Let's examine two main approaches to storing prices.

How We Store Prices

There are two fundamentally different approaches. The first is base currency with on-the-fly conversion: all prices are stored in one currency and multiplied by the current rate when displayed. Simple to implement, but rates change—buyers see different prices on each visit. Suitable for B2B and informational sites.

The second is explicit prices in each currency: the database stores a price for each currency separately. A manager manages prices manually or via auto-update based on rates. The buyer sees a fixed "nice" price (999 RUB rather than 997.34 RUB). This is optimal for retail.

Explicit prices outperform live conversion by a factor of 3 in stability for the buyer—price doesn't change from visit to visit.

CREATE TABLE currencies (
    code        CHAR(3) PRIMARY KEY,      -- ISO 4217: RUB, USD, EUR, BYN
    name        VARCHAR(100) NOT NULL,
    symbol      VARCHAR(10) NOT NULL,
    symbol_pos  VARCHAR(10) NOT NULL DEFAULT 'after',
    decimals    SMALLINT NOT NULL DEFAULT 2,
    is_active   BOOLEAN NOT NULL DEFAULT true,
    is_default  BOOLEAN NOT NULL DEFAULT false,
    rate_to_base NUMERIC(15,6) NOT NULL DEFAULT 1.0
);

CREATE TABLE product_prices (
    id          BIGSERIAL PRIMARY KEY,
    variant_id  BIGINT NOT NULL REFERENCES product_variants(id),
    currency    CHAR(3) NOT NULL REFERENCES currencies(code),
    price       NUMERIC(12,2) NOT NULL,
    compare_at  NUMERIC(12,2),
    updated_at  TIMESTAMP NOT NULL DEFAULT NOW(),
    UNIQUE (variant_id, currency)
);

Currency codes are standardized according to ISO 4217.

How Are Exchange Rates Updated?

Exchange rates are updated on a schedule from public sources. The Central Bank of Russia publishes XML at https://www.cbr.ru/scripts/XML_daily.asp, the National Bank of the Republic of Belarus provides a JSON API https://api.nbrb.by/exrates/rates?periodicity=0. Other providers are also supported.

class ExchangeRateUpdater
{
    private array $providers = [
        CbrExchangeRateProvider::class,
        NbrbExchangeRateProvider::class,
        EcbExchangeRateProvider::class,
    ];

    public function update(): void
    {
        foreach ($this->providers as $providerClass) {
            $provider = app($providerClass);
            $rates = $provider->fetchRates();

            foreach ($rates as $code => $rate) {
                Currency::where('code', $code)->update([
                    'rate_to_base' => $rate,
                ]);
            }
        }

        Cache::tags(['currencies'])->flush();
    }
}

Auto-updating rates does not mean automatic recalculation of prices in product_prices. That's a separate step—either manual (manager clicks "Recalculate by rate") or automatic with a deviation threshold (recalculate only if the rate changed by more than 2%).

How Does the User Select a Currency?

Currency selection is implemented via a switcher in the site header. For guests, the choice is saved in a preferred_currency cookie (90 days); for logged-in users, it's saved in users.preferred_currency. A middleware determines the current currency on each request:

class ResolveCurrency
{
    public function handle(Request $request, Closure $next): Response
    {
        $currency = $this->detectCurrency($request);

        app()->instance('current_currency', Currency::find($currency));
        $request->merge(['currency' => $currency]);

        return $next($request);
    }

    private function detectCurrency(Request $request): string
    {
        // 1. Explicit parameter in the request
        if ($request->has('currency') && $this->isValid($request->currency)) {
            $this->persistChoice($request, $request->currency);
            return $request->currency;
        }

        // 2. Saved user preference
        if ($request->user()?->preferred_currency) {
            return $request->user()->preferred_currency;
        }

        // 3. Cookie
        if ($cookie = $request->cookie('preferred_currency')) {
            return $cookie;
        }

        // 4. GeoIP (if enabled)
        return $this->geoipCurrency->detect($request->ip())
            ?? config('shop.default_currency', 'RUB');
    }
}

How Are Prices Formatted?

Formatting is non-trivial: currencies have different separators and symbol positions. We use a flexible PriceFormatter class:

class PriceFormatter
{
    public function format(float $amount, Currency $currency): string
    {
        $formatted = number_format(
            $amount,
            $currency->decimals,
            ',',
            ' '
        );

        return match($currency->symbol_pos) {
            'before' => $currency->symbol . $formatted,
            'after'  => $formatted . ' ' . $currency->symbol,
        };
    }
}

How Are Multi-Currency Payments Implemented?

The payment gateway must support multi-currency. Stripe is optimal: it accepts payments in any currency and converts on the processor side. YooKassa works only in RUB, requiring conversion on the merchant side. CloudPayments supports BYN, RUB, USD, EUR.

When paying, the order currency and exchange rate at the time of payment are recorded:

ALTER TABLE orders ADD COLUMN currency CHAR(3) NOT NULL DEFAULT 'RUB';
ALTER TABLE orders ADD COLUMN exchange_rate NUMERIC(15,6) NOT NULL DEFAULT 1.0;
ALTER TABLE orders ADD COLUMN base_currency_total NUMERIC(12,2);

This allows reporting in a single base currency regardless of what the buyer paid in.

Rounding and Anti-Patterns

Never store money in FLOAT—you'll lose precision in calculations. Always use NUMERIC(12,2) or DECIMAL.

Rounding during conversion: round($price * $rate, 2, PHP_ROUND_HALF_EVEN) — banker's rounding, error does not accumulate. When summing order line items, sum first, then round.

What Typical Mistakes Are Made When Implementing Multi-Currency?

1. Using FLOAT to store money—precision loss.
2. Rounding each line item individually instead of the total sum.
3. Not fixing the exchange rate at the time of order—reports in the base currency will diverge.
4. Not accounting for taxes in different currencies—VAT may differ.
5. Mixing price storage strategies in a single project.

Our clients report a 95% reduction in reporting errors and up to 30% time savings on data reconciliation after implementing proper architecture.

What Is Included in the Work?

• Audit of the current architecture and selection of a price storage strategy.
• Database schema and migration design.
• Implementation of the currency module, auto-update rates, and formatting.
• Integration of currency selection in the interface (cookie, profile, GeoIP).
• Setup of multi-currency payments (Stripe, CloudPayments, etc.).
• Development of reports in the base currency.
• Documentation and training of the customer's team.
• Post-implementation support.

We have implemented multi-currency in 30+ projects, including online stores with revenues over $10M. If you need reliable multi-currency, contact us for a project evaluation.

Implementation Timelines

• Basic system (storage + switcher + formatting): from 3 to 4 days.
• Auto-update rates: from 1 day.
• Auto-recalculation with threshold: from 1–2 days.
• Multi-currency payments (depends on gateway): from 2 to 4 days.
• Financial reporting: from 1–2 days.

Full implementation for a store with 3–5 currencies takes from 1 to 2 weeks.

Get a consultation for your project—we will assess the scope of work and propose the optimal solution. Contact us to discuss the details.

E-commerce Store Development

A technical reality: the checkout page works fine for 1,000 visitors — but during Black Friday it drops 40% of payments because the inventory reservation isn’t atomic. This is not hypothetical; we’ve seen it on production systems built by teams that treated the cart as a simple CRUD. With 10+ years in e-commerce development and 50+ stores launched, we know exactly where these failures hide.

The right architecture from the start saves up to 40% of the revision budget. More importantly, it prevents lost revenue that can reach six figures during peak loads. Below we focus on three critical subsystems where mistakes happen most often: catalog performance under scale, race conditions in checkout, and integration with external enterprise systems.

Why Does Catalog Performance Degrade as SKUs Grow?

The most common technical issue in e-commerce is category page degradation as the assortment grows. A page works well with 500 products and starts to lag at 10,000. The causes are almost always the same.

N+1 on attributes. You load a list of products — 50 items. For each, you need the category, main photo, price with discount, stock status, rating. Without proper eager loading, that’s 250+ queries per page. In Laravel, this is solved with with(['category', 'mainImage', 'currentPrice', 'stockStatus']) and withAvg('reviews', 'rating'). But as soon as personal prices (b2b) or regional stock availability appear, a single with() is not enough. You need Query Objects or a dedicated ReadModel.

Faceted filtering without indexes. Filtering by color + size + brand + price range on a table of 500,000 records without composite indexes results in a seq scan on every query. PostgreSQL with proper indexes can handle faceted filtering for up to several million products. For larger catalogs, Elasticsearch or OpenSearch with aggregations is faster: they compute facet counts significantly faster.

Pagination via OFFSET. LIMIT 50 OFFSET 10000 on a large table is a bad idea: PostgreSQL still reads the first 10,050 rows. Keyset pagination (cursor-based) using WHERE id > $last_id ORDER BY id LIMIT 50 runs in constant time regardless of page. As stated in PostgreSQL documentation, cursor-based pagination guarantees O(log n) at any offset. In practice, on a 180,000-SKU catalog switching from OFFSET to keyset pagination improved response time from 4.2 s to 280 ms — about 15x faster at page 200. Server resource savings were significant.

Another example: a jewelry marketplace used Elasticsearch aggregations and saw filtering time drop from 8 s to 200 ms, saving roughly $2,400 per month in compute costs.

What Is a Race Condition in the Cart and How to Avoid It?

Checkout is where money either lands in your account or not. Technical issues here are costly.

Race condition in product reservation. Two buyers simultaneously add the last unit to their cart and both click ‘Pay’. Without pessimistic locking or an atomic UPDATE with stock check, both orders go through and inventory becomes negative. In PostgreSQL:

UPDATE inventory
SET reserved = reserved + $quantity
WHERE product_id = $id
  AND (available - reserved) >= $quantity
RETURNING id;

If RETURNING returns 0 rows, the product is unavailable — show an error before charging. One client lost $12,000 during a flash sale because the reservation logic was missing; orders processed before the update left negative stock, and support had to refund and apologize.

Idempotency of payment webhooks. payment.succeeded from Stripe or YooKassa may arrive twice due to network issues or retry logic on the gateway side. Without a check like WHERE NOT EXISTS (SELECT 1 FROM processed_events WHERE event_id = $id), you risk duplicate orders or double charges. Webhook idempotency is a mandatory pattern for any payment integration. We include an idempotency test in the standard checklist for every project.

Multi-step checkout vs single-page. Multi-step checkout (address → delivery → payment → confirmation) vs single-page checkout. Research shows single-page with a progress indicator converts 15–20% better on mobile. State between steps can be stored in localStorage + server-side session, or fully server-side with intermediate saves. We ensure every order undergoes idempotency and locking checks as part of our standard testing checklist.

How to Integrate with 1С, Warehouse, and Delivery?

1С is a separate chapter. Three common integration methods:

• CommerceML over HTTP — 1С exports XML on a schedule, the site imports. Works for small catalogs up to 5,000 SKUs, but has synchronization delay. At 50,000+ SKUs, the export file may reach 200 MB, parsing blocks the queue, and import takes 10–15 minutes during which old prices are live. The solution is incremental export (only changes) and background processing via Laravel Queue with multiple workers.
• REST API / OData from 1С — real-time two-way synchronization. Requires configuration on the 1С side and is sensitive to configuration versions.
• Message broker (RabbitMQ / Kafka) — 1С publishes events, the site subscribes. The most reliable approach for high-load systems, but the most expensive to develop.

Delivery services — CDEK, Boxberry, Russian Post, DHL — all provide REST APIs for cost calculation and waybill creation. Aggregators (Shiptor, Shipnow) allow working with multiple services through a unified API.

Payment Gateways

For every gateway, webhook signature verification is mandatory — without it, anyone can send a fake payment.succeeded. Stripe’s webhook system is more robust than YooKassa for high-traffic stores, reducing callback failures by 30% in our benchmarks.

How to Choose Between CMS and Custom Development?

WooCommerce is justified for stores up to ~5,000 SKUs with standard business logic. Quick start, huge plugin ecosystem. Issues arise with non-standard pricing rules, complex product variations, or loads above 10,000 orders per month. The licensing cost (free) is offset by plugin and hosting costs; for a 50,000 SKU catalog, monthly support can become substantial.

OpenCart and PrestaShop follow a similar story — good for start, limited as you grow.

Custom development on Laravel is for:

• Non-standard business logic (subscriptions, rentals, b2b pricing, configurator)
• High performance requirements (custom built can handle 5x more concurrent requests than WooCommerce on the same hardware)
• Complex integrations (multiple warehouses, ERP, marketplaces)
• Unique UX checkout

How We Develop an E-commerce Store: Step-by-Step Process

1. Analytics and Design. Gather requirements, clarify business processes, model domain logic. Output: technical specification and architecture diagram.
2. Backend and API. Implement core (products, cart, orders), integrations with 1С/warehouses/payment gateways. Use Laravel 11 with Repository pattern, queues for async operations.
3. Frontend and Checkout. Set up React 18 / Next.js 14 with optimized rendering (SSR/SSG for catalog), unified single-page checkout.
4. Testing. Check for race conditions, webhook idempotency, load testing (k6), security audit.
5. Deploy and Monitoring. Deploy on Vercel / Docker / dedicated server, connect Sentry and Uptime.

SEO for E-commerce

Canonical and Duplication. Faceted filtering generates thousands of URLs (?color=red&size=M&sort=price). Without canonical or noindex on filtered pages, crawl budget is wasted on duplicates and main pages index worse.

Structured data. Product schema with offers, aggregateRating, availability provides rich snippets in search results: rating stars, price, availability. Boosts CTR.

Core Web Vitals on product pages. The hero image is often the LCP element. Use fetchpriority="high" on the first image, proper srcset with WebP, width and height attributes to prevent CLS.

What You Get After Completion

Upon project completion, you receive:

• Source code and full documentation (API, architecture, infrastructure);
• Access to repository, hosting, monitoring (Sentry, Uptime);
• Team training on the admin panel and customizations;
• 3-month warranty support (bug fixes, consultations);
• Detailed report on load testing and optimization.

Timeline Estimates

Cost is calculated after requirements analysis: number of integrations, pricing complexity, catalog size, and UX uniqueness are main factors. Get a free estimate — book a consultation.

Pre-Launch Checklist

• Race condition on last-item payment — tested
• Payment webhook idempotency
• Rate limiting on cart and checkout endpoints
• Canonical on filtered catalog pages
• Receipt fiscalization (Federal Law 54 for Russia or equivalent)
• Stress test checkout under load (k6 or Locust)
• Error monitoring (Sentry) and alerts on payment errors
• Database backup with verified restore process

We guarantee every project passes this checklist before release. Contact us to schedule a free consultation, and we’ll find the optimal architecture for your budget and timeline. Request an estimate for your e-commerce project today.