Payments Domain Architect

Otterbase, Inc.; United States; On-site; USD 180,000 - 250,000; Full time

Job summary

Otterbase, Inc. is seeking a hands‑on Architect to lead the payments area of a large‑scale digital commerce platform.

You will own the end‑to‑end payment lifecycle, from authorization to refunds, across card, SNAP, and WIC tenders, while shaping a robust Temporal/Kafka/Azure‑based platform. You will mentor senior developers, review PRs, and steer cross‑team discussions with processors, partners, and finance.

Qualifications

• Must have 10+ years in software engineering with a payments focus.
• Deep domain‑driven design and bounded contexts.
• Hands‑on C# / .NET 8+ with production experience in Temporal or similar.

Responsibilities

• Set the payments platform technical vision and roadmap.
• Design services, workflows, and event schemas across teams.
• Lead integration with processors, benefit programs, and finance systems.
• Ensure idempotency, auditability, and secure data handling.

Skills

Payments domain

C# / .NET

Temporal / durable workflows

Kafka / event streaming

Azure cloud services

Tools

OpenTelemetry

PCI DSS knowledge

Job description

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.

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.

Responsibilities

Ownership & Direction

• 
  Set the technical vision and roadmap for payments and make the major design call
• sDraw clear lines around what payments owns, and establish a common model and terminolog
• yAssign each business function to the right service or workflo
• wProduce architecture review documents and decision record

sDesi

• gn
  Create payment operations that are safe to retry and never execute twice, using patterns such as sagas, compensating actions, transactional outbox/inbox, and reconciliat
• ionDefine interfaces and event schemas shared with neighboring teams (OpenAPI, JSON Schema, Protob
• uf)Clarify which systems produce data, which verify it, and what downstream consumers can tr

ustWorkflow & 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 t
• ests)Model Kafka events with governed schemas, retry handling, and dead‑letter ro

utingPayment 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 re
• versalsResolve uncertain or timed‑out transactions without charging customers twice or leaving orphane
• d holdsKeep SNAP and WIC handling aligned with federal USDA and state‑level requi
• rementsShrink PCI footprint through tokenization (network tokens, DPAN), encryption, and key r
• otationAdd new payment options such as mobile wallets and split p
• aymentsEnable third‑party marketplace payments, including multiple captures, over‑capture limits, and split set
• tlementWork with finance on reconciliation, transaction log reporting, and ledger a
• ccuracySet and track service targets for authorization, capture, refund, and recovery

successReliability &

• Testing
  Engineer fault tolerance using Polly and Temporal retry conf
• igurationKeep authorization latency comfortably inside checkout time limits across Azur
• e and GCPImplement end‑to‑end tracing across APIs, Kafka, and Temporal using Open
• TelemetryOwn the test approach: unit, contract, replay, simulated gateways, and performanc

e testingTechnical

• Leadership
  Conduct code reviews and develop senior enginee
• ring talentRetire legacy flows through controlled, feature-flagg
• ed rolloutsApply AI‑assisted development tools to speed
• ry Must Have 10+ years in software engineering, with at least 5 years focuse
• d on paymentsStrong domain‑driven design background (bounded contexts, domain events, con
• text mapping)Deep, current, hands‑on C# and .
• NET 8+ skillsProduction use of Temporal or a comparable durable work
• flow platformProduction
• use of KafkaAzure platform services (App Service, Cosmos DB, API Management, Key Vault) or GC
• P equivalentsContainerized applications running
• on KubernetesReal‑world implementation of idempotency, saga, and reconcilia
• tion patternsPCI DSS and tokenizati
• on experienceObservability design using OpenTelemetry or an
• APM platformHistory of getting multiple engineering teams aligned on a common
• e Nice to Have Temporal Nexus or Wo
• and Google PayProcessor APIs such as Aurus, Adyen, Fiserv, Wor
• ldpay, or ChaseNetwork tokenization, DPAN, multi‑capture, and marketp
• lace settlementMulti‑cloud
• (Azure and GCP)LaunchDarkly or similar featu
• re‑flag tooling.NET Aspire, Testcontainers, Mocko
• general ledger)Grocery or omnichannel re