Google Authentication
This guide walks you through setting up Google OAuth as a custom authentication provider for your UTXOS application.
Custom authentication providers are available on Pro and Scale plans. The Base plan uses UTXOS-managed Google credentials.
Prerequisites
- A Google Cloud account
- Access to the Google Cloud Console
- A UTXOS project on the Pro or Scale plan
Create Google OAuth Credentials
-
Navigate to the Google Auth Platform in Google Cloud Console.
-
Create a new OAuth 2.0 Client ID with the Web application type.
Google may require identity verification for your OAuth consent screen before your app can be used by external users.
- Configure the authorized URLs:
| Field | Value |
|---|---|
| Authorized JavaScript origins | https://utxos.dev |
| Authorized redirect URIs | https://utxos.dev/api/auth |

-
Click Create to generate your credentials.
-
Copy the Client ID and Client Secret. Download the JSON file as a backup.
Configure UTXOS Dashboard
-
Open the UTXOS Dashboard and select your project.
-
Navigate to Settings > Authentication.
-
Select Google from the provider list.
-
Enter your credentials:
| Field | Value |
|---|---|
| Client ID | Your Google OAuth Client ID |
| Client Secret | Your Google OAuth Client Secret |
-
Toggle Enable to activate Google authentication.
-
Click Save project settings.

Verify the Integration
-
Open your application and initiate the wallet connection flow.
-
Select Login with Google.
-
Complete the Google sign-in process.
-
Confirm you are redirected back to your application with an active wallet session.
Troubleshooting
”redirect_uri_mismatch” Error
The redirect URI in your Google OAuth configuration does not match the expected value. Verify that https://utxos.dev/api/auth is added exactly as shown, with no trailing slash.
”access_denied” Error
Your OAuth consent screen may be in testing mode. Add your test users in the Google Cloud Console, or publish the app for production use.
”invalid_client” Error
Double-check that you copied the Client ID and Client Secret correctly. Ensure there are no leading or trailing spaces.
Next Steps
- Enable Third-Party Authentication to use existing Google sessions
- Add additional providers to give users more login options