System Architecture & Tenant Isolation
Rook is architected using highly resilient cloud infrastructure, distributed container runtimes, enterprise API gateway management, and zero-trust tenant boundaries.
End-to-End Request Pipeline
Every API request follows a hardened multi-stage pipeline designed for low-latency routing, strict authorization checking, and immutable auditing before executing money movement or card operations.
Global Anycast load balancing terminates TLS 1.3, mitigates DDoS attacks, and verifies protocol framing.
Inspects Authorization & X-Program-ID, enforces rate limits, and validates request schema.
Enforces ledger consistency, evaluates card velocity rules, and records cryptographic idempotency keys.
Dispatches transactions to Visa/Mastercard network or Federal Reserve FedNow clearing gateway.
Core Architectural Layers
1. Enterprise API Gateway & Perimeter Governance
The gateway acts as the single point of entry for all partner applications. It handles:
- Credential Validation: Validates Bearer API keys against active program perimeters in sub-millisecond memory stores.
- Distributed Rate Limiting: Enforces tier-based requests-per-minute (RPM) quotas per organization.
- Environment Fencing: Strictly guarantees that requests targeted at Sandbox endpoints cannot query or alter production databases.
2. Program Partitioning & Multi-Tenancy
Rook employs logical multi-tenant partitioning at the database and ledger layer. Every database table query is scoped by the caller’s validated program_id. This architecture guarantees that even in multi-program organizations, transactions, card numbers, and ledger entries remain strictly segregated.
3. Event-Driven Webhook Delivery Engine
When asynchronous events occur (such as an incoming card authorization, a settled FedNow transfer, or an ACH return), Rook's distributed event engine signs the payload using HMAC-SHA256 and dispatches it with exponential backoff retries over a 72-hour delivery window.