System Analyst (Payment Gate) - Remote

About the Role:

You'll help the Payment Gate team ship new payment features faster and with higher quality, working across a real-time platform that processes thousands of financial transactions daily.

What You'll Do:

• Work within the Payment Gate team, responsible for the payment hub and payment-gate — core infrastructure that processes thousands of real-time transactions
• Translate business and technical requirements into clear system specifications, integration plans, data models, and process diagrams that development teams can build from
• Bridge product, engineering, and operations to define how payment solutions are designed, integrated, tested, and released

What You'll Own:

• Design and configure system solutions on the Payment Gate platform, from requirements analysis through to integration planning and go-live support
• Create and maintain detailed documentation: functional specifications, data models, sequence diagrams, and BPMN process flows
• Define integration requirements and manage data mapping between Payment Gate and connected systems, including core banking, CRM, and third-party payment APIs
• Run system testing, troubleshoot issues, and work directly with developers to resolve problems before and after release
• Identify workflow gaps and propose improvements to how payment features are built, validated, and deployed
• Conduct user training and provide ongoing support to teams working with Payment Gate systems

What Makes You a Strong Fit:

• 3+ years as a System Analyst or in a closely related role, with experience in payment systems or financial platforms
• Strong understanding of system architecture, API integrations, and enterprise application integration (e.g., core banking, CRM, third-party APIs)
• Proficient in BPMN notation; able to produce clear sequence diagrams, data flow models, and functional specifications
• Hands-on experience with data mapping, API integration workflows, and integration testing
• Able to write documentation that is precise enough for developers and clear enough for non-technical stakeholders
• Comfortable working with distributed, cross-functional teams across different time zones