Livoa LogoLivoa
ADPay / MPay — Replatform Architecture (FSS → Safexpay)
Customer Interfaces


- Ecommerce Checkout (Hosted fields / SDK)

- Mobile Apps (PWA / Native)

- PayByLink / Chatbot

- POS Terminals (EMV / Contactless / QR)

API Gateway & Edge


- OAuth2 / mTLS / WAF

- Rate limiting / TLS termination

Payments Core - Orchestrator


- Payment Orchestrator (flow engine)

- Biller / Split Engine

- Tokenization Service

- Fraud & 3DS Orchestration

- Notification Service

Adapters & Integration


- Gateway Adapters (Safexpay, MPGS, CyberSource)

- POS Adapter (ISO8583 / EMV)

- FAB Core Banking Connector

Settlement & Reconciliation


- Settlement ingest (files / realtime)

- Reconciliation engine & reports

- Settlement -> FAB GL posting (REST/SFTP)

External Systems & Partners


- Safexpay (Acquirer / Aggregator)

- MPGS / CyberSource (Gateways)

- FAB Core Banking / GL

- ADDA / Biller Platform

- 3DS Provider, Fraud vendors, Payment Networks (Visa/Mastercard)

Message Bus / Event Stream (Kafka)


- payments.events, settlements, reconciliation, notifications

Data & Storage


- Postgres (transactions, merchants, services)

- Event store / ledger (append-only)

- Redis cache

- S3 object store (reports, exports)

- HSM / KMS for keys

Ops & Observability


- Monitoring (Prometheus, Grafana)

- Tracing (OpenTelemetry)

- Logging (ELK/OpenSearch)

- Ticketing & ITSM integration

Notes / Key Design Decisions


- Tokenization & hosted fields to minimize PCI scope

- Event-driven architecture (Kafka) for async splits & retries

- Idempotent APIs with Idempotency-Key header

- Support unified API for POS & Ecommerce; adapters isolate protocol differences

- Phased rollout: PoC -> Pilot -> Production -> Scale

Diagram

by Mr Che

0
0 uses