Is the currency of my country supported?

Almost certainly yes — Tickera ships with the complete list of world currencies built in, so the question isn’t whether Tickera supports your currency (it does), but whether the payment gateway you connect supports your currency for charges in your country. Tickera and the gateway have to agree, and the gateway is the limiting factor.

The two-side rule

Selling a ticket involves two pieces:

1. Tickera’s currency setting — what currency the ticket is priced in, what currency the buyer sees, what currency the order is recorded in. You set this in your dashboard.
2. The payment gateway’s currency support — what currencies the gateway can actually charge cards in for your account, in your country.

These two must match. If you price tickets in BRL (Brazilian Real) but your payment gateway only accepts USD for your account, the transaction will either fail or behave unpredictably. Set both sides correctly and it Just Works.

Setting Tickera’s currency

Inside your WordPress dashboard, go to Tickera → Settings → General → Store Settings. The currency dropdown contains every ISO 4217 currency code — USD, EUR, GBP, AUD, BRL, INR, JPY, MXN, ZAR, NGN, the lot. Pick yours, save, done. The currency symbol updates everywhere — ticket prices, cart totals, order receipts, attendee emails.

Checking your payment gateway’s currency support

This is the part that depends on the processor and your country. Common patterns:

• Stripe supports 135+ currencies for charges, but which ones your Stripe account can accept depends on the country your Stripe account is registered in. Check the official list at stripe.com/docs/currencies.
• PayPal supports around 25 currencies for transactions, with regional restrictions. See PayPal’s currency codes reference.
• Authorize.Net, Braintree, Square, Mollie, Razorpay — each has its own list, country by country. Their docs sites are the canonical source.

Best practice before launching: open a chat or email with the payment gateway, confirm your account can accept charges in the currency you want to sell in, then configure Tickera to match.

What if your gateway doesn’t support your local currency?

A few options:

• Sell in a supported currency instead (e.g. USD or EUR) and let buyers’ banks convert. Common for international audiences, less convenient for local-only events.
• Use a different gateway — many countries have local processors that handle local currencies better than Stripe/PayPal do. See our full list of supported payment gateways for region-specific options.
• Combine multiple gateways — Tickera lets you enable several at once, so buyers can pick the one that fits their card.

Using Tickera with WooCommerce

If you’re running Tickera alongside WooCommerce via the Bridge for WooCommerce add-on, the currency setting moves to WooCommerce. Tickera automatically follows whatever WooCommerce is configured to use.

In that scenario:

• Set the currency in WooCommerce → Settings → General → Currency options, not in Tickera.
• Make sure the payment gateways you’ve enabled in WooCommerce support that currency in your country.
• Tickera’s own currency dropdown becomes irrelevant — Bridge tells Tickera “WooCommerce is in charge of currency now.”

The two-side rule still applies — WooCommerce’s currency must match what the connected gateway can charge.

Multi-currency: showing different prices to different visitors

If you need to display prices in multiple currencies for different audiences (USD for US visitors, EUR for European visitors, etc.), the cleanest path is the WooCommerce + Bridge route, paired with a multi-currency plugin for WooCommerce (e.g. Currency Switcher for WooCommerce, WPML’s multi-currency module, or similar). Tickera itself stores prices in a single currency per event; the multi-currency layer happens at the storefront level via WooCommerce.

Related questions

• Is Tickera’s own pricing in USD?
• Does Tickera require WooCommerce?
• Does Tickera take a percentage of sales?