Product Manager, Payments

OpenFX is on a mission to move money as freely as data, unrestricted by time zones, banking hours, or legacy systems. We are building the infrastructure that will power the next generation of cross-border payment systems for institutions. Our early team includes operators from J.P. Morgan, Goldman Sachs, FalconX, PayPal, Affirm, Polygon, Kraken, Nium and more. We’re backed by Accel, Lightspeed, NFX, and other top-tier investors.

OpenFX can already move money cross-border. But without a world-class collections (Pay-In) layer, we’re missing the front door of the funds flow. Building this unlocks a new category of clients (global platforms, marketplaces, remitters, enterprises) and makes OpenFX materially stickier: once customers collect through us, their entire flow runs on our rails.

Most global businesses still collect money like it’s 2008: opening local bank accounts country-by-country, reconciling fragmented bank statements, and wiring funds back to HQ with delays, hidden fees, and constant operational breakage. If you have hundreds of thousands of customers across countries, “collections” becomes a full-time organisation, just to get paid and understand who paid you.

You'll be the directly responsible individual for the Pay-Ins charter, from strategy through execution. Ownership isn't about shipping features, it's about delivering outcomes. This means:

1. Enable customers to collect money in their local markets without opening local bank accounts.
2. Launch Pay-In collections through virtual accounts infrastructure on key fiat rails. e.g., ACH/Wire (USD), SEPA (EUR), SPEI (MXN), etc. and then expand.
3. Define what “live” means: onboarding, limits, payment references, exceptions, refunds/returns, SLAs, and support playbooks.
   
   

1. Allow customers to programmatically route collected funds to any destination with zero manual intervention.
2. Design and build infrastructure that will be used by clients to decide  how funds received into virtual accounts can be converted and routed:
• fiat → stablecoin → on-chain wallet, and/or
• stablecoin → fiat rails for payouts
3. Own the product decisions and the integration path with the underlying virtual account + on/off-ramp infrastructure.
   
   

1. Build end-to-end observability for customers: who paid, when, in what currency, what fee/FX was applied, and where it settled.
2. Ship reconciliation primitives: payment references, statement mapping, webhooks, reporting exports, and exception workflows.

12 months in, you’ll know you’re succeeding if:

• $5B+/month Pay-In volume processed across local rails (with a clear path to $20B/month next quarter).
• 6+ pay-in rails live and operational (e.g., ACH, Wire, SEPA, SPEI + 2 more), each with defined SLAs, monitoring, and incident playbooks.
• p95 latency <10 minutes for automated flows (fiat received → virtual account credited → routed to destination)
• 8–10 enterprise customers live, with 3+ doing >$1B+/month in collections through OpenFX infrastructure. 
• Onboarding time < 14 days for a standard Pay-In integration (from kickoff to first money collected), measured and improving.
• Auto-reconciliation rate ≥ 95% (payments matched without manual ops), with clear exception workflows for the remaining cases.

• You'll conduct 15-20 deep discovery sessions with clients/prospects (marketplaces, enterprises, remitters, payment processors). 
• You'll map the current state: how they collect, reconcile, repatriate funds, and where it breaks. Then you'll let the data, not the loudest voice, decide which rails and geographies to prioritize.
• You choose v1 rails based on demand, feasibility, and unit economics and you can defend that choice with numbers.

• Write a clear PRD and One Pager that articulates the Job to Be Done, Desired Outcomes, and SMART success metrics. Publish Pay-In API + workflow spec (payment references, webhooks, reconciliation model, exceptions)
• Define the fiat→stablecoin routing policy and the customer configuration surface.
• Bring Legal, Compliance, Ops, and Partnerships into the room during definition, and solve constraints before engineering starts coding.

• Rail #1 in development with an integration test plan and a launch readiness checklist.
• Ensure Ops is trained, FAQs are written, and support playbooks are documented before go-live.
• First lighthouse customer committed to a timeline (integration + go-live criteria).
• Weekly metrics review cadence established (latency, failure modes, reconciliation breaks, support volume).
• Begin expansion to Rails #2 and #3 based on customer feedback and pipeline demand.

• You’ve shipped payments products (API-first) where reliability, exceptions, and reconciliation matter.
• You write crisp, technically grounded specs and can drive hard tradeoffs across product/engineering/ops/compliance.
• You've been the DRI for a product line, owning adoption, volume, reliability, and unit economics, not just roadmaps. You measure success by data, write post-mortems when hypotheses fail, and iterate rapidly.
• You know how to uncover real customer pain. You ask, "Show me how you currently reconcile these payments", instead of "Would you use this feature?" You distinguish between what customers say they want and what their behavior reveals they actually need.

• Experience with local payment rails (ACH, Wire, SEPA, SPEI, Pix, FPS, NEFT/UPI etc.) and bank/payment partner integrations.
• Exposure to virtual accounts, treasury/ledgering, or reconciliation-heavy products.
• Familiarity with stablecoin rails/on-off ramps (helpful, not required).

• MBA, pedigree, or a certain number of years. We care what you’ve built and owned.

• Speed: OpenFX went from $0 to $40B+ in annualized volume in under two years. We don’t do “multi-quarter discovery.” If the opportunity is real, we ship. You’ll take Pay-Ins from charter to production fast, and you’ll feel the impact in weeks, not years.
• Access: You’ll work directly with leadership and the teams that matter: clients, partnerships, compliance, ops, and engineering. You’ll sit in enterprise discovery calls, negotiate rails/partner constraints, and get lighthouse customers live yourself. No layers. No politics.
• Leverage: Pay-Ins is the front door of the money flow. If we win here, customers don’t just move money with OpenFX. They collect through us, reconcile through us, and then route funds globally through our rails. This turns OpenFX from “a provider” into the default operating system for global collections and treasury.
• Upside: Early equity in a company scaling faster than most fintechs in the category. If we win, you’ll have built a product line that becomes foundational to how global businesses get paid. If we lose, you’ll still have shipped infrastructure that moved billions - across rails, currencies, and compliance regimes.

If you want to build the collections layer that makes global money movement actually work, at scale, apply.