Who should control payment routing policy?

Routing policy expresses business intent. The platform should make that policy executable and visible, but the merchant should remain in control of the decision.

Policy begins with merchant constraints

Entity, geography, licence, method, currency, amount, traffic type and provider availability determine which routes are eligible. These are not abstract technical filters. They reflect commercial agreements, risk decisions and the customer experience the merchant is prepared to support.

Separate hard rules from preferences

A hard rule excludes a route that cannot be used. A preference orders the eligible routes—for example by merchant priority or a defined operational objective. Keeping the two layers separate makes it possible to explain whether a provider was unavailable, ineligible or simply lower in the approved order.

The platform executes a versioned decision

PayStar applies the active rule set to the payment context and records the result. The record should identify the policy version, matched conditions, chosen pipeline and any fallback attempt. That makes execution auditable without implying that the platform invented the commercial policy.

Changes need an accountable approver

Every material policy change should have a reason, owner, scope and review point. Compare the same traffic segments before and after the change. If the intended outcome does not appear—or another segment degrades—the merchant can revert or refine the policy using evidence.

Review policy when context changes

A route that was appropriate last quarter may no longer fit after a PSP changes limits, a merchant adds a new entity or customer traffic shifts to another market. Schedule reviews around real changes rather than editing rules by habit. Reconfirm commercial readiness, technical health and operational support before increasing traffic. The review should end with a documented decision to retain, revise or retire the rule, including the evidence used and the person accountable for the next review.

The merchant owns the routing intent. The orchestration layer turns it into consistent, explainable execution.