Kasper Lindqvist
Co-founder · Chief Technology Officer
Kasper owns the systems that may not lose money. Order-book state machines, key ceremonies, and the ledger path beneath them.
- Matching engine
- MPC wallets
- Settlement
About TrustChange
TrustChange is an EU engineering firm for digital assets and payments. We build exchanges, wallets, gateways and custody for teams under real supervision. Two skill sets rarely sit in one partner: deep crypto architecture and audit-grade delivery. Ours is built on both.
Since 2015
Card and payment work taught us the delivery discipline. Digital assets came next. One team has carried both ever since.
How we build the plumbing2015
Founded
Payments and card work first.
2018
Digital assets
Exchanges, wallets, gateways and custody.
Today
One practice
The same founders still sign the build.
38
Engineers
Senior, in-house, EU-based. No offshore subcontracting.
57
Systems live
Exchanges, wallets, gateways and custody in production.
6
Rulebooks
Built against the regime that will examine the product.
Partner-led
No rotating bench. The architecture is designed and signed off by a founder, and the same person is still there at the audit after go-live.
Co-founder · Chief Technology Officer
Kasper owns the systems that may not lose money. Order-book state machines, key ceremonies, and the ledger path beneath them.
Co-founder · Managing Partner
Ilze runs delivery for EMI, PSP and neobank platforms. She sets scope, team shape and the release discipline an auditor expects.
Co-founder · Head of Compliance Engineering
Tomáš turns a licensing file into shipped code. Controls, evidence trails, and the reports a supervisor actually opens.
Engagement models
Buy the practice the way it fits your quarter. Fixed scope, a dedicated team, or two senior people inside a team you already run.
How the work runs
Discovery, architecture, build, hardening, launch and support. One group carries all six. Nothing is handed to a third party mid-flight.
See the full service listWe map the product, the rulebook and the risk. You leave with an architecture you own.
A founder signs off the design. Threat model, data flows and key handling come first.
Small senior teams ship in two-week slices. Every slice is reviewed and testable.
Security review, load work and control evidence. We fix what the audit would find.
Handover to your team, then 24/7 cover. The code stays yours from day one.
Where we stand
We also do not cut compliance corners to hit a date. That answer costs us deals. It is still the answer.
Regimes we build against
| Regime | Where it shows up |
|---|---|
| MiCA | Licensing-ready architecture and records |
| PSD2 | Strong customer auth on payment flows |
| AML / Travel Rule | Screening, KYT and transfer data |
| PCI DSS | Card data scope kept small by design |
| SOC 2 | Change control and access evidence |
| GDPR | EU data handling and retention rules |
Readiness is engineered in, never retrofitted. See how we handle compliance.
Next step
Tell us the product, the deadline and the rulebook. A founder joins the first call. You get an honest read on scope and risk, not a pitch deck.
Prefer email? [email protected]