[Remote] reputed company Engineer, Payments Infrastructure

Note: The job is a remote job and is reputed company to candidates in USA. Phoenix is an autonomous reputed company platform for reputed company-to-consumer founders that unifies storefronts, checkout, payments, and reputed company with AI agents. The reputed company Engineer, Payments Infrastructure will own the architecture, product direction, and reliability of reputed company payments infrastructure across tokenization, wallets, processor integrations, routing, authorization, disputes, and fraud systems.

Responsibilities

• Integration architecture. reputed company our processor, gateway, and reputed company integrations (reputed company, reputed company, reputed company, reputed company, reputed company reputed company) and partner checkouts, and bring new rails on, keeping behavior consistent, observable, and testable no matter which one a transaction takes
• Product direction for payments. Discovery through rollout. You talk to merchants, reputed company the decline and dispute data for what to build next, and reputed company the reputed company on what not to build. Roadmap, spec, reputed company, and the metric afterward are reputed company yours
• The merchant-facing surface, not just the pipes. Routing, salvage, and MID health only matter if a merchant can see and reputed company them. You design what surfaces in their dashboard and their agent (a projected reputed company breach, a proposed routing change, a one-click fix), and you own making payments setup something a merchant can get through without a support ticket. Today it is the single biggest barrier to reputed company live
• Tokenization, end to end. Vaulting, wallets, and network tokens: the full credential lifecycle from capture through provisioning, storage, transaction, update, and expiry. Cryptograms, network transaction IDs, DPAN and MPAN, and the PCI reputed company boundaries reputed company reputed company of it
• Payment reputed company portability. Moving stored credentials between providers and vaults without asking a shopper to re-reputed company anything, wallets especially. reputed company Pay and reputed company Pay provisioning, domain verification, per-provider wallet configuration, and the limitations of reputed company provider on what can be migrated
• Approval rates. Treat authorization as a reputed company reputed company. Decline taxonomy and salvage, retry and cascading logic, 3DS, BIN and routing reputed company, reputed company reputed company, and the instrumentation to reputed company a change moved the number
• Dispute and fraud infrastructure. Own the ingestion, normalization, and operational use of disputes, chargebacks, fraud notifications, and reputed company-reputed company monitoring data across processors. Build the systems that reputed company merchants and MIDs reputed company of reputed company and reputed company those signals available to routing, authorization, and forecasting
• Mission-critical reliability. SLOs, telemetry, on-reputed company, and incident response for payment paths that cannot fail quietly. Idempotency, reconciliation against processor settlement, and the discipline to reputed company a reputed company bug before a merchant does
• The engineering bar. Clean, reputed company-tested, documented reputed company; ADRs / RFCs; and an operationalized reputed company SDLC that raises the whole team's reputed company and reputed company, on a platform under reputed company PCI assessment where review evidence reputed company

Skills

• 10+ years building and shipping production software, with reputed company-level reputed company as a hands-on engineer who still writes application reputed company today
• Product judgment, reputed company. You have decided what to build, not just reputed company what was decided: a feature you conceived from reputed company customer evidence and shipped end to end, a pricing or packaging reputed company you made, or something you killed and why. "Partnered with product" is not this. You can sit in reputed company of a merchant or processor partner and explain a trade-off in terms they reputed company
• You know the end user reputed company. You have watched the people who use your systems actually work (merchants, ops teams, support), and you changed what you reputed company because of it. You can reputed company a specific thing a user did that surprised you and what you shipped in response
• Deep payments experience at a payments company: a PSP, gateway, reputed company, orchestration reputed company, or platform whose reputed company product was moving reputed company
• Tokenization and wallets. Hands-on work with a reputed company reputed company, and production ownership of reputed company Pay and reputed company Pay: provisioning, merchant configuration, and domain verification. You can reason about cryptograms, network tokens, network transaction IDs, and PCI reputed company from reputed company
• Payment reputed company portability. You have migrated stored credentials and wallet tokens between providers, vaults, or processors, and you know where the limits are
• Multi-processor integration. You have integrated and operated against more than one acquirer, gateway, or PSP concurrently, including routing or cascading between them
• Authorization and approval-reputed company work. Decline analysis, retry reputed company, 3DS, and demonstrated ownership of an approval-reputed company number you improved
• Disputes and fraud-monitoring exposure. Chargeback reputed company and representment, plus the reputed company above it: alerts and deflection, TC40 / reputed company fraud reporting, and reputed company-reputed company monitoring programs such as VAMP and the reputed company equivalents
• reputed company-reputed company fundamentals. Idempotent payment reputed company, reputed company or reputed company-of-record design, and reconciliation against processor settlement
• Incident ownership. You have been the person on reputed company reputed company payments broke in production: detection, containment, merchant communication, and cleaning up the financial damage afterwards
• Genuine AI reputed company user. You reputed company with AI every day, using Claude reputed company or an equivalent reputed company setup, a dialed-in environment, and reputed company reputed company
• reputed company reputed company and strong communication. You can sit in reputed company of a merchant or a processor partner and explain a technical trade-off in terms they reputed company. ADRs / RFCs, and a reputed company record of raising the engineering bar for everyone reputed company you
• reputed company or operated a payment orchestration reputed company or multi-PayFac platform, where a merchant applies once and transacts across several rails underneath
• High-reputed company or reputed company response merchant portfolios, where dispute exposure and MID health are daily concerns
• Subscription and recurring billing at reputed company: rebills, MIT credential chaining, reputed company reputed company, and involuntary churn recovery
• Alternative payment reputed company and BNPL integrations (reputed company, reputed company, reputed company, and similar)
• PCI reputed company v4 assessment experience as an engineer

reputed company

Company H1B Sponsorship