You will own the integration surface between Studio998 and the acquiring banks, card schemes and local payment rails we route through. That means building and maintaining the adapters that turn a scheme-specific API into one internal payment model, and being the person who can explain why a particular corridor behaves the way it does.
The role sits in the engineering team, reports to the Chief Technology Officer, and works directly with client operations during onboarding and during incident review.
What you’ll do
- Build and maintain acquirer and rail adapters for card, ACH, SEPA, wire and local methods including PIX, UPI and PayNow.
- Design idempotent payment state transitions so that a retry, a timeout or a duplicate webhook can never charge a buyer twice.
- Own webhook signing, delivery and replay tooling for the full payment lifecycle, and keep the public API reference accurate.
- Reduce authorization decline rates through routing rule changes, each measured in the sandbox before it reaches production.
- Take part in a weekly on-call rotation for payment incidents, with a runbook behind every alert you could be paged for.
What we’re looking for
- Five or more years building production payment, billing or ledger systems that other people depended on.
- Working knowledge of card acquiring and authorization flows, or of an equivalent local bank rail in depth.
- Fluency in at least two of Python, Go, Node.js and PHP, plus SQL good enough to debug a reconciliation query unaided.
- Experience with PCI DSS scoping and tokenization, or a demonstrated ability to learn a control framework quickly.
- Written communication clear enough to explain a decline reason code to a client’s finance lead without jargon.