Product updates

What's new
at Xicar

A clear record of product improvements, fixes, and operational updates, with the reason each change matters.

Browse updates

Latest updates

October 2026

₱1 cash-out policy, Celld Admin migration, Food & Mart order controls, and new service pilots

This October 10–18 organization-wide update covers work merged or committed after the October 10 changelog publication. The primary Ride Hailing, Wallet, Admin, and Food & Mart codebases advanced alongside separate Stays and Express development forks. Branch promotion, a release-version commit, and repository changes do not by themselves confirm a live deployment or app-store release.

Wallet cash-out now has a ₱1 floor and an editable policy

Wallet changed the default cash-out minimum from ₱100 to ₱1, while retaining the existing transfer-fee behavior and the standard ₱50,000 maximum. The minimum and maximum can now be administered through signed internal policy endpoints and persisted in a new wallet settings table. Withdrawal-channel responses expose the live policy, and invalid or below-₱1 amounts are rejected.

The Ride Hailing backend added signed admin GET/PATCH pass-through routes and clearer classification of Wallet authorization, missing-route, and upstream failures. The Waku/Hono Admin Finance screen can display the wallet-confirmed policy, edit the minimum, preserve unsaved changes, and show validation or connectivity failures. Corresponding fixes and tests were first completed in the Food & Mart forks, then brought into the primary Wallet, Ride Hailing, and Admin integration branches and promoted to main on October 13.

The ₱1 value is the default and allowed floor, not a forced reset of a previously saved higher threshold. Rollout still requires the wallet settings migration, matching service keys, and an explicit check of stored/environment overrides. These merges do not establish that live cash-out requests or previously observed HTTP 502s have been resolved in every deployment.

Ride Hailing hardened sessions and promoted the driver-credit rule

The driver online-credit eligibility calculation now considers regular credits plus promotional credits for the selected Xiclo or Xicar service. Promotions from unrelated service buckets do not qualify. This rule was promoted to Ride Hailing main on October 10 and applied consistently to driver preflight, backend go-online, post-trip, and administrative balance checks.

Authentication and session recovery changes merged into beta on October 12 and into main on October 13. Customer, driver, and attendant clients now distinguish recoverable connectivity or proxy failures from invalid sessions, reducing unwanted logouts. Refresh-token handling and shared client authentication helpers were also consolidated.

Repository release-version commits followed for customer v1.7.1, driver v1.8.1, and attendant v1.2.1 on October 13. The version commits do not certify publication to an app store.

Referral commission settings reached the primary backend

The Food & Mart development backend removed its additional Cloudflare-user-header requirement from HMAC-authorized referral settings updates. The primary Ride Hailing backend then added the missing signed GET/PATCH admin referral-settings proxy, forwarding configuration to the Affiliate service; this removes the missing-route gap behind the Admin referral-settings screen.

That backend change merged into Ride Hailing beta on October 13 and was promoted to main on October 17. The Admin main-branch integration includes the corresponding configurable referral commission UI. When a separately verified human identity is unavailable, request audit attribution remains tied to the authenticated dashboard service rather than an identified person.

Admin moved to Celld and expanded operations

Admin replaced its Next.js request-time application with Waku static pages and a Hono Worker API. The new deployment model serves prerendered dashboard routes, keeps backend credentials in signed same-origin server proxies, and introduces a guarded ride-refund path.

The integration also brings Food & Mart merchant application and store reviews, merchant moderation, delivery-fee and credit-hold settings, Rental operator/document/vehicle reviews, renter reports and support controls, Finance cash-out policy editing, Food & Mart driver-credit settings, referral settings, and editing a notification before resending it as a new message. Rental promotions remain sample/in-memory UI state, not persisted business configuration.

The migration entered beta on October 13 and main on October 17. Supporting changes moved check/deploy workflows to self-hosted Linux runners, fixed an IPv4/IPv6 mismatch that broke Waku prerendering on runners, and replaced the manual deployment ENV_FILE contract with Infisical-provided environment values. A successful GitHub merge is not a substitute for production navigation, Worker-proxy, secrets, and refund-flow smoke tests.

Food & Mart improved the merchant and dine-in experience

The Food & Mart API and merchant app added Find a rider now for scheduled delivery orders whose cooking finishes early, with a confirmation step before advancing dispatch. Merchants can also cancel dine-in, pickup, and delivery orders from active/upcoming views by supplying a reason. Delivery cancellation follows rider-state and refund safeguards, persists retry work, and keeps refunded orders visible in History.

The dine-in customer tracker gained live cooking and serving progress, including a four-step order status display, a preparation countdown, an overdue indicator, and a brief early-serving transition. The standalone dine-in web app also gained a deployable Coolify/nginx image and instructions for its development domain.

The merchant app gained adaptive phone, tablet, and desktop layouts. Private menu and storefront photos now load with the merchant’s authenticated session; photo saves wait for upload completion, and versioned web entry assets prevent stale Cloudflare caches from hiding deployed fixes. Merchant uploads gained a configurable S3-compatible/Cloudflare R2 storage driver alongside a guarded local storage option.

The cancellation flow requires database migration 0034_delivery_cancellation_requests and its scheduled retry/sweeper process. The cached-web and authenticated-photo fixes still require deployment and browser confirmation.

Food & Mart delivery and service-to-service integration were aligned

The Food & Mart Ride Hailing fork now lets a rider give back an order after arriving at the merchant, until pickup begins; its backend clears the arrival state before returning the order to dispatch. The fork also synchronized upstream Ride Hailing beta history twice while retaining its Food & Mart-specific workflows and adopting shared authentication/session fixes.

Across Food & Mart API, Ride Hailing, Wallet, Admin, and Affiliate integrations, service-key names were brought toward the matching FOOD-prefixed pairs and the X-Xicar-Service / X-Xicar-Key internal request headers. Wallet and Affiliate gained the corresponding Food & Mart caller configuration. These are configuration-contract changes: a deployed caller and receiver must use matching keys and URLs before the integrations can be treated as healthy.

Stays and Express advanced in separate development repositories

Direct commits to Xicar-Stays initialized the Stays merchant monorepo and made booking status and scheduling interactive from the merchant home screen. The ride-hailing-for-stays fork added customer Stays discovery, booking and wallet-payment integration, home-screen access, and supporting operational guidance.

The ride-hailing-for-express fork added customer parcel-booking and multi-stop routing flows, fare calculation, online-payment choices, courier booking/tracking features, a documented 15% Express commission implementation, and an expanded driver order board covering Express deliveries and Xiclo/Xicar ride requests. The latest board change raised its default search radius to 25 km and visually identifies distant pickup requests.

These are fork-specific development commits, not changes verified in the primary Ride Hailing main branch or released customer/driver applications.

Backend configuration, deployment, and engineering documentation improved

The Food & Mart backend adopted typed environment validation, URL-based Postgres/Redis configuration, consistent inter-service authentication contracts, and a database advisory lock to prevent concurrent startup replicas from racing schema migrations. Merchant mobile build configuration was reorganized under its app directory with development/beta/production build tooling. Stale repository assets and documents were removed.

Engineering documentation gained a verified repository catalog, getting-started guidance, shared service-key conventions, and Celld/Infisical deployment instructions. Operational checks still need to confirm that these documented environment contracts match the running applications.

References

Xendit rollout, admin controls, driver credit policy, and Food & Mart operations

The October 7–9 organization-wide changes, recorded on October 10, promoted the Ride Hailing and Wallet integration branches toward production, added operational controls for referrals and notifications, expanded Food & Mart merchant tools, and adjusted driver credit eligibility. This entry distinguishes changes merged to main from beta- and fork-only changes; a merge does not by itself confirm deployment.

Ride Hailing and Wallet promoted their Xendit integration to main

Ride Hailing merged the Food & Mart integration work into beta and then promoted the accumulated beta changes to main. The customer and driver wallet flows now use gateway-neutral hosted checkout for Xendit or PayMongo, confirm settlement from Wallet rather than browser redirects, support payment-app handoffs, and handle pending, failed, and unknown payment states more defensively.

Wallet added Xendit hosted cash-ins and payouts with verified webhooks, amount/currency/reference checks, reconciliation, and idempotent payout reversal recovery. Its main promotion also carries separate Xiclo, Xicar, and Food & Mart promotional buckets, promo-first eligible service-fee spending, and Food & Mart spend-status/void and refund safeguards for safe retries.

The Ride Hailing main promotion also included the updated booking payment state, cancellation-fee proximity checks, mobile push delivery improvements, and customer/driver app-update handling. Release-version commits followed for customer v1.7.0, driver v1.8.0, and attendant v1.2.0; these record repository version changes, not confirmation of app-store publication.

Wallet checkout returns now lead to backend-confirmed payment

The public Web repository added static wallet-checkout success and cancellation pages in beta and promoted them to main. The Food & Mart Wallet fork standardized both gateway return URLs on one public web origin, while the Ride Hailing fork polls the Wallet backend during checkout and on foreground resume. A successful browser return alone no longer marks a top-up as paid.

These changes require matching public return URLs, provider webhook configuration, queue processing, and payment reconciliation during rollout.

Driver promotions and the online-credit rule were updated

Admin main gained individual and bulk promotional-credit management, per-service balances, verified delivery-box eligibility controls, and configurable Xiclo/Xicar customer cancellation fees, pickup radius, and driver compensation.

A subsequent Ride Hailing beta fix on October 9 changed the online-credit threshold calculation: go-online, post-trip, and admin-eviction checks now use regular credits plus the matching Xiclo or Xicar promotional credits, rather than regular credits alone. Unrelated service promotional buckets do not count. This explicitly supersedes the regular-credit-only minimum-balance behavior described in the October 7 changelog for the beta branch; the change was not part of the October 7 main promotion.

Referral commissions and notification resends became configurable

The Food & Mart Affiliate fork introduced an editable default referral commission rate (initially 0.50%), preserving per-affiliate overrides and historical earnings. The Ride Hailing fork added signed admin endpoints to validate and forward changes to Affiliate, and the Food & Mart admin now exposes the rate in System Settings. Audit history identifies the authenticated calling service, not an individual administrator unless that identity is independently verified.

The Food & Mart admin and the primary Admin beta integration added Edit beside notification Resend. Editing preloads the old title and message, then sends a new notification or SMS without altering the original delivery record; targeting is resolved again at send time. Separately, Admin main removed the obsolete silent-notification UI and preserved the original client_app audience when resending a targeted notification.

Admin backend cleanup and driver-rating authorization were refined

The primary Admin beta integration removed unused local Postgres, Drizzle, and tRPC scaffolding and consolidated operational screens around the backend API. It also brought in cancellation settings, referral controls, notification edits, and manual driver-rating workflows.

In the Food & Mart Ride Hailing fork, HMAC-authenticated admin requests can save manual driver ratings, restrictions, reinstatements, and appeal decisions without requiring a Cloudflare user identity in development. When an individually verified Cloudflare identity is available, the Food & Mart admin forwards it for audit attribution; otherwise the backend records the authenticated dashboard machine.

A later primary Admin beta refactor removed that app’s unused Cloudflare JWT verification and identity forwarding. This is separate from the Food & Mart admin’s optional verified-identity behavior. Deployed browser routes and direct-origin exposure still require appropriate perimeter controls; HMAC is machine-to-machine authentication, not proof of the human administrator.

Food & Mart added merchant operations, receipts, and dine-in ordering

The Food & Mart admin now includes delivery-fee and order-limit settings, merchant application reviews with document previews, store approvals or rejections, merchant status management, store branches, and pending-approval counters.

The Ride Hailing Food & Mart fork added itemized digital receipts for rides and food orders, including totals, VAT and payment details, customer history actions, and queued email receipts after trip completion. It also persists the driver’s selected rider lanes.

Direct commits to the Food & Mart repository reorganized its merchant app and NestJS backend under apps/merchant and apps/backend, added a standalone apps/web-dine-in ordering experience, improved merchant-wallet retry feedback, and added store/table QR tooling. A follow-up Docker fix makes backend build dependencies available even when the deployment environment sets NODE_ENV=production.

Web delivery and CI infrastructure were adjusted

Web beta moved Celld Worker routing and environment validation into a typed Hono application, updated local and CI deployment configuration, and added one-day browser caching with ETag revalidation for stable image/icon assets. Web CI moved to self-hosted Linux runners.

Ride Hailing beta switched Linux jobs to self-hosted runner labels and kept iOS jobs on macos-graftery. A separate Web PR to promote the broader beta runtime changes to main remained open at this cutoff, so this entry does not present those beta-only infrastructure changes as promoted.

References

Referral signup, service-scoped promo credits, Xendit payments, and push reliability

The October 4–6 organization-wide update moved several beta and Food & Mart workstreams forward at once: the public referral flow went live in the consolidated web app, Wallet became the single runtime authority for driver credits, promotional credits gained service isolation and verified-rider targeting, the Food & Mart fork added Xendit support, and the mobile notification path received a broad reliability pass.

Referral signup is now part of the main XICAR web experience

The public web app now includes the referral signup flow at /refer, with referral-code validation, OTP verification, account creation, existing-account handling, and the Google Play handoff.

Legacy referral URL formats redirect into the canonical route, and the browser talks to Affiliate through a same-origin proxy instead of receiving Affiliate service credentials directly. The web deployment path also gained GitHub Actions CI/CD, Infisical-backed environment configuration, Celld routing, stricter security headers, and immutable caching for static Next.js assets.

Xicar Wallet is now the runtime source of truth for driver credits

Ride Hailing removed the remaining runtime dependency on its legacy credit implementation. Driver balance reads, top-ups, payouts, and transaction history now flow through the Wallet-backed driver controller, while the released /api/driver/credits* routes remain as compatibility aliases.

The customer wallet is also no longer hidden behind the old WALLET_RIDES compile-time flag. Wallet navigation is available as a normal app surface across flavors, and wallet deep links now land on My Wallet instead of accidentally switching to My Account.

Driver-side wallet reads were updated to the canonical wallet APIs, and the Wallet service now reconciles stale PayMongo cash-ins until they reach a terminal state. Expired checkout sessions are represented as failed/expired rather than remaining indefinitely pending.

Promotional credits are isolated by service and do not replace the driver reserve

Wallet now supports separate promotional balances for Xiclo, Xicar/Car, and Food & Mart. Eligible service fees consume the matching promotional balance before ordinary credits, but promotional credits remain non-withdrawable and cannot satisfy the driver’s minimum primary-credit requirement.

A driver with less than the configured primary reserve cannot go online even when a large promotional balance exists. Promo grants also stay inside their selected service bucket instead of repaying generic outstanding debt created by another service.

The admin experience now exposes promotional balances, standard-vs-promo adjustments, and bulk promotional grants. Food & Mart targeting is restricted to approved two-wheel riders whose delivery box is explicitly present and approved, instead of treating every Xiclo rider as a Food & Mart delivery rider.

Food & Mart adds Xendit behind the wallet gateway boundary

The Food & Mart wallet fork now supports Xendit alongside PayMongo through the payment-gateway adapter. Xendit cash-in validates the provider reference, PHP currency, and paid amount before crediting the ledger. Cash-out keeps funds held before provider dispatch, exposes only configured payout channels, releases holds on terminal failures, and restores principal plus fee idempotently when a completed payout is later reversed.

Refund, payout, and session failures now use provider-safe structured logs without copying raw upstream responses or secrets into application errors. Existing PayMongo reconciliation behavior remains in place.

The Ride Hailing Food & Mart fork uses the shared hosted-checkout flow for Xendit-compatible customer and driver payments, treats checkout return as unconfirmed until wallet status is checked, supports payment-app deep links, and keeps retryable failed attempts recoverable. The code is merged, while live Xendit sandbox transactions and device payment-app handoffs remain rollout validation items.

Driver payment presentation is clearer during booking and navigation

Food & Mart driver booking offers now show estimated earnings without exposing deduction details in the popup.

During an active cash ride, the driver sees the amount to collect together with total earnings and the collection reminder. For online-paid rides, the navigation screen shows total earnings without presenting a passenger cash-collection container.

Push notifications were hardened from native configuration through delivery

Customer, driver, and attendant apps now rely on their native Firebase service configuration as the runtime source of truth, with a shared push-registration lifecycle while preserving each app’s own presentation behavior.

Admin-originated notifications are explicitly visible: the silent-delivery option was removed from the admin UI and backend delivery contract. Scheduled notification handoff is now transactional so queue failures do not silently lose an occurrence, and transient Firebase failures retry only the affected tokens instead of resending to successful recipients.

FCM token ownership was also tightened so one exact token has one current account owner while separate customer, driver, and attendant installations remain independent destinations. Duplicate multicast inputs are removed, stale sender-mismatch registrations are pruned, and registration remains idempotent under repeated updates.

Driver booking offers no longer use phone-call/CallKit semantics. Foreground offers stay in the normal booking UI, while background and terminated delivery uses the high-priority booking notification and opens the in-app offer when tapped.

Mobile updates, CI, and repository maintenance were simplified

Customer and driver soft-update checks now run reliably across cold start and foreground resume, retry transient store failures, serialize concurrent checks, and avoid repeatedly presenting the same successful iOS update in one process.

Mobile CI moved to the current Infisical secret layout, added the Food & Mart dev-flavor distribution path, and then aligned fork builds with the fork’s beta branch while keeping primary beta workflows scoped to the main Ride Hailing repository. Production release recovery was simplified to select the latest merged app release tag automatically.

The Admin repository absorbed the mirror’s missing history and later removed its unused local Postgres/Drizzle/tRPC scaffold, keeping the dashboard aligned around the backend Admin API. The Food & Mart Ride Hailing fork was also resynchronized with upstream beta; follow-up ancestry-only merges repaired the Git history after squash merges without introducing extra product changes.

References

Post-trip credit enforcement, completed-ride recovery, and legacy wallet migration

October 3 hardened the driver credit boundary after completed rides, fixed customer recovery when a trip finishes while the app is closed, and prepared Xicar Wallet to import legacy driver credit positions without changing their financial meaning. The iOS build pipeline also moved to the Graftery macOS runner scale set.

Driver credit minimum is enforced after trip settlement

For cash and other direct-collected rides, the Ride backend now keeps the driver out of matching while the platform fee settles and then rechecks the canonical wallet balance before making the driver available again.

If the resulting credits fall below the configured MinimumDriverBalance, or the wallet is restricted or has outstanding fees, the backend removes the driver from Redis/GEO matching before notifying the app. The driver app receives the forced-offline state over WebSocket so the UI updates immediately instead of waiting for the next wallet poll.

At the current ₱50 minimum, ₱50.00 remains eligible to stay online while ₱49.99 is forced offline. The same server-side availability rule is applied across driver, admin, and watchdog trip-completion paths.

Completed rides recover cleanly after an app restart

The customer app now keeps active-booking and completed-ride cache state separate. On a cold launch it reconciles the cached ride against the server context, so a trip that completed while the app was closed can return as one display-only completed card instead of being incorrectly restored as an active or pending ride.

A recovered completion also queues the rider-rating obligation, while completed and history screens are prevented from re-registering themselves as active rides. Submitting a rating, receiving a terminal rating response, or choosing “Not now” retires the recovery card so it does not interfere with the customer’s next booking.

A same-day follow-up fixed the Dart cached-state variable shadowing that blocked the customer beta build. That follow-up changes no behavior; it only restores compilation for the completed-ride recovery work.

Wallet can import legacy driver credit positions without consuming earnings

Xicar Wallet now has a Ride-only internal migration path for signed legacy driver credit balances. Positive legacy balances clear existing outstanding debt first and then become credits. Negative legacy balances consume available credits first and place the remainder into outstanding debt.

The migration deliberately does not consume or create driver earnings, and repeated imports are idempotent through the wallet transaction key. This prepares Wallet for the Ride-side legacy credit migration while preserving the historical meaning of each driver’s credit position.

iOS CI now uses the Graftery macOS runner scale set

The reusable iOS build workflow now targets the macos-graftery runner scale set instead of the previous Tartelet-style runner group and label selector. Android and Linux runner selection is unchanged.

References

Dynamic payment methods, refund-to-source flows, and clearer wallet errors

October 2 expanded online payment handling across the customer app, wallet, and admin dashboard, while making cancellation refunds and payment failures clearer and safer for customers and operators.

Safer payment errors and provider observability

Customer and driver wallet flows now translate backend payment failures into clear client-facing messages instead of surfacing raw provider or exception text. Top-up, online ride payment, cancellation payment, and cash-out failures keep the customer-facing wording actionable while client diagnostics are limited to safe metadata such as the operation, HTTP status, backend error code, request ID, and retry uncertainty.

The wallet service now records more detailed PayMongo webhook and provider diagnostics for payment, payout, transfer, refund, and checkout events. Provider-specific details stay on the server side, giving operators better visibility without exposing sensitive upstream errors in the mobile applications.

Online payment methods become dynamic

Online methods are no longer hardcoded as GCash-only in the ride flow. The customer app asks the backend for the currently available methods for ride payment and wallet top-up, while xicar-wallet owns the payment-method records and validates availability during checkout.

The admin dashboard now has a Finance > Payment Methods page for viewing and controlling the methods exposed by the wallet service. Ride refund dialogs also use the actual payment-method name instead of assuming every online refund is GCash.

The controls were further separated by purpose: each online method can now be enabled independently for ride/payment use and for wallet cash-in. The customer top-up screen follows the cash-in setting, while ride payments, tips, and fee payments follow the payment setting. Admin status labels show whether a method is available for rides, cash-in, both, or neither.

Cancelled online rides return the fare to its source

When an online-paid ride is cancelled, the held fare can now be released back toward the original payment source instead of simply becoming wallet credit. QR Ph refunds can carry a claim link that the customer opens from wallet history.

Follow-up handling made the result authoritative and easier to explain. The full fare is returned independently of any cancellation fee, with the fee owed separately. The ride backend can ask the wallet whether the refund was sent to the provider, requires a QR Ph claim, fell back to wallet credit, is still pending, or has no refund action.

The customer app waits briefly for that status after cancellation and reports where the money actually went instead of promising a GCash refund when the provider rejected it. If a ride fails to find a driver, the paid fare can remain held briefly for a retry before being returned.

Checkout and multi-stop fare calculation are revalidated before payment

Online ride checkout now returns to an authoritative-fare flow: route and fare are calculated first, the displayed fare is revalidated, and one checkout is created for exactly that fare before driver matching. The previous multiple-payment or pay-the-difference path has been removed.

Multi-stop Xicar pricing now applies the configured minimum fare before adding the flat intermediate-stop fee. With a ₱70 minimum and a ₱20 per-stop fee, one added stop therefore produces ₱90 instead of allowing the stop fee to be absorbed by the minimum-fare floor.

References

Referral web consolidation, driver credit safeguards, and shared service hardening

October 1 brought the referral experience into XICAR Web, tightened driver wallet safeguards, and aligned the Ride, Wallet, and Affiliate services around a more consistent deployment and authentication contract.

Referral signup joins XICAR Web

Referral signup now lives under the XICAR Web application at /refer. The browser keeps using same-origin routes while the Celld Worker forwards the referral requests to Affiliate with an authenticated Web service identity, so the Affiliate service can preserve per-visitor rate limiting without trusting arbitrary forwarded-IP headers.

The existing referral flow remains intact: invite codes are validated before signup, OTP send/resend behavior is preserved, Philippine mobile numbers are normalized, customer names are collected, and successful Android signups continue to the XICAR Play Store listing.

Several same-day follow-ups hardened that rollout. Celld deployment now bootstraps the required esbuild binary explicitly, referral invite routes no longer lose their code during HTML canonicalization, and the Web repository was simplified into a single Next.js application instead of separate marketing and referral apps. The canonical referral URL is now /refer?code=..., while older supported link shapes continue to redirect into that flow.

Infisical remains the source of truth for Web build-time and Worker runtime configuration, including the Web-to-Affiliate service credential.

Driver credit safeguards and wallet visibility

Ride-hailing now enforces the configured ₱50 minimum driver credit balance before a driver can go online. The driver app also rechecks wallet state while online and after trips, automatically taking a driver offline when the balance falls below the threshold. Administrative credit deductions can remove an affected driver from active matching state immediately.

A same-day follow-up fixed a backend dependency-resolution regression in the go-online path so drivers with sufficient credits can pass the wallet check normally.

The wallet integration also expanded the administrative transaction feed and moved eligible trip earnings, tips, incentives, and referral commissions to immediate availability after settlement. GCash refund-to-source support was added with wallet-credit fallback when the provider cannot complete the refund.

The admin driver-credit dialog was also adjusted so its header and action buttons remain visible while only the body scrolls, including on smaller viewports.

Referral links and profile counts become server-driven

Affiliate now returns the referral URL and the referral/earnings counts in the fields consumed by the customer and driver applications. The customer app uses that server-provided URL for display, sharing, copying, and QR generation instead of compiling the referral domain into the mobile build.

Affiliate also owns the final referral-link construction from the configured public Web origin. This makes a referral-domain change an environment/deployment change rather than requiring a new mobile release.

Shared service authentication and database startup

Ride, Wallet, and Affiliate now use explicit shared credentials per service pair instead of legacy generic or fallback service keys. Caller identity remains explicit through the XICAR service headers, while each pair uses the same canonical secret name on both sides.

The three Laravel services also aligned their PostgreSQL startup behavior. Application traffic can use PgBouncer when configured, while startup migrations use the direct PostgreSQL connection and remain owned by the web process. Queue and scheduler roles do not compete to run migrations.

References

September 2026

Driver matching and location heartbeat reliability hardened

Ride matching is now more resilient when driver notifications, WebSocket delivery, or location heartbeats fail under real production conditions.

Production telemetry showed two related problems: nearby drivers could appear stale or missing during matching, while the driver location endpoint was also returning rate-limit responses. The matching path could additionally leave an offer active without timely recovery if notification delivery or timeout scheduling failed.

Safer driver offer delivery

Driver offers now establish their recovery timeout before any notification is delivered. WebSocket and FCM delivery share the same server-owned deadline and recheck that the offer still belongs to the same driver before sending, so expired or reassigned offers are suppressed instead of reaching a driver after the booking has already moved on.

If the timeout cannot be scheduled, the backend attempts to return the booking and driver to their searchable/available state and suppresses notification delivery so matching can retry cleanly. The FCM fallback is also queued before the synchronous WebSocket attempt, preventing a WebSocket failure from removing the fallback path.

Already-released clients remain compatible with the new deadline handling: delivered WebSocket offers keep a minimum one-second timeout value instead of emitting zero, which older clients interpret as a missing timeout and replace with a fresh 15-second countdown.

More reliable driver heartbeats

The driver home screen now uses LocationQueue as the single continuous location sender instead of submitting the same heartbeat through two paths.

The backend temporarily raises the per-driver location limit from 60 to 120 updates per minute to give already-released duplicate-sending clients additional headroom during the transition. Rate-limit and server-error responses are no longer treated as successful heartbeats, helping the client retain an accurate view of whether its location session is actually healthy.

Together, these changes reduce false stale-driver rejection during matching and make offer recovery less dependent on notification delivery succeeding at exactly the right time.

No database or Redis schema migration is required, and the hotfix does not change search radii, offer duration, active-driver freshness windows, retry counts, driver ordering, or wallet behavior.

References

Wallet, payments, referrals, and the XICAR web platform converge

September 29 brought the ride, wallet, affiliate, referral, and web surfaces closer together around a shared payment and referral architecture.

Ride payments now use xicar-wallet as the source of truth for held fares, settlement, refunds, tips, cancellation credits, and recovery. Payment choices were expanded so GCash rides can be paid directly at booking, tips can use Cash, XICAR Wallet, or GCash, and cancellation fees can be settled through the wallet or GCash. Driver trip earnings use a configurable hold period and become withdrawable after 15 minutes once the related ride has finished settling.

The customer beta app also enables the My Wallet tab by default so testers can exercise wallet balance, top-up, withdrawal, and ride-payment flows. Follow-up fixes repaired beta compilation after the payment and referral reconciliation and preserved withdrawal request IDs across ambiguous retries so repeated requests remain idempotent.

Referral sign-up moves behind Affiliate

The referral sign-up flow now separates public referral handling from ride-account creation. The referral web calls Affiliate for invite validation, OTP orchestration, account sign-up, and referral binding, while the ride backend keeps only the internal operations it uniquely owns.

Affiliate also gained durable commission delivery and reversal behavior. Failed commission deliveries can be retried, refunded rides can reverse their commissions, and wallet calls use deterministic request identities so the same operation is not applied twice.

The standalone referral page remains the current customer-facing referral surface. It validates invite codes before requesting an SMS and uses Affiliate as its backend instead of relying on the mobile app login flow.

XICAR web moves to Celld

The former marketing repository is now the broader Xicar-PH/web surface. The existing marketing application has been moved into apps/marketing as the first workspace application, while deploy/web acts as the shared composition layer for the final web artifact.

The web deployment path now uses Celld for both beta and production fleets. GitHub Actions builds the static site, keeps beta and production deployments isolated, and publishes the selected artifact to the corresponding Celld-backed fleet storage.

This structure prepares the repository to host additional XICAR web applications alongside marketing, including the referral experience and shared-ride detail pages. Those applications have not been moved into Xicar-PH/web yet; the September 29 work establishes the repository and deployment boundaries needed to add them without creating separate deployment stacks.

Ride reliability fixes

The same integration work also repaired multi-stop route and fare calculation for rides with intermediate waypoints and added the missing payment columns required by the online-payment flow, preventing schema mismatches during ride creation.

References

Ride-hailing improves discounts, ratings, wallet groundwork, and production delivery

Ride-hailing now applies the single best eligible location discount to a fare instead of combining competing promotions. The selected discount is reflected consistently in customer and attendant quotes and bookings, usage limits are rechecked during booking creation, and attribution is preserved for admin reporting.

Production booking migration stabilization

The transition to normalized booking_stops was hardened through a series of production fixes for mixed-version deployments. Customer and attendant booking creation temporarily keep legacy endpoint fields synchronized with booking_stops, while reads can fall back safely when older rows do not yet have stop records.

The migration path now accepts historical routes whose optional place IDs are missing when their coordinates still identify the same endpoints. Long-running historical stop reconciliation was moved out of application startup so web containers can begin serving without waiting for an unbounded backfill.

Startup migration ownership was returned to the web role, health-check timing was restored to the normal deployment window, and matching jobs now strip loaded Eloquent relations before entering the queue so older workers do not fail when newer producers know about the stops relationship.

An explicit route compatibility boundary now normalizes supported legacy and current booking requests into the canonical route model and presents a compatible response shape for deployed customer and driver versions. Together, these changes keep the stop migration additive rather than requiring an all-at-once backend cutover.

Wallet and referral groundwork

The ride-hailing mirror merged the broader customer and driver wallet, referral, commission, cancellation/refund, and driver-onboarding groundwork. This introduced the application surfaces and backend integration points that the settlement, payment-choice, and Affiliate-backed referral work built on the following day.

The mirror beta history was also synchronized with the corresponding ride-hailing beta history without resetting mirror-only changes, keeping the two lines of work aligned before the larger payment and referral reconciliation.

A stale import of the discontinued device-security service was removed from the customer referral service, restoring the Customer Beta Android build without bringing the removed security-tracking implementation back.

Rating experience

Customer rating prompts are less intrusive and more predictable. The home screen only prompts once per app run for the most recent eligible completed ride, while ride history now opens the rating sheet immediately and loads any missing driver details in the background. This avoids repeated prompts and removes the wait before a customer can start rating from history.

Attendant Android production distribution

The attendant Android production build is now prepared for Firebase App Distribution instead of Google Play Internal Testing. The workflow builds a production-signed APK, derives the Firebase app ID from the production configuration, and temporarily disables attendant production iOS while leaving other mobile production delivery paths unchanged.

Admin discount management

The admin location-discount form now explains maximum discount and usage-limit fields more clearly. API validation or save errors stay visible in the open modal instead of silently closing it, while true network failures continue to use the existing offline queue behavior.

References

Canonical ride-hailing promotion and production deployment hardening

The ride-hailing mirror beta history was promoted into the canonical Xicar-PH/ride-hailing repository while preserving both histories. This moved the accumulated beta work back into the primary repository without flattening or discarding the independent main-branch commits.

Production migration ownership and health checks

The backend deployment model was tightened around explicit migration ownership. Ride-hailing, wallet, and affiliate now keep startup database migrations on the web role instead of allowing every long-running container to compete for the same migration gate.

For ride-hailing, startup work was reduced so queue and scheduler processes can reach their actual workloads without waiting behind web migrations. The web health-check window was also adjusted for migration-aware startup behavior.

Wallet queue and scheduler images were hardened for Coolify by removing the inherited web-server health probe and adding explicit health checks suitable for their long-running worker roles. This prevents healthy worker containers from being rolled back simply because they do not expose the FrankenPHP/Caddy port used by the web image.

Service configuration cleanup

Wallet deployment configuration was simplified around the active PostgreSQL and service-authentication contract, including direct and optional pooled database URLs and explicit wallet service credentials. Wallet and Affiliate integration documentation was also updated so the expected service-specific credentials are clearer across the ride, wallet, and affiliate boundaries.

Ride-hailing backend removes unused GraphQL surface

The ride-hailing backend removed its unused Lighthouse and GraphQL scaffold, leaving the service focused on its existing REST and WebSocket interfaces.

The removed layer only exposed the default GraphQL hello query and was not used by ride-hailing business operations or mobile clients. Removing it also drops the associated Composer dependencies, schema validation step, configuration, environment settings, resolver, and GraphQL-specific tests.

A regression test now verifies that the backend does not expose a /graphql endpoint or GraphQL route name. No database migration, REST contract, or WebSocket contract changed as part of this cleanup.

Safer trip completion and booking-stop rollout

Trip completion now protects against delayed retries accidentally closing a driver’s newer ride. When a booking ID is supplied to the end-trip request, that booking is validated and takes precedence over the driver’s current Redis assignment.

Recovery handling was also strengthened so pending driver benefits can be retried independently of driver cleanup. Campaign redemption failures now keep the durable recovery marker active instead of being acknowledged as completed, allowing the reconciler to retry benefit publication safely.

Completed trips now keep route-stop progress synchronized during settlement, and scheduled-booking details remain restricted to the intended driver while preserving the expected pre-acceptance flow for immediate bookings.

The rollout of the normalized booking_stops model was made safer for mixed-version deployments. Legacy pickup and drop-off columns are retained for a compatibility release, new writes keep both representations synchronized, reads can fall back to legacy endpoint data when stop rows are missing, and Redis search state is rebuilt through the same compatibility accessors. A repair migration restores and backfills legacy endpoint columns in environments where they were already removed.

References

Backend containerization, service hardening, and private image registry preparation

We prepared the backend deployment path for container-based builds and future image publishing.

A Zot container registry is now available at registry.xicar.net. This gives the platform a private registry endpoint that can be used by upcoming backend image build and deployment workflows.

The ride-hailing, wallet, and affiliate backends also merged their new production Docker implementations. The updated container setup standardizes the Laravel services around production-ready images, with role-specific runtime targets where applicable and serialized startup migrations to avoid competing schema changes during concurrent container starts.

The ride-hailing backend additionally merged updated development and production environment templates for the wallet and affiliate integrations. The documented contract now includes the required wallet service key and affiliate service settings, while keeping those service credentials backend-only.

Ride-hailing booking and attendant safeguards

Customer-visible driver details are now tied more strictly to the driver actually persisted on a booking. Before acceptance, offer recipients are hidden from the customer, and cached driver metadata is only used when it matches the accepted booking owner. Reassignment also clears stale driver and tracking state so the customer experience follows the latest booking ownership.

The attendant application now requires explicit API and WebSocket runtime configuration instead of silently falling back to defaults. Local setup is consolidated around the example environment contract, reducing the chance that a build points at an unintended backend.

Wallet backend cleanup

The wallet service removed unused Node.js, Vite, and Tailwind scaffolding from its Laravel backend. Development and container workflows are now PHP-only, reducing build dependencies while preserving the existing API routes, JSON status response, health endpoint, and wallet runtime behavior.

Affiliate backend cleanup

The affiliate service removed unused Node.js, Vite, and Tailwind scaffolding from its Laravel backend and replaced the stock browser welcome page with a JSON service-status response. API routes, Swagger support, and the existing health endpoint remain intact while the runtime and development setup no longer depend on unnecessary frontend tooling.

Changelog sharing metadata

The changelog site now ships its own favicon and social-preview image from repository-owned assets. Open Graph and Twitter/X metadata use those local assets so shared changelog links can render a consistent preview without depending on an external avatar image.

References

Driver ratings and ride-service restrictions

Administrative driver rating and ride-service restriction controls are now available end to end, with the matching ride-hailing backend enforcement merged alongside the admin interface work.

Driver ratings and service-level restrictions

The admin interface now shows driver ratings by ride service, including rating source and author attribution, and allows administrators to add ratings tied to either Xiclo two-wheel service or Xicar four-wheel service.

Administrators can also restrict a driver from a specific ride service without disabling the driver’s access to the other service. Restrictions can record a reason and optional supporting rating, and the admin interface supports reinstatement plus review of driver appeals.

Trusted Cloudflare Access identity is forwarded to the backend for these actions so administrative ratings and restriction decisions can be attributed to the authenticated administrator.

The ride-hailing backend now stores the added rating metadata, supports service-specific restriction records and driver appeals, and enforces active restrictions when drivers go online, receive offers, or attempt to accept bookings.

References

Attendant access, booking, and admin workflow improvements

This update brings tighter attendant access controls together with a smoother admin experience for managing day-to-day operations.

Attendant access and registration

Attendant registration now supports explicit pending, active, inactive, and archived account states. New attendants remain in an approval-pending flow until an administrator grants access, while disabled or archived attendants are prevented from continuing service operations.

The attendant app also rechecks account access while it is in use, so administrative changes can take effect without relying on a fresh sign-in. On the backend, duplicate phone checks are normalized, administrative attendant actions are HMAC-protected, and archived attendants retain their historical booking records.

Attendant booking and dashboard workflows

Attendant-created bookings now remain available for matching instead of being automatically cancelled when the normal driver retry budget is exhausted. The app surfaces driver acceptance notifications, keeps active booking status synchronized through WebSocket updates and targeted REST reconciliation, and shows a single completion or cancellation result even when duplicate lifecycle updates arrive.

The attendant home screen now uses a compact dashboard feed for pending, accepted, and trip-started booking counts plus online-driver availability. Booking history shows customer details while withholding assigned-driver information until acceptance, and booking cards expose the booking ID so attendants can match notifications to the correct trip.

Shared WebSocket subscriptions now track ownership per screen, preventing one screen from accidentally disconnecting another screen that is watching the same booking. The backend also batches online-driver session reads to reduce repeated Redis round trips during the dashboard’s periodic refresh.

Admin attendant management

The admin interface now supports editing attendant profiles, enabling or disabling access, archiving accounts, and restoring archived attendants. Booking filters can load the complete attendant list, including archived attendants where historical records need to remain identifiable.

Admin data views also gain clearer loading states, debounced search behavior, client-side sidebar navigation that preserves scroll position, and skeleton placeholders across major dashboard screens.

Scheduling, notifications, and exports

Notification schedules can now be edited, cancelled, and deleted with stronger schedule timing and app validation. Delivery failures are reported with partial fan-out retry details, while status refreshes provide clearer feedback.

Admin date and time rendering is standardized on Manila time, list searches are normalized and debounced, and full booking PDF exports now expose progress and can be cancelled. The admin Docker Compose default database is also updated to xicaradmin.

References

Introducing the Xicar changelog, wallet, and referral foundations

Xicar now has one place to follow meaningful product and operational changes.

Each update pairs what changed with why it matters, giving the team a shared, business-friendly record of progress without losing the technical details needed for traceability.

Infrastructure
Hugo-powered changelog site

The changelog site now runs on Hugo instead of the custom Python static-site generator. The existing design remains intact, while daily Markdown files, automatic date ordering, month grouping, and the static public/ output make ongoing publishing simpler and more consistent.

The migration also adds Hugo-based smoke checks pinned to version 0.147.7, preserving the site’s JavaScript-free output and validation of links, dates, headings, and security-sensitive content. Cloudflare Pages preview validation passed; production deployment status is not separately verified here.

Wallet and referral foundations

The wallet service gained its initial MVP implementation, establishing the foundation for customer and driver wallet operations that later ride-payment work builds on. PayMongo reconciliation was also extended to resolve payments by payment intent and release eligible tips immediately after successful reconciliation.

The Affiliate service introduced referral tracking and commission processing, establishing the first backend path for linking referrals and calculating referral-related commissions before the later cross-service referral flow was integrated.

References

Admin fare controls add service filtering and safer surge validation

The admin fare tools now make service-specific pricing and zone management easier to operate.

Location-discount analytics, location-discount maps, and surge-zone maps can now be filtered by service type, with each view remembering the selected filter. The “All service types” option is handled consistently across the discount and surge-zone flows so administrators can manage rules that apply across both Xiclo and Xicar.

Fare settings also now validate the fallback surge multiplier before saving. Values below 1.0 are rejected with an inline error instead of being silently coerced, while 1.0 remains the supported way to disable fallback surge outside configured zones.

These changes reduce ambiguity when reviewing service-specific fare rules and help prevent invalid fallback surge values from being submitted.

References