Control a routing policy by country, currency, amount, or time

Edit a routing policy and open **Availability Rules**. The policy must also have **Enable Routing Policy** turned on and at least one eligible member.

Schedule & Timing

Choose **Timezone**, an optional start and end date, the days of the week, and both a start and end time when restricting hours. Dates use the selected timezone. A range crossing midnight is supported, such as 22:00 to 06:00. Leaving the day selection empty does not disable the policy; use **Enable Routing Policy** to turn it off.

Geo & Currency Targeting

**Allow Countries** restricts the policy to selected country codes. **Deny Countries** excludes selected countries. If a country appears in both, it is excluded. **Allow Currencies** refers to the order currency, not the gateway's processing currency. Leave an allow list empty when you do not want that restriction. The checkout's resolved country is used for matching, so compare the actual customer context when investigating an unexpected result.

Quotas & Transaction Limits

Set **Min Transaction** and **Max Transaction** for the order amount range. **Daily Amount Limit**, **Monthly Amount Limit**, and **Daily Order Limit** apply to the policy's member usage. Member-level limits still apply separately. Avoid combining gateway accounts with different processing currencies in one amount-cap policy, because recorded usage amounts are not a currency-converted balance.

Keep the rules easy to check

Start with one broad policy per provider pool and add restrictions only when needed. Use non-overlapping country, currency, amount, or schedule rules when different customer groups need different handling. Check the resulting checkout methods after each change.

After saving, check a fresh checkout with the expected order currency, amount, country, and current time. A rule that matches still needs an enabled, policy-approved member below its own limits.