Enterprise Integration Engineer

Flutterwave was founded on the principle that every African must be able to participate and thrive in the global economy. To achieve this objective, we have built a trusted payment infrastructure that allows consumers and businesses (African and International) make and receive payments in a convenient border-less manner. We are recruiting to fill the position below:

Job Title: Enterprise Integration Engineer

Location: Lekki, Lagos About the role The Enterprise Integrations Engineer will deliver the technical onboarding of our Enterprise merchants: payment service providers, remittance companies and global brands. These are custom integrations, usually built directly on our APIs. You are the merchant’s technical lead from the kick-off call until their payments are stable. You own well-scoped projects yourself, and you work with a Senior Integration Engineer on the most complex ones. You work with Sales, Product, Engineering and Compliance to scope, test and launch each integration. Compared with SMB Integrations, you handle fewer merchants, but each one is larger, more custom and carries more risk. The role sits between Sales and Engineering, and it is a step on Flutterwave’s Integrations career path. At Flutterwave you help some of the world’s largest payment companies and brands reach customers across Africa, and you see your work become live payments within weeks. Responsibilities include but are not limited to Get merchants live: Run each integration from start to finish. You own the technical side of your merchants’ onboarding. The goal is to shorten the time from contract signed to first live transaction. The team target is a median of 24 days. Scope the work. Run technical kick-off calls. Check what the merchant wants to do against what our products can do. Recommend the right setup, for example a direct API integration or our hosted checkout, based on their market’s rules and their customers’ needs. Test before production. Check each integration in our test environment before the merchant gets live keys. This includes 3DS card payments (the extra card security step), mobile money payments (phone prompts and redirects), webhooks that are signature-checked and can safely arrive twice, and payments that stay pending before they get a final status. Clear the go-live checks. Build and testing start as soon as the contract is signed. Only live keys wait for two checks: business verification (Know Your Business, KYB) and a daily system check that the account setup and fees match the signed deal. When the system finds a difference, it posts it to the Jira ticket. You fix it, and the system clears it. Keep the record in Jira. Write on each ticket what you did, the next step and what is blocking it. Show who must act next: the merchant, Sales, Product, Compliance, a payment partner or you. Talk with merchants on Slack or email. Solve technical problems: Explain our APIs. Guide merchant developers on Flutterwave’s REST APIs, including card tokenisation, recurring payments and split payments. Find the cause of failures. Read API requests and responses and check logs in our internal log tools and Datadog. Tell a merchant-side error from a problem on our platform, and show the evidence. Keep merchants secure. Make sure merchants confirm each payment with a server-to-server call to our API, and do not trust the browser redirect alone. Work across teams and improve how we work: Raise blockers in Jira. Log each blocker and set who must act. If it is not cleared, the system alerts the right people on a set timetable, so you do not chase by hand. Support live incidents. When a live merchant has a problem, the ticket gets a severity (P1 to P4) and Customer Reliability Engineering owns it. You give them the evidence. Improve payment success. Track success rates for each payment rail your merchants use. Work with the Global Expansion and Payment Partnerships team, who own problems caused by payment partners. Hand over cleanly. You own the merchant from the first live transaction until the system marks them stable. Then you hand over to their Technical Account Manager with a complete Jira record. Fix gaps in our docs. When the documentation is missing or wrong, send the details to the Developer Experience team, who own the docs. How we measure success We measure most of your results from system data in Jira and our payment records. Merchants live and transacting. This matters most. Our payment records show the first live transaction, and the system then marks the merchant live. Time to live. The days from contract signed to first live transaction. This is a shared team result. We look at a typical case (the median) and a slow case (the 85th percentile, which 85 in 100 projects beat). Your own share counts only the days when the ticket waits on Enterprise Integrations. Days spent waiting on the merchant, Sales or Product do not count against you. Payment success rate. The share of payment value that succeeds for your merchants in their first weeks live. We count only failures caused by the integration. Clear ticket notes. Every ticket shows what happened, the next step and any blocker. This is the basic standard for the role. Required competencies to be a Waver Minimum of a Bachelor’s Degree from an accredited university. 4-9 years of relevant experience in Integration Engineering, Implementation Engineering, etc You can read and debug REST API requests and responses in JSON. You can use Postman to send test requests and find errors. You can read code in JavaScript, Python or PHP. You can run several high-value projects at once, keep to timelines and hold people to their commitments, using Jira or a similar tool. You write and speak clearly. You can explain a complex technical limit to a non-technical person, including a merchant’s