Stash - Product Manager, Payments
Requirements
• High agency and ownership — you're comfortable being the first dedicated payments PM, building structure from scratch, and being the final call on payments decisions • An MVP, incremental-build mindset — you scope down, ship iteratively, and push back on scope creep • Tight project management execution — you run a disciplined roadmap and hold timelines and commitments without slippage • Payments/processing domain expertise — solid working knowledge of multiprocessor routing and a feel for where and why transactions fail • Data and experimentation rigor — you instrument payment funnels, run holdback/A-B tests on routing and retry logic, and let approval-rate data (not opinion) drive prioritization • A generalization instinct — you turn partner-specific payment failures into systemic product fixes • Clear communication — specs, roadmap updates that land with engineering, sales, and leadership • Background at a tech/SaaS or payments/fintech company, with direct, hands-on ownership of a payments/processing surface • Direct, hands-on experience collaborating with engineering teams • Comfortable overlap West Coast hours given where our product and payments strategy is concentrated
Responsibilities
• Act as the translation layer between payments operations, compliance, and the engineering team — turning operational needs and business risk into clear, prioritized requirements engineers can build against • Own and maintain the company-wide payments roadmap: translate business priorities into an effort-estimated, impact-sized backlog, and be the single accountable owner of sprint planning and prioritization for the payments eng team • Define and own authorization/approval rate, payment success rate, false decline rate, and cost-per-transaction as core business KPIs; turn the gap against industry benchmarks (healthy e-commerce card-not-present authorization rates typically run 85–95%, with 90%+ considered well-optimized) into a prioritized set of requirements for engineering • Build the business case and scoped requirements for multiprocessor/acquirer routing and failover, so engineering can build smart routing that keeps a single processor outage or high-decline processor from materially denting revenue • Prioritize and scope retry and recovery logic improvements with engineering, weighing recovered revenue against fraud exposure • Own the fraud-vs-conversion tradeoff as a business decision: set the target for reducing false declines and the acceptable chargeback/dispute threshold, then translate that into prioritized engineering work • Translate Merchant-of-Record obligations (tax compliance, disputes/chargebacks, regional payment compliance) into product requirements the engineering team can plan and ship against • In your first 90 days: learn our PSP/acquirer integrations, routing logic, retry/recovery, fraud rules, and MoR/tax stack well enough to translate operational needs into scoped, prioritized engineering requirements — not to become a payments engineer yourself; establish baseline metrics and identify the top 3 sources of failed or declined transactions; take over sprint planning for the payments eng team; and ship one meaningful, metrics-backed improvement to approval rate or payment success rate
Benefits
• Work on products used by some of the world's leading game studios • Own a core product area with significant autonomy and impact • Help shape the future of direct-to-consumer commerce in gaming
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT