---
type: system
title: Payments platform microservices — billing, notifications, crypto integrations
domain: fintech
services: [backend-platform]
skills: [Microservices, Idempotency, Event-Driven Architecture, gRPC, Technical Leadership]
technologies: [Go, Gin, gRPC, Python, FastAPI, Kafka, Redis, PostgreSQL, Docker]
problem: A B2B payments platform needed new product capabilities — billing, email notifications, cryptocurrency integrations — without destabilizing the existing system or risking the money-critical payment path.
approach: Designed the capabilities as separate microservices in Go (Gin) and Python (FastAPI), with gRPC for synchronous calls and Kafka for event streaming. Made money-critical flows safe under retries with idempotency keys and a producer outbox → consumer inbox dedup, and isolated failures so a slow crypto provider or a notification outage can't take down billing. Redis for caching, queues, and rate limiting.
result: A fault-tolerant microservice architecture where new services ship without risking the core payment path — with zero double-processing of payment events under retries. Led the team of 4 engineers delivering it.
evidence: Described in work history (Korvax, 2022–present); design decisions discussable in a call.
public_links: []
available_for: private walkthrough
language: en
canonical: https://asmanmalikov.com/en/proof/payments-microservices/
---

# Payments platform microservices — billing, notifications, crypto integrations

- **Problem:** A B2B payments platform needed new product capabilities — billing, email notifications, cryptocurrency integrations — without destabilizing the existing system or risking the money-critical payment path.
- **Approach:** Designed the capabilities as separate microservices in Go (Gin) and Python (FastAPI), with gRPC for synchronous calls and Kafka for event streaming. Made money-critical flows safe under retries with idempotency keys and a producer outbox → consumer inbox dedup, and isolated failures so a slow crypto provider or a notification outage can't take down billing. Redis for caching, queues, and rate limiting.
- **Result:** A fault-tolerant microservice architecture where new services ship without risking the core payment path — with zero double-processing of payment events under retries. Led the team of 4 engineers delivering it.
- **Evidence:** Described in work history (Korvax, 2022–present); design decisions discussable in a call.