Skip to content
SH-02PPlate 1

Payment & Travel Platforms

Sanjow

Production work at Sanjow on payment and travel platforms that several brands share, serving live customer traffic. My part: I built most of the check-in service and of the online ticket shop. On the shared platform API, as one of its main developers, I work on check-ins, payments and bookings, customer messages and database speed.

Type
Payments / SaaS
Status
Private
  1. A–A · 1When a check-in failed, two parts of the system each retried it three times, so one booking could be tried nine times. Now only one part keeps count: three tries.
  2. A–A · 2Every check-in attempt now leaves a record, even one the server cuts short, so a system in trouble can never look idle.
  3. A–A · 3A check-in counts as done only when every passenger has a boarding pass that we opened and checked. A "done" on screen is not enough.
  1. Front-ends: Check-in funnel, one deploy, every brand · 8 locales, contributor; Newer checkout funnels, a public login-link proxy, gated at the API, contributor; Member zones, single sign-on across the group, contributor; Tickets storefront, seat maps · 3-D Secure, main developer; Back-office, the operations console I joined in 2022, contributor.
  2. API: Platform API, Express · Prisma · Zod → OpenAPI, one of the main developers.
  3. State: PostgreSQL, 101 models, hand-written SQL migrations; Redis · BullMQ, 51 queues · 50 scheduled jobs; Object storage, verified documents.
  4. Outside: Check-in workers ×12, main developer; Payment gateways, card tokenisation · 3-D Secure; Mail · SMS · voice, webhooks in, messages out; Travel inventory · eSIM · top-ups, partner APIs; LLM, three API modules, a fallback pair in the check-in workers.

Section A–A, one check-in, from click to boarding pass. The path runs Check-in funnel, then Platform API, then Redis · BullMQ, then Check-in workers ×12, then Object storage.

Problem
Several brands sell payment and travel products on one stack, with live money moving through it.
Constraint
Every outside provider is reached through one shared service, each website serves every brand from the same code, and monitoring is not optional.
Decision
Websites that adapt to each brand's look, with one shared service behind them. That service is monitored, and its changes must pass automatic tests.
Outcome
In production, serving live customer traffic. The architecture is the drawing above; there are no public stills.

General notes

  1. 01Each outside service we connect to has its own folder, with a single way in.
  2. 02Every change to the database structure is written by hand, and its file records what was measured in production and how to check it can be undone.
  3. 03When the system cannot tell what state an account is in, it assumes the costly case: a failed lookup no longer shows an account as brand new.
  4. 04Alarms go off at levels taken from real traffic.
  5. 05Better a link that fails than a customer landing on another brand's site.
  6. 06Before the seat map was designed, four small tests recorded how the supplier's tool really behaves.
  7. 07Before release, every new safety check is deliberately broken to prove its test catches the failure, then restored.
  8. 08An hourly database search went from 818 ms to 3 ms, thanks to an index built while the database stayed open for reading and writing.

Bill of quantities · As-built 2026-11

Item, quantity, and the command that measured it.
ItemQuantity
Prisma modelsgit show origin/master:prisma/schema.prisma | grep -c '^model '101
BullMQ queuesgit show origin/master:src/app.ts | grep -c 'new Queue('51
Scheduled jobsgit grep 'scheduleLocked(' origin/master -- src/app.ts | wc -l50
Check-in workersawk over the exported worker map in src/workers/ac.ts, origin/master12
Locales, one front-endthe locales array in i18n/config.ts, checkin-ai origin/main8

Stack used

Next.jsReactTypeScriptExpress.jsPostgreSQLPrismaBullMQRedisMantineOpenTelemetrySentryVitestAWS S3
Plate 1Contact

Legend — the marks on these sheets

SH-xx
Sheet number. Every drawing in a set carries one, and the set is read in that order.
ESC 1:20
Scale. One unit on the drawing stands for twenty on the thing drawn.
DETAIL A/B/C
Detail callout. A lettered part of a drawing, enlarged on a sheet of its own.
SECTION C-C
Section mark. The line a cut is taken along, lettered at both ends.
BH-01
Borehole log. What a trial hole found, recorded downward by depth.
EOB
End of borehole. The depth at which the log stops.
REV. 2026
Revision. The issue a sheet belongs to; a later revision supersedes it.
As-built register
A table of what was actually built, set against what was drawn.

Press ? in the title block to open or close. Escape closes.