Production Deployment &
System Architecture

A comprehensive technical breakdown of the Easypay Payment Terminal Service Provider (PTSP) and Middle-ware systems, engineered for high-availability transaction processing.

System Topology

The architecture is split into two critical routing layers: the PTSP Service for location and authentication, and the Middle-ware for core transaction orchestration across central switches.

PTSP Service Layer

easypay-ptsp-api
NIBSS SYSTEM Auth Token & Location Services
sweasyprodb
Table: NIBSS_TOKEN
access_token
token_type
expires_in
date_gen
ext_expires
token_name

Middle-ware System Layer

POS Terminal
Middle-ware System
NIBSS Switch
NCS Routing
ISW Switch
Kimono Service
sweasydb
Core Transaction DB

System Binaries Profile

Analysis of the compiled Java Archive (JAR) artifacts required for production deployment in /opt/prod/. Total system payload approaches ~670 MB.

Binary Mass Distribution (MB)

Ecosystem Composition

The ISW Kimono Integration Service and PTSP APIs form the largest individual application footprints due to extensive switch networking dependencies.

Deployment Pipeline

Strict sequential execution map for initializing the production environment with administrative privileges.

01

Environment Setup

Initialize secure directories and variable injections.

mkdir -p /etc/tms/prod/
touch /etc/tms/prod/.env
02

YAML Configurations

Establish routing and database overrides per service.

mkdir -p /etc/app-config/prod/
# 8 YAML files loaded
03

Keystore Binding

Mount the NIBSS SSL/TLS secure keystore.

nibss.ks required for Location Services handshake.
04

Daemon Init

Register and orchestrate 5 systemd unit files.

systemctl daemon-reload
systemctl enable <svc>
systemctl start <svc>