Hyperswitch is a composable open-source payments infrastructure built in Rust that provides a modular platform for processing payments through multiple connectors. The system handles the complete payment lifecycle including authorization, capture, refunds, and dispute management, while offering features like intelligent routing, 3DS authentication, revenue recovery, and analytics. Built with a microservices architecture using Actix-web, it features a plugin-based connector system, event-driven design with Redis/Kafka, and comprehensive SDK support for web and mobile platforms. The codebase demonstrates strong engineering practices with typesafe ID generation, robust encryption utilities, and well-abstracted interfaces that promote reusability and maintainability.
This repository implements a comprehensive Telegram bot for managing VPN subscriptions via Remnawave panel integration, featuring a web-based admin cabinet (cabinet) and public API (webapi). The system handles user subscriptions, payments (20+ gateways), referrals, promotional systems, contests, news, and support tickets. Architected with modular layers: Telegram bot handlers (aiogram), cabinet/web API routes (FastAPI), service-layer business logic, and SQLAlchemy ORM with Alembic migrations. Key entry points include main.py (application bootstrap), bot.py (Telegram setup), and unified_app.py (combined web server). Data flows involve Telegram interactions → handler processing → service execution → database CRUD operations, with webhook handlers for payment gateway callbacks and panel synchronization. External dependencies include Telegram Bot API, Remnawave API, PostgreSQL, Redis, SMTP, and numerous payment processors (Yookassa, CryptoBot, etc.). The codebase demonstrates strong engineering practices: clean separation of concerns, dependency injection, structured logging (structlog), and reusable patterns like event emitters, caching utilities, and retry queues. Payment processing abstraction shows particular skill with uniform CRUD interfaces across gateways. Active maintenance is evident through frequent releases, Dependabot integration, and responsive issue triage. While complexity arises from extensive feature set and payment integrations, the modular design contains coupling effectively. Technical drift is low due to current Python version (3.13), updated dependencies, and proactive schema migrations.
Payum is a framework-agnostic PHP payment processing library that unifies dozens of payment providers (PayPal, Stripe, Klarna, Authorize.Net, Be2Bill, Payex, Sofort, Offline, and others) behind a common API. The code reveals a dual architecture in transition: the mature 1.x action/request/reply model coexists with a newer 2.x command/handler/context model that returns typed result objects and executes through a middleware pipeline. Core capabilities include gateway factories, registry and container abstractions, token-based security URLs, pluggable storage backends (Doctrine ORM, MongoDB ODM, filesystem, Laminas), Twig template rendering, PSR-7/14/18 support, event dispatching, and currency/money handling. It is a library meant to be embedded inside Symfony, Laravel, or plain PHP applications, not a standalone service. The architecture is genuinely well-engineered: the middleware pipeline, handler map, token factory, and storage abstractions are cleanly separated and heavily unit-tested. However, the codebase is mid-migration between 1.x and 2.x APIs, with many deprecated legacy adapters and bridge classes still present. This dual-path design increases complexity and can confuse new users, but the core abstractions remain sound and reusable. The repository is a monorepo with per-gateway subpackages, extensive PHPUnit coverage, CI workflows, static analysis, and release automation. Technical drift is moderate: gateway integrations using old SOAP/XML-RPC SDKs and deprecated Symfony/Httplug bridges are aging, while the core 2.x architecture is actively maintained.
The stripe/java repository is the official Java client library for the Stripe API, providing type-safe access to Stripe's payment processing and financial services. It features a layered architecture with model classes representing Stripe objects, service classes for API resource access, parameter builders for request configuration, and webhook handling infrastructure. The library supports both legacy static API patterns and a modern instance-based StripeClient entry point, with comprehensive telemetry, expandable fields, and extra parameters for accessing beta features. Code generation from OpenAPI specs ensures consistency with Stripe's API evolution, while hand-crafted components like utility classes and webhook verification demonstrate engineering excellence.
This repository is a collection of Odoo Community Association (OCA) addons focused on extending accounting and invoicing functionality in Odoo. It provides over 50 modules that automate invoice processing, manage taxes and discounts, handle refunds and returns, integrate stock operations with invoicing, and enhance partner-specific invoicing workflows. Each module follows standard Odoo module structure with models, views, wizards, and data files, extending core Odoo models like account.move, sale.order, and stock.picking via inheritance. The modules are loosely coupled but may have interdependencies declared in their manifests. The system is designed to be installed within an Odoo instance, with entry points defined in each module's __init__.py and __manifest__.py files. Recent activity (last commit 2026-09-25) and active maintenance indicate a healthy project, though the wide version support (some modules targeting Odoo 9.0c-18.0) requires careful dependency management.
This repository implements a banking system built with ASP.NET Core that enables users to create bank accounts, manage cards, transfer funds internally and between banks via a central API, and process payments. The system features a modular architecture with separate projects for the main bank web application, central API for inter-bank communication, and a demo shop showcasing payment integrations. Key capabilities include user authentication with 2FA, email notifications via SendGrid, security measures like reCAPTCHA and request encryption, and role-based administration. The solution follows layered architecture patterns with separation of concerns between presentation, service, and data access layers, utilizing Entity Framework Core for ORM and AutoMapper for DTO mapping.