₱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
- Primary Wallet / cash-out: Wallet #38, Wallet #40, Ride Hailing #278, #279, #280, Admin #103, #104.
- Authentication, driver credits, referrals: Ride Hailing #275, #268, #281, #282, Food & Mart Ride Hailing #30.
- Admin migration and controls: Admin #99, #101, #102, #105, #106, #107.
- Merchant, dine-in, and storage: API #21, #26, #27, #28, #29, #30, #31, #32, #33.
- Food & Mart forks and internal contracts: Ride Hailing fork #23, #24, #28, #29, #31, Wallet fork #7, Admin fork #11, Affiliate fork #2, API #22.
- Service pilots (direct commits): Stays customer, Stays merchant, Express backend/customer, Express commission, Express driver board, Express pickup radius.
- Engineering and docs: API #4, #5, #20, #23, #24, Docs #4, #7, #8, #11.