I’m putting together a dedicated module that will organise, validate, and record the financial traffic in my application. The scope is clear-cut: handle payments and transfers only—refund logic can remain out of scope for now. At minimum, I need: • A clean API (REST or GraphQL) that lets my front-end trigger a payment or a transfer, check its status, and pull a complete audit trail. • Secure transaction processing with idempotency keys, rollback on failure, and detailed logging that I can pipe into my existing monitoring stack. • Persistent storage structured so every transaction is immutable yet query-friendly for reporting. • Brief but complete developer docs and a post-deployment test suite so I can reproduce results locally or in CI. I’m happy to adopt whichever stack you’re strongest in—Node, Python, Go, or another—so long as the final codebase is Docker-ready and easy to slot into a Kubernetes cluster later. Direct hooks to bank APIs or payment gateways are welcome; you can mock them for the initial milestone if credentials are an issue. Quality, clarity, and extensibility matter more to me than sheer lines of code. If this sounds like your kind of build, let’s talk timelines and the best way to phase delivery.