Senior Backend Engineer-Payments

CXM Group is an international group of companies established in 2015 to provide reliable trading solutions within the global forex industry. Our team of experts has decades of experience across the Asia Pacific, US, and European markets, and has delivered multi-award-winning services for traders of all levels. With a focus on B2B and institutional customers, we have expanded to provide retail traders with cutting-edge technology tools and account types. Our offering includes SWAP-free trading for all clients, unlimited leverage, competitive spreads, deep liquidity pools, and strong relationships with tier-one banks and prime brokers. Our goal is to provide our customers with the optimal trading experience, regardless of their experience level.

• 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
• Experience integrating third-party APIs of uneven quality, including working directly with a provider's integration team to resolve documentation gaps
• Ability to own a service rather than just close tickets: architecture decisions, standards and root cause fixes
• English and Russian at a working communicative level

Nice to have:

• Exposure to .NET for work touching the client portal
• Experience with APM and local payment rails in Asia, Africa or LATAM besides cards
• Experience with bank transfer rails, virtual accounts, QR-based methods, mobile money etc.
• Experience with event-driven patterns in production: transactional outbox, idempotent consumers, sagas
• Background in brokerage, crypto payments, orchestration or high-volume payments environment; on the provider side, PSP, gateway or payment company
• Active use of AI tooling in daily work
• Ability to work independently and make decisions without constant oversight
• Proactive mindset: willingness to propose improvements, fixes, new approaches

• 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; designing, arguing for, and reviewing it
• Supporting integration work for the card programme
• Extending the same integration set to acquired entities as configuration rather than a new build each time