Product Manager, Payments

OpenFX

About The Position

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. The Problem You’ll Solve 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 build the product that fixes this. By owning Pay-Ins end-to-end, from local fiat rails and virtual accounts to fiat→stablecoin routing, to reconciliation that finance teams can close books with, you'll unlock a new category of customers (global platforms, marketplaces, remitters, enterprises) and make OpenFX the default operating system for their global treasury.

Requirements

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.

Nice To Haves

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).

Responsibilities

Launch Pay-In v1 across priority rails
Enable customers to collect money in their local markets without opening local bank accounts.
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.
Define what “live” means: onboarding, limits, payment references, exceptions, refunds/returns, SLAs, and support playbooks.
Allow customers to programmatically route collected funds to any destination with zero manual intervention.
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
Own the product decisions and the integration path with the underlying virtual account + on/off-ramp infrastructure.
Build end-to-end observability for customers: who paid, when, in what currency, what fee/FX was applied, and where it settled.
Ship reconciliation primitives: payment references, statement mapping, webhooks, reporting exports, and exception workflows.