TITLE: Payment Engineer

ENVIRONMENT: Financial Services

LOCATION:  New York City, NY

COMPENSATION RANGE:  $200,000.00 - $295,000.00   DOQ

DEGREE REQUIREMENTS:  Bachelors Degree

EXPERIENCE LEVEL: 5+ years experience

NUMBER OF POSITIONS AVAILABLE: 1

WORK STATUS:  Must be able to work for any United States. Company without sponsorship

POSITION SUMMARY:

As a Payments Engineer, you will have the opportunity to join our growing Engineering team and report to the Head of Engineering and CTO. You will be staffed directly on one of our highest-leverage new initiatives: building our credit card processing infrastructure from the ground up — including acquirer integration, PCI-scoped data handling, and modern checkout flows that power card-based pay-ins and pay-outs across our platform. This is a core new piece of our infrastructure, and we're hiring someone who has done this before and can come in with thesis-backed opinions on how and why to build it a certain way.

Responsibilities

Own the card stack end-to-end:

• Architect and ship our acquirer integration — authorization, capture, void, refund, partial capture, 3DS, network tokens, account updater, and settlement/reconciliation flows
• Design and build PCI-compliant data handling: tokenization, scope minimization, vaulting strategy, and secure checkout surfaces that keep us in the smallest possible PCI footprint (SAQ A where feasible)
• Integrate robust abstractions for payment orchestration that minimize complexity and ensure extensibility as we add networks, acquirers, and geographies

Shape the future of our product, solve real-world use cases:

• Contribute in a full-stack manner to our platform and API offerings
• Build checkout experiences and hosted payment flows — including SDKs, iframes/elements, and server-side orchestration that balance conversion, fraud, and compliance
• Build robust chargeback, dispute, and exception handling pipelines, including evidence submission, representment workflows, and fraud signal integration;
• Design for idempotency, auditability, and eventual consistency across card authorization, capture, and payout workflows — with a deep respect for retries, network timeouts, and dual-writes
• Communicate implementation tradeoffs across acquirers, processors, and gateways with a focus on cost, performance, auth rates, security, and observability

Our stack: TypeScript + React, NestJS + Postgres + Prisma, AWS (SQS/SNS/Lambda), Vercel, Docker