Copyright © 2026 Unity Technologies
It should not be possible to create routing rules with the same priority, same audience, and same target for different payment providers. The Dashboard currently permits this.
Two rules saved with identical priority, target country and webshop setting but different providers both go live. The routing rule documentation recommends distinct priorities so developers "don't need to rely on tie-breaking behavior", but that tie-breaking behavior is not specified anywhere, so which provider a matching player is offered is unpredictable from the developer's side.
The second rule is rejected, with an error identifying the rule it conflicts with.
The second rule saves. Rules activate immediately on save, so the ambiguous configuration goes live with no warning.
Applies to the Unity Dashboard payment provider routing configuration, not the SDK. D2C payment provider routing was introduced in IAP 5.4.0. Routing rules are evaluated server-side at runtime, so no client update is involved.
Issues you vote on will appear here