Kensink Labs
B2B SAAS · PAYMENTS + FSMNuforce (US)· US

Nuforce.
Payment-integrated B2B SaaS, shipped end-to-end.

200+ accounts on one ledger.

200+
B2B accounts onboarded
PAYMENT-INTEGRATED B2B SAASB2B SAAS · PAYMENTS + FSM

Nuforce: Payment-integrated B2B SaaS, shipped end-to-end. 200+ accounts on one ledger.

Field-service management built around three payment processors abstracted behind one unified ledger, with tokenisation, idempotent capture/refund, reconciliation, and dispute handling. We took it from architecture to 200+ B2B accounts in production.

200+
B2B accounts onboarded
3×
Processors abstracted behind one ledger
< 1%
Settlement variance auto-reconciled
8 wk
Onboarding → first transaction
01 · THE PROBLEM

Where they were stuck.

Nuforce's field-service operators were juggling three payment processors, each with quirks around capture windows, partial refunds, and dispute lifecycle. The legacy stack relied on hand-rolled reconciliation scripts and an Excel-based dispute queue. Every new customer added required a bespoke webhook handler. Growth past 50 accounts started compounding the operational debt.

02 · OUR APPROACH

How we built it.

  • 01Three-processor abstraction behind a unified capture/refund/void interface. Switching processors per merchant became a config flag, not a code change
  • 02Idempotent capture/refund with per-transaction idempotency keys, retry semantics tested under network-failure scenarios in CI
  • 03Tokenisation at point of payment: card data never touched our database. PCI-DSS scope reduced to a single audited surface
  • 04Reconciliation pipeline reading processor settlement reports nightly into Postgres, surfacing discrepancies in the operator dashboard
  • 05Dispute lifecycle automation: webhook → ticket → response builder → submission, with full audit trail
  • 06Observability across the payment surface: PagerDuty alerts on settlement variance > 0.5%, latency p95 dashboard per processor
“The platform absorbed processor differences so cleanly that our operators stopped knowing which processor a customer was on. That's the moment we knew the abstraction worked.”
Engineering Lead
Nuforce
[TECH STACK]
  • TypeScript
  • Edge serverless
  • Postgres
  • Payment processor APIs
  • Error monitoring
[ENGAGEMENT]
DurationMulti-year (2019–2022)
ClientNuforce (US)
ShapePAYMENT-INTEGRATED B2B SAAS
HandoffFull ownership · 90-day warranty
START YOUR OWN PROJECT

Bring a real problem.
We’ll bring code on day one.

Start your own project →Book a 15-min intro
← All casesCASE · NUFORCE