Financial services / Employment contribution
Keep bank connections working behind the products that depend on them.
Backend engineering at Brankas on open banking integrations across Indonesia and the Philippines: bank API connections, performance work on legacy integration paths, and microservice design for fintech products.
- Project
- Open banking integrations
- My role
- Software engineer
- Scope
- Banking API connections, legacy path refactoring, and microservice design across fintech products
- Built with
- Go, gRPC, Kubernetes, PostgreSQL
- Period
- 2022–present · employment period
- Project status
- Ongoing employment
Engineering focus
Build and maintain bank connections
Banking API integrations across Indonesia and the Philippines, maintained as each bank’s interface and requirements change.
Refactor legacy paths for performance
Existing integration paths were reworked with performance as the goal, inside a fintech platform that stays in service while the work happens.
Design services across products
Go and gRPC microservices on Kubernetes with PostgreSQL, designed to be shared across several fintech products rather than rebuilt for each.
Work carried out by Jufianto Henri as an employee of Brankas, with its product and engineering teams. This is not a Sevtee client engagement. Partner banks, customers, internal systems, and metrics are confidential and are not disclosed; the diagram is a simplified overview.
Employment dates from Jufianto’s professional profile. This is the role period, not a project timeline. Current role. The case study describes the kind of work involved using public profile information only.
Integrations that other products stand on
Open banking products depend on connections to many banks, each with its own interface, rules, and failure behaviour. When a connection degrades, the products built on top of it feel it immediately. The engineering job is to keep those connections dependable while the banks, the regulations, and the products keep changing.
Since 2022 I have worked on that layer at Brankas, building and maintaining banking API integrations across Indonesia and the Philippines.
What the work involves
The day-to-day work combines three things. New bank connections are built against each bank’s API and brought into the shared platform. Existing integration paths are refactored, with performance as the goal, without taking the products that use them out of service. And the services themselves are designed as Go and gRPC microservices on Kubernetes, backed by PostgreSQL, so that several fintech products can share them.
This is team work inside an employer’s platform. My contribution is backend engineering within those teams, not ownership of the whole product.
Why it matters for a client project
Payment and banking integrations come up regularly in client work: connecting an application to a payment service, reconciling transactions, or handling an external API that behaves differently from its documentation. This experience is the background for the integration work Sevtee offers. Bank names, partner details, internal architecture, and performance figures are confidential and are not part of this case study.