Tehran, Iran · UTC+3:30
Software Architect & Engineer
Payment systems, core banking, ERP.
For six years I've built backend systems where a mistake costs somebody money. A payment gateway and core-banking platform at Hami System Sharif. A provider-agnostic payment layer over Stripe and NMI for LeadFi in the United States. An ERP that five departments at AhanOnline still run on. Since 2025 most of my time has gone into products of my own, and two of them are live.
Three products, all of them mine. Two are live, and the third stays unnamed until it ships.
Founder · architect
A Persian-language AI legal assistant for Iranian law, with a network of licensed lawyers.
It answers from the text of the law itself and checks every citation against the statute before the user sees it.
Open dadyar.pro
Founder · architect
A cloud accounting and ERP platform for Iranian businesses.
Every module posts to one shared ledger, so approving an invoice records the journal entry and updates inventory in the same step.
For teams whose audience lives in messaging apps rather than social feeds. Workspace isolation enforced in the data layer, subscription billing, channel and bot administration, an operator console behind it.
If that's close to something you're working on, ask me. I'll tell you more than this page does.
Four engagements worth describing. Two as an employee, two on my own.
Payments · United States · 2025 to now
LeadFi pre-qualifies consumer leads: a client posts a contact, the platform calls a credit API, and sends back a tier, a status and the finance offers behind it. I own the money side of that, which is everything from whether a request is billable to getting paid for it.
The processor sits behind an abstract provider interface, so Stripe and NMI are two implementations of one set of methods instead of two paths through the codebase. Checkout sessions, charges against a saved card, tokenization and vaulting, refunds, customer portals and webhook signature verification all return the same shapes whichever provider is configured. Card verification is a one-dollar authorisation and an immediate refund. Invoice numbers are allocated under a retry, because the sequence is contended and two concurrent payments will otherwise pick the same one.
Changing processor used to be a rewrite. Now it's configuration.
Django, DRF, PostgreSQL, Celery, Redis, JWT, Stripe, NMI, Prometheus
Payment gateway and core banking · Iran · 2025 to 2026
Lead architect on PayWeb, the payment gateway now running at payweb.ir, then senior architect on core banking. I set the microservice boundaries and the technical standards the team built against, and designed the distributed payment services that talk to several providers at once under PCI-DSS-aware constraints.
One constraint shaped everything else: a transaction is allowed to be slow, and it is never allowed to be lost.
Microservices, distributed transactions, high availability, PCI-DSS-aware design
Platform and integrations · Europe · 2025 to 2026 · under NDA
A whole .NET service estate delivered end to end: a webhook-driven messaging bot service, an embedded web client over REST and OpenAPI, internal admin APIs, and crypto-gateway integrations. Containerized, with CI/CD from the first commit rather than bolted on at the end.
ASP.NET Core (.NET 10), EF Core, PostgreSQL, Redis, Docker Compose, GitHub Actions
ERP and trade platform · Iran · 2020 to 2025
An online marketplace for steel and iron in Iran. I led the ERP that its call center, trade, accounting, procurement and sales teams work in, then spent the following year on the unglamorous half of the job: making it hold up under real transaction volume and rewriting the internal workflows it had inherited.
Before the ERP I built their warehouse and inventory system in Nest.js, which is where I learned what production actually costs.
Domain modelling, high-volume data, SQL Server, Nest.js, TypeScript, RBAC
Founder, software architect, technical lead
Own products, and a short list of client engagements. A few engineers work with me.
Backend engineer, remote (United States)
Provider-agnostic payments over Stripe and NMI for a lead pre-qualification platform. Django, PostgreSQL, Celery.
Backend engineer, remote (Europe)
ASP.NET Core services, messaging bot platform, admin APIs, crypto-gateway integrations.
Senior backend developer, lead architect
Payment gateway architecture, then core banking. Microservice boundaries and team standards.
PayWebThe payment gateway I architected there. Live at payweb.ir.
Senior backend developer
ERP across call center, trade, accounting, procurement and sales. Security and performance work.
Backend developer
Warehouse and inventory system in Nest.js. REST APIs, role-based access control.
2019 to 2023B.Sc. Business Management, University of Applied Science and Technology, Tehran
C#, Python, TypeScript, SQL
ASP.NET Core (.NET 10), EF Core, Django, Django REST Framework, Celery, Nest.js
Clean architecture, CQRS with MediatR, event-driven design, microservice boundaries, domain and data modelling
Gateway design, Stripe, NMI, tokenization and vaulting, webhook reliability, idempotency, PCI-DSS-aware design, core banking
PostgreSQL, SQL Server, Redis, pgvector
Docker, Docker Compose, GitHub Actions, Prometheus, structured logging, OpenAPI
Machine-learning research. Dadyar runs on retrieval and citation checking; the model underneath it is somebody else's, and if your problem needs one built and tuned from scratch I'd be guessing. Native mobile is the same story. I can review the work and I shouldn't own it.
I take on one or two things at a time. The work I'm useful for tends to look the same from the outside: money moves through the product, or regulated data sits inside it, or the codebase has quietly become expensive to change and nobody can say exactly when that happened.
You get a written architecture your engineers can argue with. I build the parts that carry the most risk myself and hand the rest over with the reasoning attached. A few engineers I've worked with before come in when a project needs more hands. There's no agency behind me and nobody in the middle.
If your problem isn't one I'm good at, I'd rather say so on the first call than find out in month three.
Yes, and I do now. LeadFi is in the United States and my 2025 to 2026 platform client was in Europe. Payment and contracting arrangements are worth settling in the first week, and I've had that conversation enough times to keep it short.
That I own the shape of the system and still write the code for the parts that matter. Payment flows, data models, anything with money or compliance in it. I've never wanted the version of the job where you stop opening the editor.
For one more engagement this year. Not for a full-time role, because most of my week belongs to my own products.
Telegram. I read it myself and usually answer the same day. Email works too, it's just slower. If you would rather talk, the number is below.
Tell me what you're building and where it hurts. A paragraph is enough to start, and I'll tell you quickly whether I'm the right person for it.
vCard, 2 KB. Opens straight into your contacts app.