Skip to content

PulseRoute

Predictive payment routing engine that keeps transactions flowing when processors fail.

PulseRoute monitors payment processor health in real-time and automatically reroutes traffic before failures impact your customers. It operates across three tiers of intelligence:

Tier Name What it does
Tier 1 Sentinel Health-based failover. Detects failures and switches to backup processors.
Tier 2 Foresight Predicts failures before they happen, enabling pre-emptive routing changes.
Tier 3 Autopilot Continuously optimizes traffic allocation across processors in real-time.

Key Features

  • Sub-10ms routing decisions at 300+ decisions/sec
  • Flexible routing rules — match by country, currency, payment method, and more
  • Zero-downtime failover with automatic recovery detection
  • Shadow mode — observe what PulseRoute would do before going live
  • Prometheus metrics and pre-built Grafana dashboard
  • Webhook alerts for failover events with HMAC-SHA256 signing
  • Multi-language SDKs — Node.js, Python, Java, and REST API
  • Multi-tenant with full data isolation
  • Docker-ready deployment

Quick Example

# Start the stack
docker compose up -d

# Add a routing rule
curl -X POST http://localhost:8080/v1/rules -H "Content-Type: application/json" -d '{
  "rule_id": "us_cards",
  "attributes": ["US", "USD", "card"],
  "primary_id": "stripe", "primary_name": "Stripe",
  "secondary_id": "adyen", "secondary_name": "Adyen"
}'

# Get a routing decision (pre-transaction)
curl -X POST http://localhost:8080/v1/route -H "Content-Type: application/json" -d '{
  "country": "US", "currency": "USD", "payment_method": "card",
  "card_type": "visa", "amount": 99.99
}'

# Report the outcome (post-transaction)
curl -X POST http://localhost:8080/v1/outcome -H "Content-Type: application/json" -d '{
  "rule_id": "us_cards", "processor_id": "stripe",
  "success": true, "latency_ms": 120.0
}'

What Happens When a Processor Fails?

  1. Tier 1 detects the error rate crossing the threshold
  2. Tier 2 predicted the failure before it happened, pre-emptively shifting traffic
  3. Tier 3 has already optimized the traffic split across healthy processors
  4. A webhook fires to your alerting system
  5. The dashboard shows the failover in real-time
  6. When the processor recovers, traffic gradually shifts back

Next Steps