Merchant
| Metadata | Value |
|---|
| TAM Boundary | #7 of 12 |
| Mission | Merchant onboarding and lifecycle |
| Key Capabilities | Merchant onboarding, activation, configuration, hierarchy management |
| Last Scanned | 2026-01-09 |
Overview
The Merchant boundary manages the complete merchant lifecycle from onboarding through activation and ongoing configuration management. This includes merchant hierarchy, gateway configuration, and activation across multiple systems (Integra, 3CDB, Datatrans).
Applications
- Merchant Activation - Cross-system merchant activation service
- Gateway Service Activation (SVA) - Integra/3CDB merchant activation
- UPP Admin - Datatrans merchant configuration
Repository Inventory
Architecture Notes
Merchant Activation Flow
Onboarding System → Merchant Activation Service → Target Systems
├── Integra/3CDB
├── Datatrans (UPP)
└── PSW
Key Integrations
- Integra Portal API - Merchant management in Integra
- 3CDB - Gateway configuration database
- UPP Admin Backend - Datatrans merchant configuration
- PSW Merchant Service - PSW merchant data
Strategic Direction
- Unified merchant onboarding through Planet Portal
- Single source of truth for merchant master data
- Automated cross-system activation
Technology Stack
| Component | Technology |
|---|
| Merchant Activation | TypeScript, Node.js |
| SVA Backend | C# (.NET) |
| SVA Frontend | Angular, TypeScript |
| Message Broker | RabbitMQ |
| Infrastructure | Terraform (HCL) |
Data Flow to Analytics
Merchant data flows to Snowflake via:
dataeng-dip-etl-dt-merchant - Datatrans merchantsdataeng-dip-etl-ccc-merchant - CCC/Integra merchants
Future Considerations
- Centralized merchant master data service
- Self-service merchant onboarding in Planet Portal
- Merchant hierarchy API for complex merchant structures
