Loading this job…
Orbitpay collects recurring payments for subscription businesses. That sounds simple until you look at the failure modes: a mandate that is valid at the bank but expired at the network, a webhook delivered twice, a retry that must never charge a customer a second time. Our Node services are where all of that is resolved.
You will work on the collections engine — the service that decides which mandates to present today, handles the response, schedules retries and produces the settlement file our merchants reconcile against.
Everything here is a correctness problem with money attached. Idempotency keys are not a design pattern we read about; they are the reason a merchant does not get an angry phone call. We take state machines seriously, we write tests for the ugly paths first, and we keep the code readable because someone will debug it at 2am under pressure.
Three to six years of Node in production, real comfort with async control flow and error propagation, and a database background strong enough that you reach for a transaction or a unique constraint before you reach for application-level locking.
Orbitpay is a small, profitable payments company. We give subscription businesses one API for recurring collections across UPI autopay, e-mandates and cards, then handle the retries, dunning and reconciliation that follow.
At our size everyone is close to the customer. Engineers join support calls, read the failure logs of real merchants and ship the fix the same day. There are no layers between having an idea and putting it in front of someone who pays us.
We work from a single office in Sector 62, Noida, four days a week.




Zentari Technologies🇮🇳 Bengaluru
Sarvam Learning🇮🇳 Remote (India)