Backend Engineer · Financial Systems · Java Ecosystem
Building distributed, compliant systems for financial environments — from legacy fiscal engines to cloud-native Open Finance APIs.
My background spans enterprise Java at a Brazilian ERP/fiscal software company and greenfield microservices targeting financial regulation compliance. I'm drawn to problems where correctness is non-negotiable: payment reconciliation, identity federation, API security, and distributed system reliability under financial-grade constraints.
| Project | What it does | Stack |
|---|---|---|
| open-finance | FAPI 1.0 API Gateway with mTLS, certificate-bound tokens (RFC 8705), JTI anti-replay, consent lifecycle management and CNAB240/CIP banking reconciliation engine | Java 21 · Spring Cloud Gateway · Spring Cloud Config · Spring Batch · Redis · Kafka · Docker · Maven |
| Biked | IoT system that turns a spinning bike into smart connected equipment | ESP32 · MQTT · Spring Boot · RabbitMQ |
| FlightIssues | Micro SaaS — generates EC 261/2004 flight compensation claim letters; structured passenger input → regulation-compliant PDF artifact, one-time payment | React · Supabase · Stripe · React PDF |
Open Finance Brasil — FAPI 1.0 Compliance [open-finance]
- API Gateway with ordered filter chain: mTLS validation → JTI anti-replay → consent authorization → rate limiting
- Certificate-bound access tokens per RFC 8705 (
cnf.x5t#S256thumbprint binding) - JTI replay prevention via Redis atomic
SETNXwith TTL anchored to JWT lifetime (fail-closed on Redis unavailability) - CNAB240/CIP reconciliation engine with Spring Batch
- Reactive pipeline (Project Reactor) with security-safe error boundaries
Brazilian Fiscal Systems — PHD Sistemas
- NF-e, CT-e and NFS-e generation, signing and transmission
- PL/SQL stored procedures for fiscal calculation engines on Oracle DB
- JWT security library across interconnected Java monoliths (RS256, JWKS endpoint, servlet filters, SOAP handlers)
The more we automate, the more human we must become — Ginni Rometty



