A full-time, on-site Lead Payment Gateway Integration Engineer position is open at a software company in Technopark, Kazhakkoottam, Thiruvananthapuram. The role pays up to ₹1,54,000 a month.
The work itself
The team builds and maintains the code that connects the company's products to payment providers, so much of the job is writing and updating integration code that has to behave correctly even when a provider's API changes with little warning. You'd also work across teams regularly, since payment flows touch product, finance, and support whenever something goes wrong.
- Write and maintain application code for payment gateway integrations and related services
- Work with product, QA, and finance teams to ship new payment features without breaking existing flows
- Fix bugs surfaced during testing, including edge cases specific to payment processing
- Review integration points against PCI-DSS requirements before anything goes live
A case that came up recently: a payment provider started retrying webhook deliveries slightly faster than before after an update on their end, and the system briefly logged a handful of transactions as duplicates before the idempotency check caught up. Untangling that meant reading through webhook timestamps line by line to confirm no customer had actually been double-charged, then adjusting the retry-handling logic so the same timing shift wouldn't cause a scare again. That kind of detail-heavy troubleshooting is fairly typical of what a lead spends time on here.
Standups happen daily, but the more useful conversations tend to be the ad hoc ones, someone flagging a settlement mismatch or a provider's changelog entry that might affect an existing integration. A lead is usually the first person those conversations land on, since spotting which changes matter and which don't takes familiarity with the codebase that newer engineers haven't built up yet.
Skills required
Hands-on experience with payment APIs is non-negotiable for this seat, along with solid REST API design and consumption skills, since most of the integration work happens over REST. Security compliance knowledge, specifically PCI-DSS, matters just as much as the coding itself. A lead who writes clean integration code but doesn't think about compliance implications will create problems for the whole team later.
- Practical experience integrating payment gateway APIs
- Strong REST API design, consumption, and debugging skills
- Working knowledge of PCI-DSS and general payment security compliance practices
Beyond that baseline, experience with webhook-based event systems, idempotency handling, or prior work on reconciliation logic will make an application stand out. Exposure to a specific payment provider's SDK, whether that's a major international gateway or a regional one common in India, is a plus, not a requirement. Comfort reading a provider's API changelog and judging what needs a code change versus what's just documentation noise is a skill that develops with time, and this role leans on it often.
Pay and what's included
The role pays up to ₹1,54,000 monthly, competitive for payment gateway integration engineer jobs in Thiruvananthapuram at the lead level given the compliance responsibility attached to it.
- Health insurance
- Paid time off
- Performance-linked bonuses tied to delivery and reliability metrics
- Relocation assistance for candidates moving to Thiruvananthapuram
- Accommodation support during the initial move
Education and experience
A four-year degree is the standard requirement, with computer science or information technology as the expected background, though the company doesn't rule out adjacent fields if practical experience is strong enough. On the experience side, the listing calls for 144 months in relevant technical roles, which puts a realistic candidate well over a decade into their career and almost certainly with prior exposure to financial or transactional systems specifically, not just general backend work.
Naukri Mitra notes that payment integration roles at this seniority tend to draw from a narrower pool than general software development listings, since the compliance layer filters out candidates who've only worked on non-regulated products.
None of this means the ideal candidate has spent their whole career purely in payments. Someone who spent a few years on a general backend team and then moved into a fintech product for the last several years often has exactly the right mix, practical range plus depth where it counts.
Team and pace
The team is small enough that a lead here touches most of the payment codebase personally rather than owning one narrow slice of it. Release cycles for anything touching payment flows go through an extra review step beyond normal code review, given how expensive a mistake in this area can be for both the company and its customers. That adds friction some engineers find frustrating, though most people who've worked in payments before expect it and plan their time around it rather than fighting it.
Location
The office sits inside Technopark in Kazhakkoottam, and the role is on-site, not remote or hybrid. Anyone searching broadly for payment gateway integration engineer jobs near me should consider whether relocating to Thiruvananthapuram works for their situation, since this listing has no remote option.
Applying
Submit a resume that specifies which payment providers or gateways you've integrated with directly, along with any compliance-related work you've done. The interview process typically includes a technical round covering REST API design and payment-specific edge cases, followed by a scenario-based discussion about handling a security or compliance issue under time pressure. This listing is one of several payment gateway integration engineer jobs for experienced professionals in Thiruvananthapuram currently open, and candidates with direct PCI-DSS exposure tend to move through the process faster than those without it.
Scenario discussions, in particular, are worth preparing for beyond a general sense of best practices. Interviewers tend to ask for specifics: how you'd verify whether a suspicious transaction pattern was a genuine issue or a false alarm, and what you'd change afterward so the same ambiguity doesn't cost as much time next time.
