Jim ChangSoftware Engineer ยท System Integration
Digital wallets

Wallet Ledger & Payment Operations

Backend, operations console and chat-bot channel for a multi-wallet platform, designed so transactions are never duplicated or lost.

The problem

Money moves between the platform, payment gateways and partner systems that retry, time out and send duplicate callbacks. Crashes and delayed messages must never duplicate, lose or misattribute funds.

What I built

  • Wallet, transaction and currency-exchange services with pluggable payment-gateway and partner integrations.
  • Operations console for finance, risk, compliance, support and admin teams: identity verification (KYC), risk review, support tickets, reporting and a full audit trail.
  • A chat-bot channel, built as a separate service, where customers link their account, check balances and history, top up or withdraw, upload verification documents and contact support.
  • Partner middleware with signed requests, idempotency records and a saga for multi-step money operations.

Technical highlights

  • The PostgreSQL ledger is the only source of truth. The message bus, cache, admin client and partner systems all defer to it.
  • Transactional outbox to Kafka, with dedicated workers for payments, reconciliation, risk, reporting and notifications.
  • Idempotency and replay protection on every external callback, with operational and wallet data in separate databases.
  • Grew out of an earlier double-entry ledger service with HMAC-signed APIs and pluggable top-up methods.

Need something built or connected?

Send me a few lines on what you need and when you need it by.