Skip to main content
Platform serviceCentral auth & billing API · microservices

Accounts

The single source of truth for login, companies, invoices and Stripe billing across a suite of independently deployed apps.

In plain words

When several apps make up one product, they all need to agree on who the user is and what they owe. Accounts is that shared brain: it handles sign-in, companies, customers, invoices and payments, and every other app asks it rather than keeping its own copy.

Interactive preview

How Accounts works

Interactive · illustrative sample data

The challenge

A billing platform split into several services still needs one login, one set of companies and one ledger. Duplicating that data in each app leads to drift and security gaps.

Our approach

Make Accounts the only owner of identity and money. Other services consume its JSON APIs, and every record is scoped by company.

Step by step

From first click to finished job

  1. 1

    User signs in once

    Accounts issues the session used across the suite.

  2. 2

    Apps request data

    Billings and GSM call Accounts' APIs, never a private copy.

  3. 3

    Invoice is paid

    Stripe confirms the payment and Accounts updates the ledger.

Capabilities

What it does

Central login & RBAC

One identity and role model shared by every app in the suite.

Companies, customers & vendors

Multi-company records with consistent scoping.

Invoices & payments

Invoice lifecycle and payment records, integrated with Stripe.

JSON APIs

Clean APIs consumed by Billings, GSM and the platform shell.

Admin dashboards

React + TypeScript admin for operators.

Tested with Pest

Automated tests around the money paths.

Engineering

Key decisions

One owner for money

Billing logic lives in one service so totals can't disagree.

company_id everywhere

Every record is scoped by company to prevent cross-tenant leaks.

Architecture

Tech stack

API

  • Laravel
  • PHP
  • REST API

Admin

  • React
  • TypeScript

Payments & quality

  • Stripe
  • Pest

Outcome

What it delivers

  • Single login and billing source for the whole platform
  • Other teams build on stable APIs instead of re-implementing billing

Deep dives

Read the engineering notes

Services behind it