Payments Strategy & Roadmap
–Own the direction: Define the multi-year Payments strategy and rolling roadmap across UK and US requirements; decide what to build, defer, simplify, reuse, or deprecate.
–Own the scheme calendar: Productize non-discretionary change — Nacha rules, ISO 20022 deadlines, scheme mandates — before it becomes urgent.
–Keep the roadmap on track and define success: STP, success and return rates, latency, availability, reconciliation breaks, onboarding lead time, adoption.
Payments Domain & Client Leadership
–Be the SME: Serve as the internal product authority on how rails, schemes, participants, processors, settlement models, and operating rules work end to end.
–Problem-solve with clients: Join client working sessions to define what to build — whiteboard the actual payment lifecycle, expose missing controls and edge cases, and identify the minimum viable reusable capability.
–Guard the platform: Convert recurring client and field signal into reusable payment primitives, not client-specific forks; countersign any client commitment that binds the roadmap before it is promised.
–Challenge constructively: Push back on clients and internal experts with evidence; document decisions so they stay made.
Technical Product Definition
–Write the contract: Author PRDs and decision documents; define payment APIs, events, data and state models, error semantics, and acceptance criteria.
–Sweat the semantics: Partner with engineering on idempotency, duplicate handling, retries, ordering, cut-offs and value dates, settlement finality, and recovery.
–Own the boundaries: Define product contracts with Ledger, Customer, Reg & Compliance, Orchestration, Reconciliation, Data, and Command Center.
–Respect the split: This role owns what, why, priority, and acceptance criteria; engineering owns architecture, implementation, and estimates.