How tsiparinda/capitalbank works
Component Details
a. Data Sources Layer:
• PrivatBank API (represented as an external system)
• iBank2UA CSV Files (represented as file storage)
b. Integration Layer (Core Application):
• API Interface Module (from /api)
• This as an abstract interface layer
• Bank-Specific Implementations:
• PrivatBank Module (/pbapi)
• CSV Processing Module (/csv)
• Logic Module (/logic)
• Subcomponents for:
• Payment Exchange
• Transaction Exchange
• Balance Updates
• Store Module (/store)
• Data operations components
c. Storage Layer:
• Capital ERP Database (show as a database symbol)
Flow Connections
• Data ingestion flows from PrivatBank API and CSV files
• Processing flows through the integration layer
• Storage flows to the database
Technical Details
Annotations for:
• Go-based implementation
• Database connection requirements
• File system dependencies
• API specifications
Key Architectural Patterns to Highlight:
• Interface-based design (api/interfaces.go)
• Modular architecture with clear separation of concerns
• Plugin-style bank integration system
• Data transformation pipeline
Remember to:
• Use consistent symbols throughout
• Version information
• Notes about scalability for new bank integrations