What is MPAC?
MPAC (MP-Solution Advanced Cloud Service) is a cloud platform for SmartPOS payment terminals, providing end-to-end payment processing, device management, and merchant services.
The Platform
MPAC powers S-Pitt terminals — the Smart Parallel Intelligent Transaction Tool — available in two form factors:
| Terminal | Description |
|---|---|
| S-Pitt Air | Countertop SmartPOS terminal |
| S-Pitt Mobile | Portable handheld terminal |
These Android-based terminals run business applications for QR code payments, credit card processing, cash management, order/bill handling, and customer loyalty — all connected to the MPAC cloud platform.
What MPAC Does
For Merchants
- Accept payments — QR code (via payment providers), credit card, and cash
- Manage stores — multi-store, multi-terminal configurations
- Track sales — real-time reporting and settlement via the merchant portal
- Customer engagement — loyalty programs and digital receipts
For Payment Providers
- Provider integration — plug-in adapter pattern for QR payment providers
- Per-store credentials — each store can have different provider configurations
- Transaction lifecycle — full PaymentIntent state machine with idempotency
For Operations Teams
- Centralized observability — metrics, logs, and traces in Grafana
- Device management — remote app updates, terminal monitoring
- Infrastructure as code — AWS CloudFormation with isolated VPCs per system
Platform Components
| Component | What It Does | Key Technology |
|---|---|---|
| mpac-smartpos | Core platform — portal, APIs, terminal services | FastAPI, Go/Gin, React |
| mpac-pgw | Payment gateway — PaymentIntent lifecycle, provider adapters | Go 1.24, PostgreSQL, Redis |
| mpac-obs | Observability — centralized telemetry collection | Alloy, Prometheus, Loki, Tempo, Grafana |
| mpac-infra | Infrastructure — AWS resources, networking, deployments | CloudFormation, isolated VPCs |
Multi-Tenant Architecture
MPAC supports multiple organizations and merchants on a single platform:
Each level in the hierarchy has its own configuration, credentials, and data isolation.
Environments
| Environment | Domain | Purpose |
|---|---|---|
| Production | mpac-cloud.com | Live merchant traffic |
| Staging | mpac-cloud-stg.com | Pre-release validation |
| Development | mpac-cloud-dev.com | Active development and testing |
All environments run in ap-northeast-1 (Tokyo), separated by AWS account.
Next Steps
- Getting Started — set up the development environment
- Architecture Overview — system topology and design
- SDK Quick Start — integrate payments from your application
- API Reference — payment gateway endpoints