JuanClick 1.62.0 — Credit wallet preparation 8 November 2026 · Asia/Manila Open: https://juanclick.ph/credits.php Status: prepared for future use; live payments are NOT enabled. WHAT CHANGED - My credits page, reachable from the account menu and dashboard. - Private balance and top-up history views. Existing accounts receive no money or credits. - GCash connection panel and Top up credits action. Both show a persistent, viewport-visible popup explaining that setup is pending, with a Go to Show me recovery action. - Four-step, sample-only demonstration of linking, choosing a package, authorizing a payment and receiving confirmed credits. Includes Play/Pause, Back, Replay, Close, keyboard dismissal/focus restoration, readable steps and sample labels. The header Show me uses this page-specific demonstration. - Two empty storage tables with ownership, integer amount, duplicate request/reference and duplicate ledger-entry constraints; updated account-deletion data coverage. An empty wallet does not block deletion. If future payment records exist, deletion requires wallet review. - Payments fail closed in server code. No environment toggle, form input, fake success return or example payment can activate checkout. No Xendit credentials or customer wallet tokens are collected. - Existing installed-web-app identity and nonblocking background Update/Later checks retained. Website version incremented to 1.62.0. This is a web/PWA release, not a new APK or native package. USER DIRECTION Credits have no use for now. There are no actual prices, packages, credit spending, automatic top-ups or active wallet links. Demo amounts (100 demo credits / PHP 100) are examples only and are not an offer or chosen conversion rate. VERIFICATION 26 backend assertions cover empty balances, blocked writes, account isolation, duplicate reference/order constraints, ownership constraints and account-deletion coverage. Phone-sized Chromium viewports: 320x568 and 390x844. Desktop: 1440x1000. These are browser viewport tests on Windows, not physical-device tests. Browser checks cover balance/history privacy, CSRF rejection, forged payment inputs, persistent visible popups, recovery focus, both Show me entry points, sample Play/Pause/Replay/Close and no sample write requests. 44 transactional publication checks cover additive schema creation, original-data preservation, consistent private backup, rollback on injected failure, concurrent source changes and maintenance-lock ownership. All changed PHP/JavaScript sources receive syntax checks. Release packages contain source only, not private databases, sessions, keys or account records. NOT FINISHED / REQUIRED BEFORE REAL PURCHASES Xendit account recovery, merchant approval and GCash Link and Pay enablement; approved credit purposes/packages/prices; actual provider linking and unlinking; encrypted token storage; verified server-to-server payment status and authenticated callback handling; atomic exactly-once credit posting; pending/retry reconciliation; refunds/disputes; operational retention/account-deletion handling; sandbox and authorized live payment testing; physical Android/iPhone and manual screen-reader acceptance. The current schema constraints are a foundation, not a claim that the complete payment processing service is implemented. PORTFOLIOS No SimplerBooks or BizCore360 portfolio pages updated. MyApps receives only the JuanClick release entry and original verification captures. No promotional illustration generated.