Payment ledger is out of sync with the database schema
Admin payment transactions API returned 503 because the running Prisma client does not match the DB schema (e.g. unknown field such as staffReadAt).
Why this happens
Deploy/migrate applied schema changes without regenerating the Prisma client, or the web process is still on an old client. Not a member checkout error.
Diagnose and fix
1. On the app host, run the product-suggested fix: docker compose exec web npx prisma generate && docker compose restart web (adjust compose service name if yours differs).
2. Confirm migrations are applied (prisma migrate deploy / your usual migrate path) before regenerate if columns are truly missing.
3. Reload Payment transactions list; the ledger should load.
4. If it still fails, check deploy logs for Prisma generate errors.