Cashier infrastructure

Your players load, play and cash out. Nobody stands at a counter.

eZFunds gives every player one account and one balance, moves money into the games you already run, and keeps a ledger that reconciles at the end of the day.

A player's balance, Tuesday
Deposit received +$47.13
Sent to game −$47.00
Cashed out of game +$62.00
Withdrawn −$60.00
Still in wallet$2.13

What it replaces

The counter.

Every load and every payout is a person, a keyboard and a chance to fat-finger a number. eZFunds does the same work continuously, and writes down what it did.

A player signs up once

Their accounts on each game platform are created for them in the background. They never register anywhere twice.

They fund their own wallet

Money arrives at an address that belongs to that player alone, so it is never ambiguous whose deposit it was.

They move it into a game when they want to

Not when it arrives. A deposit at midnight can sit in the wallet until Saturday.

Cashing out comes back the same way

Winnings return to the wallet, and the player withdraws on their own schedule.

How money moves

Three places money can be. Never in between.

Every transfer either completes or is returned. There is no state where a player's money is somewhere neither of you can see.

01 — Wallet

Money they've paid you

Held to the exact cent, spendable by them, visible to you.

Guaranteed: the balance is the sum of its own history. There is no stored total that can drift.
02 — In play

Money on a game

Moved on the player's instruction, carried out by an automated cashier against the platform you already use.

Guaranteed: a transfer that fails is refunded in the same write that records the failure.
03 — Out

Money they've taken

Withdrawn to the player's own address, inside limits you set per transaction, per player and per day.

Guaranteed: one payout per instruction, enforced by the database rather than by hoping.

The server derives every deposit address from a watch-only key. It can see what arrives and it cannot spend it — the keys that could stay with you, on hardware, offline.

Built in, not bolted on

The boring parts, done properly.

Most of this is invisible until the day it matters, which is the day it has to already be there.

An append-only ledger
Nothing is edited. A correction is a new entry, so a balance and its history can never disagree with each other.
Every action attributed
Who did it, when, and from where — staff, automated cashier, or us if you ever ask us to look at something.
Limits that assume a bug
Caps per transaction, per player and per day. The last one exists to bound a fault that satisfies the first two on every attempt.
Your own domain and branding
Players see your business. Ours appears nowhere they can reach.
Backups that have been restored
Including the encrypted material a database dump alone cannot bring back. An untested backup is a belief, not a backup.

Who it's for

Small operators running sweepstakes gaming.

One location or several. If your staff currently key loads into a game platform by hand and settle up out of a drawer, this is built for exactly that.

  • You already run a game platform and don't want to change it
  • Your cashier work happens at a counter, in person, one at a time
  • You'd rather your staff served customers than typed numbers
  • You want to be able to answer "where did that money go" precisely

Get in touch

Tell us what you run.

We'll come back with what setting this up for you would actually involve — including the parts that need something from your side.

We'll only use this to reply.