High-Level Topology
The diagram below illustrates the flow of raw provider events through the Indic8 ingestion and processing layers:Architectural Components
1. Edge Ingress Gateway
The ingress gateway acts as the initial frontline receiver.- Signature Verification: Validates HMAC-SHA256 signatures for Stripe, Polar, Lemon Squeezy, and Paddle.
- Idempotency Guard: Extracts provider event IDs into an in-memory Redis cache with 48-hour expiration to prevent duplicate billing records.
- Immediate Acknowledgment: Responds to providers with
200 OKwithin 25ms to prevent timeout retries, then delegates processing to the asynchronous worker queue.
2. Atomic Normalization Pipeline
Each payment provider formats payloads differently. Indic8 parses nested metadata into a uniform canonical schema:3. Real-Time Foreign Exchange (FX) Engine
Indic8 connects to the European Central Bank (ECB) reference feed and cross-references historical intraday spot rates for 140+ currency pairs.- Multi-currency sales in EUR, GBP, JPY, CAD, and AUD are converted to your workspace base currency at the exact second of purchase.
- Zero conversion spread is applied, guaranteeing accurate net revenue reconciliation.
4. Zero-PII Sovereign Privacy Vault
Before records are written to PostgreSQL:- Customer names, IP addresses, and email prefixes are scrubbed.
- An irreversible cryptographic one-way salt generates a pseudo-anonymous
customer_hash. - Sensitive tokens are sealed client-side using Web Crypto AES-256-GCM keys that are never shared with backend telemetry servers.
5. WebSocket Telemetry Broadcaster
Every committed transaction emits an event to the internal Pub/Sub channel. Connected clients receive the live transaction stream with sub-10ms latency.Resilience and Scalability
Horizontal Scaling
Ingress workers run statelessly across multiple edge regions, scaling dynamically based on traffic spikes.
Dead Letter Queue
Malformed or rejected provider payloads are isolated in an encrypted dead-letter queue for inspection and replay.