JuanClick Facebook login — activation handoff 9 November 2026 · Asia/Manila Status: prepared integration; NOT activated. The JuanClick Meta app has been created. Website, app domain, privacy and deletion links, icon, Facebook Login permissions (public_profile/email), callback and JavaScript SDK settings have been saved. Meta confirmed the callback is valid. A new JuanClick business portfolio was created and linked successfully; it is unverified. Public activation awaits Meta business verification and required review. Provider credentials have not been installed. Owner-specific account details and evidence are recorded privately in the JuanClick Google Drive master record. Website: https://juanclick.ph/ App domain: juanclick.ph Exact valid OAuth redirect: https://juanclick.ph/oauth.php?provider=facebook Privacy: https://juanclick.ph/privacy.html Data deletion instructions: https://juanclick.ph/privacy.html#data-deletion Allowed JavaScript SDK origin: https://juanclick.ph/ Saved security settings: client/web OAuth enabled; HTTPS and exact redirect matching required; JavaScript SDK enabled; forced password reauthentication, embedded-browser OAuth and device login disabled. Only public_profile and email requested. Next: complete the new JuanClick portfolio’s verification and required review, confirm supported Graph API version and public/non-role access, and store App ID/App Secret/redirect/version in the existing server-private Facebook provider entry while preserving Google. Never paste passwords or the App Secret in chat or publish them in HTML, JavaScript, URLs, screenshots or release artifacts. Validate provider acceptance before enabling the public button. Prepared behavior: Facebook's official SDK can show a browser account picker and eligible returning-user prompt, with explicit OAuth fallback. Automatic prompts defer while sign-in details are being entered. The user approves sharing their Facebook identity; JuanClick never receives the Facebook password. A web/PWA cannot guarantee access to a session held only inside the native Facebook phone app. Before enabling: test an app-role and a permitted non-role user, new registration, linked sign-in, conflicting-email recovery without automatic linking, cancellation, blocked cookies/SDK, expired/wrong-app tokens, CSRF/state rejection, Android/iPhone browsers, Safari fallback, keyboard and screen-reader behavior. Use dedicated test accounts. Marketplace phone/ID verification remains a separate pending integration. Official documentation inspected: https://developers.facebook.com/documentation/facebook-login/web/fedcm/ https://developers.facebook.com/blog/post/2026/08/27/new-from-facebook-login-beta/