Multi-PSP Routing

Priority System

The priority-based routing combines two levels of priority to calculate an effective score for each payment method:

// Effective Priority Formula
effective_priority = method_priority + (psp_priority × 0.2) + boost

// Example calculation
// Method Priority: 80 (set by merchant)
// PSP Priority: 90 (set by admin)
// Boost: 0 (no rule boost active)
effective_priority = 80 + (90 × 0.2) + 0 = 98

Routing Rules

Routing rules provide fine-grained control over payment method selection. Each rule has conditions that are evaluated against the transaction context, and an action to execute when all conditions match.

Rule Types

Routing Context

Each transaction generates a routing context containing the following fields that can be used in rule conditions:

Condition Operators

Rules support a rich set of operators for building conditions:

// Example routing rule structure
{
    "rule_name": "Route US high-value to primary PSP",
    "rule_type": "route_to",
    "priority": 100,
    "conditions": [
        {
            "field": "country",
            "operator": "equals",
            "value": "US"
        },
        {
            "field": "amount",
            "operator": "greater_than",
            "value": 1000
        }
    ],
    "actions": {
        "route_to": "payment_method_id_here"
    }
}

Cascading & Failover

When a payment attempt fails with the selected PSP, EPaySe automatically cascades to the next available payment method. This ensures maximum payment success rates.

// Cascading failover flow
Transaction → PSP A (primary, priority 98)
    ↓ Failed (timeout/declined)
Transaction → PSP B (secondary, priority 85)
    ↓ Failed (declined)
Transaction → PSP C (tertiary, priority 72)
    ✓ Success

How Cascading Works

Routing Context

For each transaction, EPaySe builds a routing context containing all available information about the transaction, customer, and timing. This context is used to evaluate routing rules.

// Routing context built for each transaction
{
    "country": "US",
    "ip_country": "US",
    "card_bin": "411111",
    "card_brand": "visa",
    "card_type": "credit",
    "amount": 150.00,
    "currency": "USD",
    "customer_email": "[email protected]",
    "customer_email_domain": "example.com",
    "customer_ip": "192.168.1.1",
    "time_of_day": "14:30",
    "day_of_week": "Monday",
    "hour_of_day": 14,
    "transaction_id": "01abc...",
    "merchant_id": "01xyz..."
}

PSP Management

Platform administrators manage PSP configurations through the admin dashboard. Each PSP has the following controls:

PSP Status Lifecycle

Dashboard Configuration

For Merchants

Merchants can manage routing through the merchant dashboard:

• Payment Method Priorities — Set the priority (0-100) for each assigned payment method
• Routing Rules — Create custom rules based on transaction conditions
• Rule Testing — Test routing configuration with sample transactions before going live
• Analytics — View routing decision history to understand how transactions are being routed

For Admins

Platform administrators have additional controls:

• PSP Management — Enable/disable PSPs, manage credentials, freeze/unfreeze
• Merchant PSP Assignment — Assign PSPs to merchants with per-merchant priority
• Global Configuration — Set platform-wide routing defaults and PSP weights
• Monitoring — Track PSP health, success rates, and routing patterns

Best Practices