Payments Domain Architect

We're looking for a hands-on architect to lead the payments area of a large-scale digital commerce platform. You'll be responsible for how every online order gets paid for, from the first authorization through adjustments, capture, and refunds, across card, SNAP, and WIC tenders.

Please ensure you read the below overview and requirements for this employment opportunity completely.
You'll shape a platform built on Temporal, Kafka, and Azure, with the goal that no payment is ever lost, duplicated, or left unreconciled, even when a processor stops responding or a process breaks midway. You'll also set the standards the teams follow for versioning, monitoring, fault tolerance, and card-data security.
You'll build prototypes and reference code, review pull requests, and coach senior developers. You'll also serve as the technical lead in conversations with processors, benefit program partners, and the finance organization, and work alongside the pricing, ordering, and fulfillment teams so that payment data flows accurately all the way into the books.
ResponsibilitiesOwnership & Direction

Set the technical vision and roadmap for payments and make the major design callsDraw clear lines around what payments owns, and establish a common model and terminologyAssign each business function to the right service or workflowProduce architecture review documents and decision record
s
Desi
gn
Create payment operations that are safe to retry and never execute twice, using patterns such as sagas, compensating actions, transactional outbox/inbox, and reconciliationDefine interfaces and event schemas shared with neighboring teams (OpenAPI, JSON Schema, Protobuf)Clarify which systems produce data, which verify it, and what downstream consumers can tr
ust
Workflow & Event Architec
ture
Implement long-running workflows in Temporal, including cross-team calls through NexusEstablish safe upgrade practices for in-flight workflows (patching, build IDs, replay tests)Model Kafka events with governed schemas, retry handling, and dead-letter ro
uting
Payment Proc
essing
Design payment handling for each stage of an order: placement, changes, cancellation, completion, and returnsCoordinate orders paid with more than one tender, including card, SNAP, and WICLead integrations with processors and benefit providers covering authorizations, captures, voids, refunds, and reversalsResolve uncertain or timed-out transactions without charging customers twice or leaving orphaned holdsKeep SNAP and WIC handling aligned with federal USDA and state-level requirementsShrink PCI footprint through tokenization (network tokens, DPAN), encryption, and key rotationAdd new payment options such as mobile wallets and split paymentsEnable third-party marketplace payments, including multiple captures, over-capture limits, and split settlementWork with finance on reconciliation, transaction log reporting, and ledger accuracySet and track service targets for authorization, capture, refund, and recovery
success
Reliability &
Testing
Engineer fault tolerance using Polly and Temporal retry configurationKeep authorization latency comfortably inside checkout time limits across Azure and GCPImplement end-to-end tracing across APIs, Kafka, and Temporal using OpenTelemetryOwn the test approach: unit, contract, replay, simulated gateways, and performanc
e testing
Technical
Leadership
Conduct code reviews and develop senior engineering talentRetire legacy flows through controlled, feature-flagged rolloutsApply AI-assisted development tools to speed
up delive
ry
Must Have
10+ years in software engineering, xzbcwsv with at least 5 years focused on paymentsStrong domain-driven design background (bounded contexts, domain events, context mapping)Deep, current, hands-on C# and .NET 8+ skillsProduction use of Temporal or a comparable durable workflow platformProduction use of KafkaAzure platform services (App Service, Cosmos DB, API Management, Key Vault) or GCP equivalentsContainerized applications running on KubernetesReal-world implementation of idempotency, saga, and reconciliation patternsPCI DSS and tokenization experienceObservability design using OpenTelemetry or an APM platformHistory of getting multiple engineering teams aligned on a common
architectur
e
Nice to Have
Temporal Nexus or Worker VersioningSNAP / WIC payment processingApple Pay and Google PayProcessor APIs such as Aurus, Adyen, Fiserv, Worldpay, or ChaseNetwork tokenization, DPAN, multi-capture, and marketplace settlementMulti-cloud (Azure and GCP)LaunchDarkly or similar feature-flag tooling.NET Aspire, Testcontainers, Mockoon, or WireMockRetail finance data (transaction logs, sales audit, general ledger)Grocery or omnichannel retail background