A Configuration Guide

Payment Gateway Routing and Optimization in Juspay

Priority Logic is a gateway routing and decision-making framework in the Juspay Payment Platform. It allows you to define rules that determine how payment transactions are routed across configured payment gateways based on performance, business requirements, cost optimization, and fallback handling.

By configuring Priority Logic, merchants can:

• Improve success rates by routing to healthier gateways.

• Ensure business continuity during gateway downtime.

• Route transactions based on payment attributes (card type, issuer bank, PSP, etc.)

• Maintain control and transparency over gateway selection.

Accessing the Priority Logic Dashboard

1. To open the Priority Logic Dashboard:
   Juspay Dashboard → Payments → PG Control Center → Priority Logic

2. Or navigate directly to:
   https://portal.juspay.in/gateways/priority-logics

1. Dashboard Overview

1.1 Active Priority Logics

The Active Priority Logics section displays all currently active routing configurations along with their real-time performance metrics. This view helps you monitor how each configuration is performing and how traffic is distributed across them.

1.2 All Priority Logics Table

The All Priority Logics table lists every routing configuration created. This includes both active and inactive configurations, helping you view, manage, and track the full history of your routing logic setups.

2. Creating a New Priority Logic

You can create three types of Priority Logic configurations based on your business requirements:

2.1 Advanced Routing

Offers maximum flexibility for defining routing rules using various combination of dimensions such as payment method, card BIN, issuer bank, and PSP etc..

Under Advanced Routing, you can choose between:

1. Rule-Based UI: Create rules using a visual drag-and-drop interface.

2. Code-Based UI: Define routing behavior using custom JavaScript code (requires additional approval in production).

2.1.1 Rule-Based Priority Logic Configuration

Rule-Based Routing in Priority Logic allows you to define transaction routing conditions using a visual “if–then” interface. This lets you control how payments are directed to different gateways based on transaction attributes for example, card type, card issuer, payment method, amount and more.

2.1.2 Code-Based Priority Logic Configuration

The Code-Based Priority Logic option allows merchants and developers to define custom routing logic using JavaScript. This configuration method is allowed only for certain advanced usecases, beyond what can not be achieved through the visual Rule-Based UI.

Key Use Cases

• Complex routing conditions involving multiple dynamic parameters

---

2.2 Default Routing

A simple, order-based routing strategy. Traffic is routed according to the priority order of gateways.

---

2.3 Volume-Based Routing

Routes traffic across multiple gateways based on predefined volume thresholds. This helps distribute load evenly while maintaining optimal performance.

• Adjust gateway weights for performance or cost optimization.

---

3. Core Concepts Behind Priority Logic

3.1 Default Gateway Configuration

This is different from Default Routing. It is configured under both Rule-Based and Volume-Based Routing.

It lets you set fallback gateways that process transactions when routing rules configured do not matches, ensuring smooth payment flow and uninterrupted service.

Key highlights include:

• Always-available fallback options to keep transactions flowing.

• Cascading fallback logic that routes through gateways in sequence.

• Emergency routing during outages to maintain uptime.

• Performance-based automatic switching for optimal success rates.

3.2 Managing Existing Priority Logics (View, Edit and Delete)

• View a Priority Logic: 00:00
  Filter and select the configured Priority Logic you want to view, then click to view it.

• Edit a Priority Logic: 00:14
  To make changes, create a copy of the existing logic, update the required configurations, and save it.

• Delete a Priority Logic: 00:47
  Locate the logic you wish to delete, click the bin icon on the right, and confirm the deletion.

3.3 Full and Staggered Release

• Under Full Release 100% of traffic is routed through the new configuration instantly.

• Staggered Release means gradually rolling out a new Priority Logic configuration to live traffic instead of activating it for all transactions immediately.

  Only a small percentage of live traffic (say 10%, 20%, etc.) is routed to the new logic initially, while the rest still uses the old configuration.

Example

You create a New Volume-Based Priority Logic:

Now, Instead of routing all transactions through this new logic immediately, you choose staggered activation at 10%, therefore;

• Only 10% of traffic uses the new routing; 90% continues with the previously configured logic.

• This allows you to:

  • Test the new logic with limited exposure.

  • Monitor performance, success rates, and routing accuracy.

  Gradually increasing traffic to 100% once verified.

3.4 Rule Configuration Options

When configuring a new rule within Priority Logic, several options are available to help you manage, share, and enforce routing behaviors effectively.

4. Use Cases

Use Case 1

Gateway Performance Optimization

Scenario: Operations team needs to optimize transaction routing based on gateway performance metrics.

Configuration:

• Rule-based routing with performance conditions

• Gateway priority based on success rates

• Automatic failover for underperforming gateways

Outcome: Improved transaction success rates and optimized gateway utilization.

Use Case 2

Business Rule Implementation

Scenario: Business team needs to implement specific routing rules based on transaction characteristics and commercial agreements.

Configuration:

• Transaction amount-based routing rules

• Card issuer and currency-specific routing

• Commercial agreement compliance routing

Outcome: Alignment with business objectives and revenue optimization.

Use Case 3

Disaster Recovery and Failover Management

Scenario: Technical team needs to ensure business continuity during gateway outages or technical issues.

Configuration:

• Robust failover logic with cascading gateways

• Emergency routing during outages

• Automated recovery processes

Outcome: Business continuity during outages with minimized transaction failures.

5. FAQ & Troubleshooting Guide

Configuration Validation Errors

API and System Errors

Code-Based Configuration Errors

Gateway-Based Configuration Errors