The Problem.

• Legacy Processes: Legacy software depended on other vendors for working.
• In-house Need: Wanted an in-house Application for Trade Finance, BG, LC, SBLC, etc.
• Inefficiency: Lengthy turnaround times and manual verification.
• Security Risks: Need for granular authorization in high-stakes financial environments.

TradeX Architecture.

A highly scalable, secure, and resilient microservices platform.

System Architecture for
Authentication.

Powered by ORY Hydra

• OAuth 2.0 and OpenID Connect provider.
• Stateless, API-first architecture.
• Secure token issuance and validation for all microservices.
• Replaced traditional session-based auth with modern JWTs.

System Architecture for
Authorization.

Powered by Permify (ReBAC)

• Relationship-Based Access Control (ReBAC) inspired by Google Zanzibar.
• Fine-grained permissions for specific financial entities (e.g., specific branches, specific corporate clients).
• Decoupled from business logic, ensuring scalable security policies.

Maker-Checker.

Implementing robust concurrency controls.

• 4-Eyes Principle: Crucial for banking operations to prevent fraud.
• Concurrency Issues: Resolving race conditions when multiple checkers attempt to approve simultaneously.
• Pessimistic Locking: Enforced via PostgreSQL `SELECT ... FOR UPDATE`.
• Optimistic Locking: Leveraging version numbers for safe state transitions.

Financial Messaging.

• SWIFT (MT700 series): International generation of LCs securely formatted and transmitted.
• SFMS: Domestic messaging for Indian financial institutions.
• Automated Parsers: Robust parsers to translate business entities into standard banking formats.

Conclusion &
Learnings.

• Transitioned from academic theory to enterprise-grade production systems.
• Mastered backend services design, component architecture, and modern database modeling.
• Gained deep domain knowledge in Trade Finance (LCs, BGs).
• Learned the importance of TDD, clean architecture, and rigorous code reviews.

Thank You.

Any questions?