How PrimeShieldHub Works
The infrastructure, integrations, and safeguards behind every transaction. This page describes what we actually built — no more, no less.
Platform Architecture
PrimeShieldHub is built entirely on Cloudflare's global edge network. This means:
- Zero origin servers. Every request is handled on Cloudflare's edge (300+ cities), reducing latency globally.
- Cloudflare Workers handle API routing, authentication, and business logic using V8 isolates.
- Cloudflare Pages serves the static frontend with global CDN caching.
- Cloudflare D1 (SQLite-compatible) stores all relational data: products, orders, users, staff, reviews.
- Cloudflare R2 hosts product images and receipt PDFs (zero egress fees).
- Cloudflare KV caches high-read data like product lists and rate-limit counters.
The Engines
Price Guard (Fraud Prevention)
Before any payment is initialized, the priceGuard engine re-validates every line item in the cart against the product catalog in D1. If any price has been manipulated, the checkout is rejected with HTTP 403. This prevents cart-manipulation attacks where a user alters prices in the browser.
FX Engine (Currency)
Prices are normalized across currencies using the fxEngine. All prices are stored and displayed in Nigerian Naira (₦) by default. Multi-currency conversion uses live rates fetched from the FX engine at checkout time.
Logistics Engine
Shipping calculations use the logisticsEngine, which computes delivery cost based on weight, dimensions, and destination region. Delivery regions are stored in the delivery_regions table.
Payment Integrations
- Paystack — Primary payment gateway for NGN card, bank transfer, USSD.
- Coinbase Commerce — Cryptocurrency payments (BTC, ETH, USDC, and others). Handled entirely by Coinbase; we do not run our own blockchain node.
- Webhook verification — All payment webhooks are verified using HMAC-SHA256 signatures before processing.
Security
- Authentication: JWT tokens signed with HMAC-SHA256, stored in HttpOnly cookies with CSRF protection.
- Password hashing: Secure password hashing with per-user salts.
- Rate limiting: Cloudflare KV-backed rate limiter prevents brute-force attacks.
- Session security: All traffic uses TLS 1.3 (enforced by Cloudflare).
- Audit logging: All sensitive operations are logged to the
PAYMENT_LOGS_DBD1 database for fraud analysis. - Two-factor authentication: TOTP-based 2FA available for staff and admin accounts.
Real-Time Features
- Chat: Live customer-to-staff chat powered by Cloudflare Durable Objects (WebSocket).
- Notifications: Email (Resend), SMS (Telegram bot), and browser push notifications.
- Order tracking: Real-time order status updates via courier API integration. Updates are pushed as your package moves through the delivery stages.
Automated Background Operations
Every 6 hours, a scheduled Cloudflare Worker runs maintenance tasks:
- Checks for stale orders (orders without status updates).
- Sends reminder emails to staff about pending approvals.
- Recalculates product stock alert thresholds.
- Logs anomaly events to the security audit log.
These operations are automated — meaning they run on a schedule without human intervention — but they are rule-based, not AI-powered. The logic is deterministic and auditable.
AI-Assisted Features
We use OpenAI's API for the following features (which are clearly labeled as AI-assisted in the interface):
- Product recommendations based on browsing history.
- Chat assistant that answers common questions and escalates to human staff.
- Admin insights that summarize sales and inventory trends.
We do not use AI for: payment processing, fraud decisions, KYC verification, or order fulfillment. Those are deterministic, rule-based processes that are fully auditable.
What We Don't Claim
- We do not use blockchain technology. Reseller codes are securely generated random tokens, not blockchain assets.
- We do not use quantum computing or quantum-resistant cryptography (we use standard TLS 1.3 and HMAC-SHA256).
- We do not use satellite or IoT sensors for delivery tracking (we use courier API integrations).
- We do not use neural networks or deep learning for inventory management.
- We do not use smart contracts (reseller agreements are signed electronically and stored as PDFs).
Questions?
If you need to verify any specific claim on our website, or would like to see a technical walkthrough of the architecture, contact us at our contact page. We're happy to answer specific technical questions.
Last updated: October 2026. This page is maintained as part of our commitment to honest technical communication.