Payment Operations Associate

Work to Be Done
Instead of a list of requirements, we want to give you a directional look into the first 30, 90, and 180 days on the job.

We are a startup, so the pace is fast and the specific work will change. People who thrive here are finding ways to contribute in their first week, and fully productive in their third month.

If you think this is something you can handle, we will be excited to speak with you.

First 30 days: Contribute from week one
Run daily reconciliation of crypto and fiat across banks, PFIs, liquidity providers, and exchanges, and start clearing breaks yourself.

Monitor live payment flows across on/off-ramp and payment rails, and flag stalled or failed transactions as you learn the systems.

Pick up your first exceptions—returns, rejects, recalls—and drive them to resolution.

Map how current reconciliation and monitoring workflows actually run, and name one thing worth fixing.

Outcomes

Owning daily reconciliation for at least one partner or rail with minimal support.

A short written read on the biggest gap you've found in current tooling or process.

By 90 days: Own your domain
Own daily reconciliation and exception handling across your assigned rails and partners end to end.

Serve as an escalation point for payment issues, settlement delays, and failed conversions, partnering with Customer Support to close them out.

Coordinate with Treasury on operating balances, prefunding, rebalancing, and settlement timing.

Ship improvements to reconciliation systems, dashboards, and reporting, and track KPIs like throughput, settlement latency, and exception rates.

Build or rewrite SOPs and runbooks for the workflows you own.

Outcomes

Full independent ownership of reconciliation and exceptions for your rails.

At least one manual workflow measurably reduced through automation or an AI-enabled process.

By 180 days: Scale the function
Cut manual work across the operation through automation and AI-enabled workflows, scaling through better systems rather than headcount.

Partner with Product and GTM to launch new rails, partners, and corridors: define acceptance criteria, support end-to-end testing, and validate settlement and reconciliation before go-live.

Support product readiness and QA by turning Payment Operations requirements into clear specs and testing new functionality before launch.

Build monitoring and alerting that catches problems before they reach customers.

Outcomes

A repeatable playbook for bringing new rails and partners into production.

Measurable gains in operational efficiency—lower exception rates, faster resolution, or reduced manual load.

Some challenges you might tackle
Reconciling crypto and fiat across many banks, PFIs, liquidity providers, and exchanges, each with its own quirks and timing.

Diagnosing why a payment stalled or failed when the answer spans several partners and systems.

Deciding when an exception needs escalation versus a fix you can own directly.

Building automation and AI-enabled workflows that hold up as volume grows.

Keeping settlement and reconciliation accurate while new rails and corridors launch around you.