Bridgewater Payments, a payments platform for businesses

Bridgewater Payments is a payments platform for businesses. A client onboards, holds balances in virtual accounts, moves and converts money, pays out to fiat and settles, with the compliance controls a regulated financial product requires. It also runs a self-serve flow for end users.

I am the sole technical owner: the architecture, backend, frontend, integrations, the backoffice and the product decisions around all of it.

This case study contains no proprietary code or confidential data. It describes the product, my role and how it is designed.

What I built

• KYC and KYB onboarding. Identity and business verification integrated with external providers, with review states and audit trails.
• Virtual accounts. Account issuance and balance management for business clients.
• Fiat off-ramps. Flows to convert and pay out to traditional rails, with configurable fees.
• Settlement rules engine. Configurable rules that decide how and when funds settle.
• Billing. Fee configuration and a true-up reconciled against real movement.
• Transfer approvals. One person enters the operation and another approves it, for sensitive operations.
• Self-serve flow for end users. Signup, terms acceptance and onboarding.
• Operational backoffice. The internal console the operations team uses to review, approve and resolve cases.

How it is designed

Correctness and auditability come first: every financial state change is recorded and reviewable.

Client-facing flows are separated from operations and compliance tooling.

Providers sit behind internal interfaces, so one can be swapped without touching core logic.

Paths that delete data or move money fail closed: when in doubt, the operation does not go out.

Status

Live in production with real business clients. I still run it.