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 page to enable the Google button in an enrolment form.

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

Connect with Google in an enrolment form example

Overview

What is set up here

• A Google OAuth 2.0 Client ID.

• Authorized JavaScript origins for the enrolment form domains.

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

Prerequisites

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

• Permission to create OAuth 2.0 Client IDs.

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

Configure Sign in with 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 in use.

• https://app.neostore.cloud

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

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

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

Leave Authorized redirect URIs empty.

Check that every origin is listed and that the redirect URI list is empty.

Check that the Client ID saved here matches the one issued by Google.

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. One is not needed for this flow.

Configure Google in The Wallet Crew

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

Social logins -> Google

The Wallet Crew - Google Social Sign In configuration

1. Paste the Client ID from Google.

2. Save.

Enable Google on the enrolment form

Enable the provider in the enrolment form settings.

Go into advanced configuration -> Layout. Open the layout where social sign-in should be activated and add these lines:

signinOptions:
  providers:
    - type: android
      displayProps:
        isMobile: true
        isAndroid: true

For more information see Enrolment form.

FAQ

Do we need a Google client secret?

No. This setup uses the Google Client ID only.

If a client secret appears in Google Cloud Console, do not paste it anywhere in The Wallet Crew.

Should we configure “Authorized redirect URIs” in Google?

No. Leave Authorized redirect URIs empty for this flow.

Adding redirect URIs 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 one is used).

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 the custom domain as an Authorized JavaScript origin in Google Cloud Console.

Use the exact domain customers 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 customer hits QA but only prod is configured, Google rejects the sign-in.

Where is the Google button enabled in the customer journey?

Provider setup is not enough. Google must also be enabled on the enrolment form.

See Social sign-in and Enrolment form.