Orchestration Rules

Orchestration rules in Tuxopay empower you to precisely control how payments are routed, limited, and managed across multiple providers and shops. With a rich set of rule types, you can optimize for compliance, cost, reliability, and custom business logic.

---

What Are Orchestration Rules?

Orchestration rules are logic-based configurations that let you:

• Limit the total amount or number of transactions processed in a given period
• Allow or block payments from specific countries
• Restrict payments to business hours
• Distribute payments across shops using weighted load balancing
• Warm up new payment gateways with controlled limits and schedules
• Route payments and define fallback strategies based on transaction attributes

Example Use Cases

• Maximum Amount Per Period: Limit the total processed amount for a shop to $10,000 per day.
• Country Filter: Block payments from restricted countries or only allow payments from specific regions.
• Business Hours: Only allow payments between 9:00 AM and 6:00 PM local time.
• Maximum Transactions Per Period: Limit a shop to 1000 transactions per hour.
• Weighted Load Balancing: Distribute 70% of payments to Shop A and 30% to Shop B.
• Payment Gateway Warming Rule: Gradually introduce a new gateway by allowing only 50 transactions per hour during the first week.

---

Defining a Rule

A typical orchestration rule includes:

• Condition: When the rule should apply (e.g., country is not allowed, amount exceeds limit, outside business hours)
• Action: What to do (e.g., block, route, limit, distribute, or warm up a gateway)