ALGOBAIN
A customer paying at a card terminal on a shop counter
[Photo placeholder] Payments, point of sale

Case study 02 · Payments · 12 months

Ten million dollars of bills, each payment rewarded.

A payments client wanted people to pay bills on time and keep coming back. Algobain built the multi-biller payment platform, the coin-rewards engine and the ledger that accounts for every coin.

$10M+
Transactions processed through the platform.
35K+
Active users.
94%
Of payments made on time.
01
The situation

Paying a bill on time earned nothing.

The client wanted a gamified payment platform: digital coins for paying bills and making transactions, and a loyalty ecosystem that makes timely payment worth the effort. What stood in the way:

  1. iUsers had little motivation to pay bills on time.
  2. iiTraditional payment systems offered no reward for regular transactions.
  3. iiiThere was no single place to manage several bill payments.
  4. ivPayment history and upcoming bills were hard to track.
  5. vNothing encouraged consistent payment behaviour over time.
02
What we built

A payment platform with its own economy.

i

Coin rewards engine

The economy: how coins are earned, recorded, redeemed and protected.

  • A coin economy with dynamic reward calculation.
  • A blockchain ledger for transparent coin transactions.
  • Tiered rewards based on payment amount and frequency.
  • A redemption marketplace with partner integrations.
  • Anti-fraud mechanisms that stop people gaming the system.
ii

Bill payment integration

One platform for many billers.

  • Integrations with 50+ utility providers and service companies.
  • Automated bill detection and payment scheduling.
  • Recurring payments with reminders.
  • Payment history, analytics, receipts and tax documentation.
iii

Payment processing

The money movement underneath the rewards.

  • Card processing through Stripe; ACH transfers for bank payments.
  • A wallet for coin storage and management.
  • Instant payment confirmation.
  • A refund and dispute resolution workflow.
iv

User experience

The reason people come back.

  • A responsive web app in React and Material UI.
  • Badges, levels and streaks.
  • Real-time coin balance updates.
  • A dashboard of savings and rewards, with achievements users can share.

03 · Architecture

Every coin traced to the payment that earned it.

A confirmed payment is the only thing that can mint coins. The rewards engine calculates the tier, the anti-fraud check decides whether the coins are issued, and the ledger keeps the record.

Coin rewards, reference architecture
Bill detection50+ billers Scheduled paymentsRecurring, reminders Card and bankStripe, ACH Payment processingInstant confirm Rewards engineTiered calculation Anti-fraud checkStops gaming Coin ledgerBlockchain, append-only WalletLive balance RedemptionPartner marketplace Flagged, no coins issued, logged Every coin traced to the payment that earned it Fig. 1

Fig. 1 Reference architecture as built. Component names are generic; client systems are withheld under NDA.

The operator's view

Each payment shows the coins it earned and why. A payment that looks like gaming the system is flagged before a single coin is minted.

04
The result

The numbers the platform is held to.

MeasureResultBasis
Transactions processed$10M+Bill payments across 50+ billers. [Period]
Active users35K+[Definition of active]
Coins distributed5M+Recorded on the coin ledger.
On-time payments94%[Baseline and period]

Figures from the engagement record. Where the basis of a figure is not yet documented, it is shown as a placeholder rather than invented.

05
Technology

What it runs on.

Interface
ReactMaterial UI
Services
Node.js
Data
PostgreSQLBlockchain ledger
Payments
StripeACH transfersCoin wallet
Integrations
50+ billersPartner merchants
A hand holding a payment card above a laptop keyboard
[Photo placeholder] Online bill payment
An empty meeting room with a long table and floor-to-ceiling windows in daylight
[Photo placeholder] Briefing room

A transaction system that has to reconcile?

Tell us what you are trying to run in production. A senior engineer replies within 48 hours.

  1. 1
    Within 48 hoursA senior engineer replies, not a sales desk.
  2. 2
    NDA, then a working sessionWe sign first, then look at the system together.
  3. 3
    Two-week fixed-fee assessmentWritten roadmap, ROI and build-versus-buy. No lock-in.