Google Sign-in configuration

Configure Google Sign-In (OAuth 2.0 Client ID) and connect it to The Wallet Crew social sign-in.

Use this when you want to enable the Google button in an enrolment form.

Connect with Google in an enrolment form example

Start with Social sign-in to understand the user flow. Then come back here for the provider setup.

What you’ll set up

• A Google OAuth 2.0 Client ID.

• Authorized JavaScript origins for your enrolment form domains.

• The Client ID stored in The Wallet Crew admin console.

Connect with Google in an enrolment form example

Prerequisites

• Access to your brand’s Google Cloud Console project.

• Permission to create OAuth 2.0 Client IDs.

• The list of domains where your enrolment forms will run (prod + staging + dev + custom).

Create the OAuth Client ID in Google

1

Open Credentials

Open the Google Cloud Console Credentials page:

Google Credential page

2

Create a Web application OAuth client

1. Click Create credentials → OAuth client ID.

2. Choose application type: Web application.

3. Set a name. Example: neostore login.

3

Configure origins

Add Authorized JavaScript origins for every domain you will use.

• https://app.neostore.cloud

• https://app-qa.neostore.cloud

• https://app-dev.neostore.cloud

• Any custom domain you use for enrolment forms (add the exact origin).

Leave Authorized redirect URIs empty.

Google OAuth client settings

Google Sign-In for web uses the Client ID. It’s safe to paste it in the admin console.

Do not share any Google client secret. You should not need one for this flow.

Add the Client ID in The Wallet Crew

1. Open Social logins → Google in the admin console.

Social logins -> Google

1. Paste the Client ID from Google.

2. Save.

Wallet Crew Google social login settings

Enable Google on your enrolment form

Enable the provider in the enrolment form settings.

See Enrolment form.

FAQ

Do we need a Google client secret?

No. This setup uses the Google Client ID only.

If you see a client secret in Google Cloud Console, don’t paste it anywhere in Wallet Crew.

Should we configure “Authorized redirect URIs” in Google?

No. Leave Authorized redirect URIs empty for this flow.

If you add redirect URIs, it usually doesn’t help. It can also confuse debugging later.

What exactly must be added as an “Authorized JavaScript origin”?

Add the origin only: scheme://host (and port if you use 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 as an Authorized JavaScript origin in Google Cloud Console.

Use the exact domain users see in the browser. Example: https://wallet.brand.com.

Why do we list prod, QA, and dev origins?

Google validates the origin at runtime.

If a user hits QA but only prod is configured, Google rejects the sign-in.

Where do we enable the Google button in the user journey?

Provider setup is not enough. You must also enable Google on the enrolment form.

See Social sign-in and Enrolment form.