Patreon

Members sign in with their Patreon account, in the system browser.

Before you start

Console	Patreon developer portal
Endpoint group	Social Login
Email	Returned, and verified — Patreon can match an existing account
Signs in	In the browser

Create the client

1. Open the Patreon developer portal and register a client.

2. Fill in the App Name, Description and App Category. Members read the name and description when authorising.

3. Set the Redirect URI to the address from Memberside → API Keys → Social Login → Patreon, which looks like https://yoursite.com/wp-json/memberside/v1/social/callback/patreon.

4. Set the API version to 2 if you are asked.

5. Copy the Client ID and Client Secret.

Sign-in uses the identity and identity[email] scopes, which return the member’s name and address.

Signing in is not the same as checking a pledge

This tells you who the member is on Patreon. It does not tell your site what they support you at, and it does not gate anything by tier — Memberside asks only for identity. Tier-based access is a job for a Patreon membership plugin on your WordPress site, which the app then reflects like any other role.

What to paste into Memberside

Under Memberside → API Keys → Social Login → Patreon:

Field	Value
Client ID	The Client ID
Client secret	The Client Secret

When it does not work

Symptom	Cause	Fix
“Invalid redirect_uri”	The address does not match the registered one	Copy it again
No email comes back	The client was registered against API version 1	Register it for version 2
A patron signs in with no membership	Sign-in carries identity only	Use a membership plugin on your site
The client secret stopped working	It was regenerated in the portal	Paste the new one