Payments Systems Manager

Our client, a high-growth consumer subscription company, is hiring a Payments Product Manager to own their payments platform end to end. This is not a greenfield build. You inherit a modern stack — a first-party payments microservice, a payment orchestration layer routing across processors, BNPL, automated dunning, and a self-serve analytics layer — plus a dedicated engineering scrum team. Your job is to push it forward. Two priorities define the first six months. First, rebill recovery: a meaningful share of subscription rebills fail, and too many of those customers churn for payment reasons, not product reasons. You'll audit the dunning stack, evaluate vendors, and decide whether to optimize, switch, or layer. Second, initial auth rate: routing optimization, network tokenization, express checkout, and continuous experimentation at the checkout layer. In a given week you'll write a spec, pull your own numbers out of the data warehouse, negotiate a vendor SLA, and present findings to the CFO. There is no payments ops team behind you. When something breaks, you drive resolution. You set the roadmap, you ship, you measure.