Payments and POS
Card terminals, refunds and voids, and keeping raw card data out of places it shouldn't be.
Xin chào, I'm Quyen Chau
Full-stack developer with 7+ years across Java and Kotlin backends, native and Flutter mobile, and NestJS microservices. Lately: POS terminals, card tokenization and real-time tour tracking for clients in the USA, Australia and Vietnam.
Four kinds of problems I keep coming back to, across seven years of client work.
Card terminals, refunds and voids, and keeping raw card data out of places it shouldn't be.
Live location, turn-by-turn navigation and chat that survive bad GPS and flaky networks.
Services that pass data between each other fast, for networks with thousands of devices.
Native and cross-platform apps shipped to Google Play and the App Store, then kept stable.
Since 2025 I've been running several products in parallel. Select a bar to jump to that project.
One company, many clients. Client and product names are described generically to respect confidentiality.
Everything here has been used in production, not just in a tutorial.
Things I build after hours, all open source on GitHub.
A Claude Code plugin that runs a virtual software team. A tech-lead agent routes each request through 12 specialist agents and 7 delivery pipelines, with resumable state.
A multiplayer 3D room for studying TOEIC together: shared desks with practice sets and Pomodoro, proximity voice and text chat, timed exams with leaderboards.
Chat rooms over WebSocket with a reactive Java Quarkus backend on MongoDB and a Flutter client in English and Vietnamese.