OLTP (Online Transaction Processing)
| Metadata | Value |
|---|
| TAM Boundary | #2 of 12 |
| Mission | Real-time transaction processing |
| Key Capabilities | Authorization, card-present processing, e-commerce gateway, acquirer routing, scheme connectivity |
| Last Scanned | 2026-01-09 |
Overview
The OLTP boundary handles all real-time payment transaction processing across multiple channels. This includes card-present (POS terminals via Integra), e-commerce (Datatrans/DFS), and routing to acquirers (NAS) or Planet's own acquiring platform (PSW).
Applications
- Datatrans/DFS - E-commerce gateway, tokenization, 3DS, Pay-by-Link (Tier 1)
- Integra FE - Card-present gateway for POS terminals
- NAS - Acquirer switcher routing to Planet (PSW) or 3rd party acquirers
- PSW - Core acquiring solution for card processing with scheme connectivity
Datatrans (DFS) - E-commerce Gateway
Repository Inventory
DFS Architecture Notes
- Heavy external API integrations: Apple Pay, Visa CTP, Mastercard CTP, Vipps, MobilePay, Twint
- UPP database contains 77+ JPA entities
- Synchronous REST communication pattern (no Kafka)
- Zuora integration for PCI Proxy usage-based billing
PSW (Planet Switch) - Acquiring Platform
Repository Inventory
PSW Architecture Notes
- .NET monolith with 200+ projects, microservices PoC in progress
- Supports all major schemes: Visa, MasterCard, Amex, Discover, JCB, Diners, UnionPay
- Three main databases: PPTables (config), Switch (core), Transactions (logs)
- Kafka producer for SchemeResponded events to Data Platform
- HSM integration: Thales, SafeNet, Atalla, CipherTrust
NAS (Network Access Switch) - Acquirer Router
Repository Inventory
NAS Architecture Notes
- 65+ processor modules for global acquirer connectivity
- Naming convention:
proc-{currency}{identifier} (e.g., proc-usdfd, proc-gbpax)
- Protocols: ISO 8583 (CCC 3C variant), GICC/GICCx, Nexo XML
- Connection types: HTTPS, raw sockets (TNS), Apache MINA
- Oracle database for transaction logging and configuration
Integra FE - Card-Present Gateway
Repository Inventory
Integra Architecture Notes
- Terminal protocols: ISO 8583, Nexo/ns3cXml, OPI
- Routes to: NAS (3rd party acquirers), PSW (Planet acquiring), DGW (APMs)
- Databases: 3CDB (config), 3CINTEGRADB (integra), 3CTOKENDB (tokens), 3CDCCDB (DCC)
- RabbitMQ for async terminal communication
Cross-Cutting Architecture Notes
Transaction Flow
POS Terminal → Integra FE → NAS → PSW/3rd Party Acquirer → Card Scheme
│
E-commerce → Datatrans → PSW → Card Scheme
Data Flow to Analytics
All systems publish events to Kafka for consumption by Data Platform (Flink workers → Snowflake)
Technology Summary
| System | Language | Database | Message Broker |
|---|
| Datatrans | Java | MySQL/PostgreSQL | - |
| PSW | C# (.NET) | SQL Server | Kafka |
| NAS | Java | Oracle | - |
| Integra FE | Java | SQL Server | RabbitMQ |