Payment Integrations & Technical QA Manager

Responsibilities

• Running the full onboarding cycle for new payment providers: first technical call, credentials and sandbox access, configuration, test design, UAT, production launch and post‑release stabilisation
• Owning first‑line response for payment incidents, including failed and stuck transactions, unconfirmed payments and method‑level anomalies, and driving them to resolution rather than passing them on
• Defining the acceptance standard for new integrations and holding the go or no‑go decision before launch
• Reading provider API documentation and turning it into implementation‑ready specifications for engineering, including edge cases, failure paths and confirmation model behaviour
• Running hands‑on verification: manual checkout testing on mobile and desktop, callback verification through Postman, and SQL queries against transaction data
• Maintaining the catalogue of payment methods and providers: what each supports, which integration types are available, what has been tested and where known failure modes sit
• Building the first capability inventory of all live methods and providers
• Later, producing a 90‑day breakdown of deposit attempts by outcome: completed, declined by the provider, abandoned by the user, abandoned at redirect, and completed but never confirmed back to us

What you'll need

• 4+ years in payments, PSP integrations or fintech platforms, with hands‑on ownership of integrations rather than tracking them, basic knowledge using AI tooling in daily work
• Working knowledge of APIs, webhooks and asynchronous payment status, plus an understanding of confirmation models, callback mechanics, redirect flows and common failure modes
• The ability to read a provider API specification and identify what is missing from it
• Postman or equivalent for API testing, and structured checkout testing across mobile and desktop
• Experience diagnosing a live payment incident from logs and API responses, separating provider‑side causes from platform‑side causes, and explaining the finding to both a provider contact and an engineer
• The ability to turn ambiguous provider documentation and undocumented knowledge into specifications and catalogues that engineering can act on
• Composure during incidents, and clear communication with the team and stakeholders
• English and Russian at working level. Both are in daily use

Will be a significant plus

• Experience with APM and local rails in Asia, Africa or LATAM rather than cards alone
• Experience with bank transfer rails, virtual accounts, QR‑based methods, mobile money etc.
• Background in brokerage, crypto payments, orchestration or another high‑volume payments environment; on the provider side, at a 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

What the first year looks like

• In the first months you take over incident first line, build the method and provider catalogue from documentation, existing knowledge and direct querying, and produce the deposit attempt analysis.
• By mid‑year you have defined the integration acceptance standard and applied it to a live provider onboarding from start to production.
• In the second half the catalogue is current, the gate is running, and incidents reach you for decisions rather than for explanations. As the team grows, a Systems Analyst takes over formal verification while the acceptance gate stays with you.

Recruitment process

• HR interview, covering background, motivation and fit
• Technical interview on payment integration knowledge, tooling and hands‑on experience, including incident diagnosis
• Product and problem‑solving interview, covering integration decisions and prioritisation
• Final interview with senior stakeholders

We offer

• Fixed monthly compensation of [depending on experience]
• Fully remote work within GMT to GMT+4, with no relocation required
• End‑to‑end ownership of a provider from first call to production, and the go or no‑go decision on every integration
• Scope that grows with the business: cards, alternative payment methods, a card programme and new entities
• Corporate AI tooling as part of the working process