Skip to main content

​
System Architecture

OLIVE is a three-tier payment processing system designed for high security, scalability, and AI-powered decision making.

​
High-Level Architecture

​
Component Overview

​
Gateway (Go)

The public-facing REST API that handles all external requests.
ResponsibilityDescription
AuthenticationAPI keys, JWT, HMAC, service auth
Rate LimitingPer-client request throttling
Request RoutingRoutes to appropriate handlers
Audit LoggingComprehensive request/response logging

​
Wallet-Core (Go)

The secure financial engine that processes all transactions.
ResponsibilityDescription
LedgerAtomic transaction processing
AccountsMulti-currency account management
ComplianceTransaction monitoring and alerts
ReconciliationExternal processor reconciliation

​
Agent-TS (TypeScript)

AI-powered conversational agent for natural language interactions.
ResponsibilityDescription
NLUOpenAI-powered intent recognition
KYCDocument validation with OCR
ToolsWallet operations via function calling
WebhooksWhatsApp message handling

​
Data Flow

​
Payment Flow

​
Agent Message Flow

​
Security Layers

  • VPC isolation for internal services
  • Firewall rules restricting access
  • Network policies in Kubernetes
  • TLS 1.3 for all external traffic
  • mTLS for internal gRPC communication
  • Certificate rotation policies
  • JWT/OAuth2 authentication
  • API key management with scopes
  • Rate limiting per client
  • Input validation and sanitization
  • Encrypted database connections
  • Comprehensive audit logging
  • Idempotency keys for operations

​
Database Schema

​
Core Tables

TablePurpose
accountsUser accounts with balances per currency
transactionsCentral transaction ledger
subscribersUser profiles with KYC status
nfc_cardsCard serials linked to subscribers
agentsAgent/merchant accounts with float
audit_logTransaction and event audit trail
api_keysThird-party integration keys

​
Transaction Table Schema

CREATE TABLE transactions (
    id TEXT PRIMARY KEY,
    request_id TEXT UNIQUE NOT NULL,
    user_id TEXT NOT NULL,
    recipient_id TEXT NOT NULL,
    amount INTEGER NOT NULL,
    currency TEXT NOT NULL,
    status TEXT NOT NULL,
    memo TEXT,
    metadata JSONB,
    created_at TIMESTAMP,
    completed_at TIMESTAMP
);

​
Scalability

Gateway

Fully stateless, unlimited horizontal scaling behind load balancer

Agent

Stateless design with async request handling

Wallet-Core

Scale with read replicas, sharding by user_id for writes

Database

PostgreSQL with connection pooling and optimized indexes

​
Next Steps

Gateway Deep Dive

Explore the Gateway architecture in detail

Wallet-Core Ledger

Learn about the transaction processing engine