Integrations Support Engineer [Remote | EMEA]

MoneyHash is building the future of API-based payment infrastructure. Our easy-install APIs consolidate the revenue cycle across geographies, functions, and use cases. We're saving our clients time and money, boosting product performance, unlocking new business opportunities, and reducing tech debt.

We're one of the fastest-growing payment infrastructure companies in emerging markets, and we know that building the right team is crucial to realizing our potential. At MoneyHash, we champion human empathy as well as work excellence. Join us and let's explore this journey together!

Integrations is where MoneyHash's core promise actually gets built. Every merchant who connects once and reaches dozens of providers is standing on a connection that somebody scoped, briefed, tested and shipped. We add providers and payment methods continuously across MENA and beyond (cards, KNET, Mada, STC Pay, Fawry, wallets, BNPL), and each one is its own small project with its own documentation, quirks, sandbox and failure modes.

You'll own that pipeline. Requests arrive from sales, customer success and merchants: a new provider, a new payment method on a provider we already support, or a new capability on a method that's already live. You work out what each one actually involves, write it down precisely enough that other people can build it, and carry it through to go-live.

You will not write code. You will read a great deal of API documentation.

• 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 docs don't answer.
• 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.

• 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)
• Write short. Much of this job is compressing a 200-page provider doc into a one-page brief somebody can build from without asking you five follow-up questions.
• Know the difference between authorize, capture, purchase, void and refund, what a webhook can and cannot be trusted for, and why tokenization and recurring are not the same thing
• Are organized under load, with several connections in flight at once, each waiting on a different person
• Have worked with external contractors or vendors and can hold them to a specification

• MENA/GCC payment methods and local acquiringn
• Payment orchestration, routing, or failover
• Error-code mapping, reconciliation, or QA of payment flows
• Linear, Notion, and writing for engineering audiences

Onboarding here is a designed program, not a stack of documents: structured sessions on how our platform and payments actually work, hands-on sandbox access from day one, and real connections to scope in your first weeks. By the end of it you'll be running the integration pipeline for real.

Beyond your functional responsibilities, everyone at MoneyHash plays a part in shaping our culture and values:

• Respect. We’re a global team and value diversity, empathy, and honest dialogue.
• Humility. We give and receive feedback with openness, leaving egos at the door.
• Flexibility. We adapt quickly, learn constantly, and step up where needed.
• Willingness to Learn. We embrace growth, celebrate iteration, and treat every mistake as a step forward.

Where we work: Remote-first across EMEA time zones, with an annual in-person retreat to bring the team together.

Competitive salary - stock options - health insurance - professional development stipend - wellness stipend - tech allowance - equipment financing program - annual in-person retreat - team engagement initiatives

Originally posted on Himalayas