Principal Payments Engineer

Payabli is a next-generation Payments Infrastructure and Monetization Platform purpose-built for vertical software companies. Through a single, developer-friendly API with low-code embedded payment components, Payabli enables platforms to seamlessly embed, monetize, and operationalize payments—making payments a core part of their platform and business model. By unifying payment acceptance, payment issuance, and advanced payment operations tooling, Payabli empowers software companies to manage and move money through a single infrastructure stack that delivers total control over the payments experience. Built to scale with PCI DSS 4.0 and SOC 2-compliant security, Payabli’s infrastructure delivers enterprise-grade reliability and trust while leveraging AI-driven intelligence to enhance visibility, streamline operations, and drive revenue growth. Backed by leading fintech investors including QED Investors, Fika Ventures, TTV Capital, and Bling Capital, Payabli is setting the standard for embedded payments infrastructure powering the next generation of vertical SaaS. This Principal Payments Engineer is the founding hire for Payments Core - a dedicated team we're standing up to centralize the parts of the platform that cannot fail: the movement of money itself, from rails to batching/funding to reconciliation to ledgering, across hundreds of partners and hundreds of thousands of paypoints. This work happens today, distributed across the org and coupled to lower-blast-radius concerns. This role owns pulling it into one place, drawing a hard line around it, and holding it to the reliability and correctness standards money movement demands at scale. You'll be the most senior IC on the team and report to the CTO on an interim basis while we build out the org around you. The test for what belongs in this org is simple: does it stop the movement of funds? If yes, it's core, and it's yours to own. We're looking for a bar-raiser who's operated payments infrastructure at $10s to $100s of billions in GMV and knows what that scale actually breaks - someone who looks around corners, finds trouble before it finds us, and isn't afraid to challenge orthodoxy, including ours, when the evidence says we're wrong. This role rewards an entrepreneurial mindset: comfort with ambiguity, making calls with incomplete information, and taking ownership of outcomes rather than waiting to be told what to build. The choices you make early will be load-bearing for years, and you'll set the technical foundation both for the payments engineers we hire after you and for the engineers already working in these areas today.

Guarantee correctness at scale. Define how the platform guarantees a payment executes exactly once, even under partial failure, retries, and cross-service races - and make that guarantee a first-class, testable property of the system, not a convention people are trusted to follow. Set the API contract. Design the internal/external API surface partners and internal teams both build against - versioning, backward compatibility, webhook delivery guarantees - so there's no split between what we use internally and what partners get. Direct money-movement architecture. Set the direction for multi-rail orchestration (ACH, wire, RTP/FedNow, card networks) across multiple financial institutions, including direct connections to our sponsor banks and networks like Visa Direct, and how the platform routes, retries, and fails over rails and FIs. Own batching, funding, and reconciliation. These are the functions where a broken promise gets noticed fastest - partners feel it directly when funding is late or reconciliation doesn't match. Bring the same rigor here as anywhere else in the platform: accurate matching against external settlement data, fast exception handling, and no surprises. Build reliability and observability from day one. Establish the architecture-review and RFC standards, plus the monitoring and alerting, that let us catch