How to build multi-currency ecommerce in Bubble

To build multi‑currency ecommerce in Bubble, store all product prices in one base currency (like USD), fetch live exchange rates from a real API, save those rates, and convert prices on the fly for the user’s selected currency. For checkout (Stripe, PayPal, etc.), always send the amount in the currency that the gateway requires, converting right before payment so the user is charged correctly.

Core Structure

The stable pattern is: store once in base currency → convert for display → convert again for payment. Bubble does not do currency conversion automatically, so you need one external rates API (ExchangeRate‑API, Fixer, etc.) via the API Connector, and a tiny “Rates” data type to cache the latest conversion values.

• Create a data type CurrencyRate with fields: code (text), rate (number) relative to USD.
• Use a backend workflow to call a real exchange‑rates API and update those records daily or hourly.
• Let the user pick a currency (store in Current User’s currency field).
• For display: Product price \* CurrencyRate.rate.
• For checkout: convert again and send the converted amount to Stripe.

API Connector Example

This is a real request format most exchange‑rate APIs use. Replace the URL with your provider’s.

{
  "url": "https://api.exchangerate-api.com/v4/latest/USD",
  "method": "GET"
}

Backend Workflow Logic

In your scheduled workflow, loop through the API response and update each CurrencyRate entry. Bubble’s backend workflows let you run this daily so your app is always up to date.

Checkout Flow

Stripe requires amounts in the smallest currency unit (like cents). So if your user is paying in EUR, calculate: (Product price in USD _ EUR rate) _ 100 and send that number to Stripe’s “amount” field in the API Connector or the Stripe plugin.

• ALWAYS do a fresh conversion right before paying.
• Do not store converted prices in the database; always calculate from the base price.

Privacy & Accuracy

Use Privacy Rules on CurrencyRate so only backend workflows can write, and users can only read. This prevents accidental edits and keeps your rates trusted.