Senior Backend Engineer-Payments

We are an international broker. Our clients fund and withdraw through roughly 60 payment methods across Asia, Africa, LATAM and the Middle East.

Payments is now a standalone function, and we are building the team around it.

We are looking for a Senior Backend Engineer who will own our connector layer and everything downstream of it: building a canonical adapter layer so that providers plug in rather than get built one by one, moving payment methods to server-to-server and embedded flows, and making transaction status reliable and observable across the estate.

You will also be the payments function's technical counterpart to the orchestration platform team: the behaviour we need from the platform is specified here, argued here and reviewed here.

Your responsibilities will be:

• Building and owning the connector and adapter layer, so that adding or replacing a provider becomes configuration and a thin adapter rather than a new integration each time
• Migrating payment methods from redirect flows to server-to-server and embedded flows where the provider supports it, and measuring the result
• Owning everything downstream of the orchestration layer: reconciliation, transaction status handling on our side, method configuration and payment flows into the client portal
• Making transaction status reliable end to end, through active status polling, idempotent processing and reconciliation
• Building observability over transaction status and provider performance across the estate
• Specifying the behaviour we need from the orchestration platform: transaction state machine, idempotency, polling, routing and cascading rules. You design it, argue for it and review what comes back
• Supporting integration work for our card programme
• Extending the same integration set to acquired entities as configuration rather than a new build each time

• 5+ years in backend engineering, strong in TypeScript, Node.js, comfortable in relational databases
• Production experience with payment systems: authorisation, callbacks, refunds, reconciliation and retry behaviour
• Practical understanding of idempotency, asynchronous status handling, transaction state machines and designing for partial failure. This is the core of the role rather than a detail, and you will both build against it and specify it
• Experience integrating third-party APIs of uneven quality, including working directly with a provider's integration team to resolve what the documentation does not answer
• The ability to own a service rather than close tickets: architecture decisions, standards and root cause fixes
• English and Russian at a working communicative level