QR tipping and settlement · Work in progress

Work in progress · hosted sign-in verified; money movement not exercised

Splitcore

Splitcore is a product for venues and entertainers: guests can reach a human-facing tipping experience from a QR code while venue teams have a separate management surface. The public repositories contain a Next.js frontend and a NestJS backend with payment, webhook, ledger and payout modules.

Splitcore’s hosted venue sign-in screen, with no credentials entered.
Hosted venue sign-in screen, captured 3 November 2026. No credentials were entered; the signed-in dashboard and any guest or payment route were not opened.
INTENDED USERS

Guests who want to tip; venue teams managing entertainers, QR codes and split rules.

These are the product roles described by the repositories, not verified customers, venues or adoption.
PRODUCT STATUS

Work in progress · hosted sign-in verified; money movement not exercised

TECHNOLOGY

Next.js App RouterNestJSTypeScriptPrisma / PostgreSQLRedis / BullMQPaystack provider interface

01 / Business problem

Why this product exists.

A QR code that opens raw API data is not a usable guest experience. Once a payment is introduced, the system also needs a defensible way to verify settlement and account for each share.

02 / Product objective

What it is trying to change.

Separate the guest-facing QR route from the venue dashboard and keep payment verification, split calculations and ledger posting on explicit backend paths.

03 / Solution architecture

Separate concerns.
Keep the path clear.

Module boundaries and data paths observed in source; this is not a live deployment diagram.

  1. 01

    Guest and venue surfaces in a server-rendered Next.js frontend

  2. 02

    NestJS API with role-scoped routes

  3. 03

    Prisma/PostgreSQL persistence and immutable ledger entries

  4. 04

    Redis/BullMQ for asynchronous webhook and payout work

04 / Engineering decisions

Choices worth
making explicit.

These notes describe the implementation found in the repositories—not measured product outcomes.

01

The ledger uses positive integer kobo, validates split basis points, and checks that debits equal credits before returning a posting.

02

The settlement service re-verifies payment status, amount, currency and the stored split snapshot; a single database transaction conditionally claims settlement and writes ledger and payout obligations.

03

Webhook payloads are not treated as payment truth: stored events route into settlement, which verifies with the provider. Duplicate or concurrent settlement attempts do not double-post.

05 / Selected implementation

Details you can
follow to source.

The source separates pure ledger calculation from persistence and payment-provider access. The hosted frontend currently exposes a venue sign-in screen; the private dashboard, guest QR flow and payment paths were not exercised during this review.

06 / Current status and limits

What remains
unfinished.

  • No sign-in was attempted and no QR-token endpoint was called; the latter can create a guest session.
  • No payment provider, webhook, test card, payout or production database was contacted. Repository completion notes and service documentation are not independent proof of current production readiness.
  • The backend’s integration guide requires a configured database, queue and provider test environment; those integrations were not run as part of this website work.

07 / Potential improvements

What to do
next.

  • Add a sandbox-only, non-settling walkthrough that can be reset and that never reaches live payment services.
  • Recheck deployment and backend contract status with a controlled test environment before describing live money movement.
  • Add visible operational evidence for retries, reconciliation and manual review paths.
Back to all engineering work

A useful next conversation

Have a problem
like this?

Bring the situation, not a finished technical brief.

Discuss a project