Galih
Priyambodho

My first IT job, back in 2014, was tech support at Berca: sitting with clients, learning the tools, and one long project upgrading the work PCs at a bank office — where success meant staff sitting down the next morning and noticing nothing except the speed. Then a computer science degree at the University of Indonesia, and in 2018 a college friend pulled me into Arranet. Day one I was dropped into a live PPOB payment app on ASP.NET, Bukopinet. Every new product — university tuition, prepaid and postpaid telco — was mine to add, the frontend and the logic behind it.

Nearly everything I've built since follows one pipeline: a supplier's product (PLN, telco, e-money) enters Octopus, Arranet's switching core, passes through a product interface, and comes out in an app people actually pay with. I took Bukopinet to mobile with Xamarin — the API and the app — plus the admin dashboard and the partner management web around it. Then Arranet sent me to Bali to learn how closed-loop payment apps get made, and months later that became PayAja: a Gopay-style wallet for community networks, from nature schools to pesantren to cooperatives. I signed up to build the API; the dashboard developer quit, so I built that too. When it needed to talk to MiniATM devices, PayAja Bisnis was born, and that later grew into BayarBayar. To this day, if anything breaks in either, it lands on my desk.

Right now the big work is a re-platform: taking our Windows-era .NET Framework services — Octopus included — to .NET Core so they can run on Linux in Docker. Honest confession: I love greenfield builds like PayAja, and I dread onboarding a supplier with a huge catalog, because every product and every fee config still has to be added to Octopus one by one. Off the clock it's coffee and a French press. If you need an engineer who knows payments from the switching core out to the device, the contact page is short.