Money movement
Multi-PSP routing, idempotent deposits and withdrawals, double-entry ledgers, and reconciliation against provider statements. The parts where a duplicate posting is a clawback and a regulator conversation.
Aldiger
Mehilli
Software architect for regulated .NET platforms — money movement, identity and compliance. Ten years designing systems where state has to be correct and auditable, and shipping them.
About
I design and ship server-side systems for regulated products — money movement, identity and onboarding, e-signature, compliance reporting, and the operational surfaces that keep them running. The through-line is not an industry: it is state that has to be correct, recoverable and explainable to somebody who audits it. I am deepest in payments, and that is where the work has run longest.
I care about clear contracts between services, predictable failure modes, and the unglamorous work of making systems observable and debuggable long after they ship.
Alongside client work, I run value.al, a software studio in Tirana, where I also write about payments and integration work.
Focus
Distributed services
Outbox and inbox over dual writes, message-driven workflows, and explicit state machines — so retries, partial failures and replayed webhooks settle to one correct answer instead of two.
Identity, compliance & audit
Onboarding and verification flows, e-signature with tamper-evident proof, regulatory reporting under changing rules, and the RBAC and audit trails that still answer for a decision years later.
Evidence & operability
One trace per movement, audit logs that answer a compliance question from a single query, and the runbooks on-call teams rely on. Increasingly what DORA asks EU financial entities to demonstrate, not just have.
Working stack
C# / .NET
PostgreSQL
RabbitMQ
Redis
OpenTelemetry
Docker / AKS
Blazor
Selected Work
12 engagements across payments, identity and compliance, distributed services and reliability — clients anonymized where confidentiality requires. The shape of the work tends to be the same: money or operational state that has to move correctly across services, with auditability the user-facing teams can trust.
-
01 — Payments & settlement
Multi-PSP routing for an FX & CFD broker
One provider's outage no longer fails a deposit — an affected corridor falls back to another PSP on the same request, instead of returning the trader an error. Onboarding a new provider dropped from weeks to days.
-
02 — Identity, compliance & audit
End-to-end digital onboarding platform
Average onboarding time dropped from days to minutes for end customers. Full audit trails are available to compliance officers on demand.
-
03 — Distributed services
API gateway for a regulated B2B platform
Partner integration time dropped from weeks to days. Security policy is now enforced in one place rather than audited per service.
-
04 — Reliability & operability
Performance tuning of a trading platform's hot path
The endpoints that were breaching their tail-latency budgets now hold them through market open — and each budget is enforced per endpoint in CI, so a regression fails the build instead of reaching traders.
In the Open
One piece of work is not anonymized. Remit is an open-source reference money-movement backend — deposits and withdrawals through payment providers, a double-entry ledger, reconciliation — with every decision recorded as an ADR and a public sandbox you can drive from the browser without installing anything. It is the clearest available answer to “how do you actually build this?”
.NET 10
PostgreSQL
RabbitMQ
OpenTelemetry
AKS + Bicep
MIT
Contact
Open to architecture and delivery work, technical advisory, and contract engagements with fintech, regtech and platform teams. Engagements run either directly with me or through value.al, the software studio I run in Tirana. Email me, or put half an hour straight in my calendar — whichever suits.