Facebook Sign-in configuration
Configure Facebook Login for enrolment forms: create a Facebook App, set redirect URIs and allowed domains, then add the App ID in The Wallet Crew admin console.
Use this when you want to enable the Facebook button in an enrolment form.
Start with Social sign-in to understand the user flow. Then come back here for the provider setup.
Overview
What you'll set up
A Facebook App with the Facebook Login product enabled.
Allowed OAuth redirect URIs and valid domains for your enrolment form.
The App ID stored in The Wallet Crew admin console.
Prerequisites
Access to your brand's Meta for Developers account.
Permission to create or manage Facebook Apps.
The list of domains where your enrolment forms will run (prod + staging + dev + custom).
Create the Facebook App
Create a new App
Click
Create App.Select use case:
Authenticate and request data from users(orConsumerdepending on your Meta dashboard version).Set a name. Example:
neostore login.Complete the app creation wizard and confirm your developer account if prompted.
Add the Facebook Login product
From your App dashboard, find the Add a product section.
Click
Set upon Facebook Login for Business (or Facebook Login).Choose
Webas the platform.Enter your website URL (e.g.
https://app.neostore.cloud) and save.
Configure allowed domains and redirect URIs
Navigate to Facebook Login → Settings in the left sidebar and configure the following:
Valid OAuth Redirect URIs — add one URI per environment:
https://app.neostore.cloudhttps://app-qa.neostore.cloudhttps://app-dev.neostore.cloudAny custom domain you use for enrolment forms (add the exact origin).
Allowed Domains for the JavaScript SDK — add the same list of origins (scheme + host only, no paths).
Save your changes.
Note: Unlike Google, Facebook requires both the redirect URI and the domain allowlist to be filled in.
Switch the App to Live mode
In the top bar of the App dashboard, toggle the app from Development to Live.
If prompted, provide a Privacy Policy URL — this is required by Meta before going live.
While in Development mode, only users listed as testers or developers on the app can sign in. Switch to Live so all users can authenticate.
Info: Facebook Sign-In for web uses only the App ID. It is safe to paste it in the admin console.
Do not share your Facebook App Secret. You should not need it for this flow.
Add the App ID in The Wallet Crew
Open Social logins → Facebook in the admin console.
Paste the App ID from Meta for Developers.
Save.
Enable Facebook on your enrolment form
Enable the provider in the enrolment form settings.
See Enrolment form.
FAQ
Do we need a Facebook App Secret?
No. This setup uses the App ID only.
If you see an App Secret in Meta for Developers, don't paste it anywhere in Wallet Crew.
Should we configure "Authorized redirect URIs" in Facebook?
Yes — unlike Google, Facebook requires valid OAuth Redirect URIs to be explicitly listed.
Add each environment origin under Facebook Login → Settings → Valid OAuth Redirect URIs.
What exactly must be added as an allowed domain?
Add the origin only: scheme://host (and port if you use a non-standard one).
Examples:
✅
https://app.neostore.cloud✅
https://brand.example.com❌
https://app.neostore.cloud/molia/mobile(paths are not allowed)
We use a custom domain. What should we do?
Add your custom domain both to Valid OAuth Redirect URIs and Allowed Domains for the JavaScript SDK in the Facebook Login settings.
Use the exact domain users see in the browser. Example: https://wallet.brand.com.
Why do we list prod, QA, and dev origins?
Facebook validates the origin at runtime.
If a user hits QA but only prod is configured, Facebook rejects the sign-in.
Where do we enable the Facebook button in the user journey?
Provider setup is not enough. You must also enable Facebook on the enrolment form.
See Social sign-in and Enrolment form.
Last updated