Documentation

In-App Purchasing

Client API

SDK API

In-App Purchasing

Payment provider routing in webshops

Understand how a webshop chooses which payment providers to offer each player, including routing by player tag and the fallback provider.
Read time 1 minuteLast updated a day ago

Webshops can use different payment providers for different players. When a player opens a webshop, the webshop finds the providers the player can use and selects the eligible provider with the highest priority for checkout. You control provider routing with the following settings:
  • Routing rules that map player tags to providers.
  • A fallback provider for players who don’t match any routing rule.
To configure the fallback provider, refer to Set a fallback payment provider.

Provider selection in webshops

When a player opens a webshop, the webshop finds the payment providers the player is eligible to use and orders them by priority. Checkout starts with the highest-priority provider. If no provider is eligible, the webshop uses the fallback behavior you configured. Webshops evaluate routing rules each time a player opens the shop. Routing changes apply in the player’s next session. You don’t need to republish the webshop.

Route by player tag

Each player sees only one payment provider at checkout. When a player matches multiple tags, the webshop combines their provider lists, removes duplicates, and presents the highest-priority provider. A routing rule maps a player tag to an ordered list of payment providers. Tag order sets the primary priority. Provider order within a tag sets the secondary priority. For example, if a player matches both
highSpender
and
likelyToChurn
, the webshop initiates checkout with the provider mapped to whichever tag has higher priority. The player only sees that provider.

Fallback provider

The fallback provider is a single payment provider that the webshop uses when a player doesn’t match any routing rules. If you don't set a fallback provider, the webshop doesn’t offer external payment to players who don’t match a routing rule. A fallback provider ensures all players have a payment option, regardless of routing rules. To configure the fallback provider, refer to Set a fallback payment provider.

No eligible providers available

When a player doesn’t match a routing rule and no fallback provider is configured, the webshop doesn’t offer external payment. The shop still loads, but it doesn’t show an external payment option for that player.