Digital Banking Integrations

Insurance partner integrations and in-house SFTP file exchange for a digital bank.

5 partners
Insurance partners integrated; operational errors reduced by about 30%
~30%
Throughput increase after moving flows to Kafka and Redis
99%
In-house SFTP uptime, with about 1,000 transfers per month

Role: Software Engineer
Period: Jun 2024 to Dec 2025
Client: Jenius (SMBC Indonesia)
Project type: Key project
Room in the 3D HQ: L3:digital-banking-integrations

Situation

Jenius offers partner insurance products inside its banking app, and each partner used different APIs and file formats. Policy workflows still needed manual steps, and partner file exchange relied on a licensed commercial transfer product. As a Software Engineer, I integrated five insurance partners through a consistent microservices layer.

Role and key decisions

Integrated five insurance partners through one consistent microservices layer
Why: Each partner used different APIs and file formats, so the integrations went through one consistent microservices layer built with Express.js and Spring Boot.
Replaced a licensed transfer product with an in-house SFTP service
Why: Scheduled partner file exchange could run in-house instead of on a licensed product; the MFT/SFTP service held 99% uptime with about 1,000 transfers per month.
Set full unit-test coverage as the team standard
Why: New and refactored modules shipped with full Mocha, Chai and Sinon coverage plus k6 load tests, and production issues fell by about 30%.

Results

5 partners
Insurance partners integrated; operational errors reduced by about 30%
~30%
Throughput increase after moving flows to Kafka and Redis
99%
In-house SFTP uptime, with about 1,000 transfers per month
-30%
Reduction in production issues after adopting full unit-test coverage