Create a payment routing policy

A routing policy groups saved connections of the **same provider type** and selects an eligible member for checkout. For example, a pool can contain several Stripe connections. It cannot mix a Stripe connection and a PayPal connection.

Create a policy

1. Add the provider connections under **Payment Gateway** first.

2. Open **Routing Policies** and choose **Add Policy**.

3. Turn on **Enable Routing Policy**.

4. Enter an **Internal Group Name** for your team and a **Checkout Display Name (Mask)** for the customer.

5. Choose a **Selection Strategy** and add at least one member.

6. Drag selected members into the intended order when using **Priority**.

7. Review **Availability Rules**, save, and check a fresh checkout.

Selection strategies

- **Priority** prefers the first eligible member in the saved member order. A disabled, blocked, or capped member is skipped. This chooses an eligible connection before payment; a declined payment is not automatically retried on another account.

- **Round robin** rotates selection using recorded paid-order counts for the eligible members. It does not guarantee an exact split of checkout visits or concurrent orders.

- **Weighted** chooses an eligible member probabilistically. Use **Priority** when you need a particular account to be preferred instead of relying on a percentage split.

Check policy membership

Once a gateway belongs to a routing policy, it is no longer a standalone option. Turning the policy off can therefore hide all of its members unless another applicable policy uses them. If you need a gateway to return to standalone checkout, remove it from every policy that contains it.

Use a clear checkout name such as “Pay by card.” The mask changes the displayed method name; it does not change which provider account receives the payment. Review affected member lists after deleting a gateway.