Skip to main content

Overview

In order to future-proof your public website and application for price localization, it’s recommended to implement these changes as part of your initial integration with Stigg. Doing so will allow you to introduce and rollout changes to the price localization configuration, without requiring any additional code changes.
Stigg does not automatically determine a customer’s billing currency. You are responsible for implementing the logic that resolves the correct billingCountryCode for each customer and passing it to Stigg’s components and APIs.Common approaches include using the customer’s IP address (GeoIP), their billing address, or a currency preference they select during onboarding. Make sure to apply the same logic on both your public pricing page and in-app experiences - customers who see one currency before subscribing should not be surprised by a different currency afterward.
  1. When no localized pricing is defined for a specified country, the default pricing will be used.
  2. If the customer has already subscribed to a plan with a localized price, its billing country code would override the one that’s provided programatically.

Visibility for localized prices in your public pricing page

Visibility for localized prices in your in your application

In-app paywall

Customer portal

Checkout

Provisioning subscriptions with localized pricing

Additional resources

Integrate Stigg into Your Codebase