Integrations Support Engineer [Remote | EMEA]

Responsibilities

• Own the intake. Every connection request lands with you. Work out whether it's a new provider, a new method, or a capability extension, and check what we've already built before anything starts.
• Scope at the method level. A provider doesn't "support KWD". It supports KWD on KNET via redirection, with a specific set of operations and no tokenization. Read the provider's documentation and produce that matrix: integration types, currencies, schemes, operations, tokenization, 3DS, webhooks. Mark clearly what the…
• Find what's missing before engineering does. Which merchant requirements the provider genuinely cannot meet, which features the provider has to switch on for our account, what the sandbox won't let us test.
• Write the tickets. A self-contained build brief for the external developer, an engineering story with a QA checklist as its acceptance criteria, an error-code mapping table. Short, specific and correct. Our engineers have built dozens of connections and don't need the basics explained back to them.
• Manage the external developers. Brief them, keep them unblocked, review what comes back, and say no when it isn't right.
• Run the integrations backlog for a dedicated squad. Sequence the work, keep the pipeline moving, and tell the people waiting where their connection stands.
• Get it live. Credentials, testing data, QA, launch.
• You’ll Be Great for This Role If You
• Have hands-on experience scoping or delivering payment provider integrations. You've worked through a PSP's API documentation and turned it into something a team could build. This one isn't negotiable.
• Can read API documentation, JSON payloads and webhook specifications and state precisely what a provider does and does not support (you won't write code)

Languages