← Latest projects
02 · iGaming payments · 2024 – 2026

Payment systemEvery way money moves, in one back office.

A payment platform built from scratch for an iGaming operator: deposits and payouts through bank gateways, P2P card apps, crypto, Stripe, PayPal and Idram — with live monitoring, reports and roles down to every action. I led the front end.

Stack
Vue 3 · Inertia · PrimeVue · Laravel
Role
Front-end team lead
Payment methods
25+ in one admin
Admin
50+ sections
payment-system.example
Payment system — main screen
The challenge

An iGaming operator needed to take deposits and pay out winnings through dozens of channels — local bank gateways, P2P card apps, crypto and international cards. Each channel had its own panel, its own failures and its own reports, and support and finance were juggling tools instead of helping players.

What I built

We built the platform from scratch — it started as two developers. It routes every deposit and payout, and one admin runs all of it. I led the front end, every screen of that admin: transactions of every type with filters and a timeline, Live Ops for real-time monitoring, gateways and user levels, withdrawals, the dashboard and reports, and roles and permissions down to each action. When a payment fails, the admin says why in plain words.

My part
  • Front-end team lead — the whole admin front end
  • Dashboard, reports and statistics
  • Roles and permissions for every action
  • Live Ops: real-time monitoring over WebSockets
Stack
Vue 3Inertia.jsPrimeVueTailwindPiniaChart.jsLaravelWebSockets
Screens

How it works, screen by screen.

payment-system.example
The dashboard
01

The dashboard

Money in by hour and by payment type, with totals per channel — for today, this week or any range.

payment-system.example
Every deposit, one table
02

Every deposit, one table

Status, amount and method at a glance, with the filters support actually uses.

payment-system.example
Filter by what went wrong
03

Filter by what went wrong

Two clicks narrow the list to cancelled or failed payments.

payment-system.example
The whole story in a drawer
04

The whole story in a drawer

Every status change of a transaction on one timeline, in order, without leaving the list.

payment-system.example
The reason, in plain words
05

The reason, in plain words

The provider's error code becomes a sentence support can read to a player, plus the next step.

payment-system.example
Live Ops
06

Live Ops

Transactions and gateway health as they happen, so a failing channel is caught in seconds.

payment-system.example
Roles and permissions
07

Roles and permissions

For every section: who can view, create, update and delete — and the admin shows each role only its part.

On the phone

The whole admin, on a phone.

9:41
9:41
9:41
9:41
The rest of the admin

Built for daily operations, by support, finance and ops.

Live Ops · light theme
Live Ops · light theme
Gateways by user level
Gateways by user level
Prepayment management
Prepayment management
Withdrawals
Withdrawals
P2P card deposit · details
P2P card deposit · details
Scheduled updates
Scheduled updates
Details

The small things that make it work.

By the hourEvery channel on one chart.
TimelineEvery state the payment passed through.
PermissionsPer section, per action.
Decisions

Why it's built this way.

  1. 01

    One admin for every way money moves

    Bank, card, crypto, Stripe, PayPal and Idram deposits and every kind of payout share the same table, filters, timeline and actions — support learns one screen, not ten.

  2. 02

    Live Ops in real time

    New transactions and gateway errors arrive over WebSockets on a live monitor, so the team sees a failing gateway in seconds instead of from player complaints.

  3. 03

    Roles down to every action

    Every section has its own view, create, update and delete permission, and the admin only shows what a role is allowed to do — finance, support and ops each get their own back office.

  4. 04

    Reports people act on

    Statistics by hour, payment type, amount range and user level, a P2P report with success rate and failure reasons, and a 360° report for any customer — the numbers behind every decision.

Result
25+payment methods in one admin
50+admin sections, from Live Ops to reports
Livemonitoring of every transaction and gateway
Next projectSongBuilt for a phone and greasy hands.→