Brankas is an open finance platform in Southeast Asia. Direct is its account-to-account payment product. Instead of routing a payment through a card network, the customer pays straight from their bank account.
Brankas sits in the middle of that. It integrates with banks directly, including BPI in the Philippines, and gives merchants one checkout interface and one contract. A merchant does not build and maintain a separate integration per bank. That aggregation is the product.
What I do here
Architecture redesign
Restructured the Go service layer around SOLID boundaries and an enforced repository structure, chosen over incremental patching because bank-integration logic was being re-implemented inconsistently for every provider.
Event-driven decoupling
Moved work off the synchronous payment path with a NATS JetStream publish and subscribe pattern, so a slow or failing downstream step does not hold a payment request open.
Design-first contracts
Architecture diagrams and OpenAPI specifications before implementation, so banks and business customers have something stable to build against and internal teams agree on the boundary before code exists.
Technical leadership
Sprint planning, release management, scoping directly with product managers and enterprise customers, code review standards, mentoring.
Reliability on the payment path
Prometheus, Grafana, and InfluxDB observability, Kubernetes HPA autoscaling, graceful shutdown with connection draining, so deploys and scale events do not drop in-flight payments.
Go · NATS JetStream · gRPC · Protocol Buffers · PostgreSQL · Kubernetes · GCP · Prometheus · OpenAPI