new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Better Auth · Authentication · all subjects

social sign-on/paybin

8 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Paybin OAuth setup prerequisites

To use Paybin sign in, create an OAuth 2.0 Client through your Paybin Portfolio application at https://portfolio.paybin.io. Log in, navigate to Developer Settings or OAuth Applications section, and click 'Create OAuth Application' or 'New Application'.

Paybin OAuth application fields

When creating a Paybin OAuth application, fill in: Application Name (the name shown to users during authorization) and Redirect URIs. After creation, copy the Client ID and Client Secret for your environment variables.

Paybin redirect URI configuration

For local development, set Paybin redirect URI to http://localhost:3000/api/auth/callback/paybin. For production, set it to https://yourdomain.com/api/auth/callback/paybin. If you change the base path of the auth routes, update the redirect URI accordingly.

Paybin provider configuration in Better Auth

To configure Paybin provider in Better Auth, import betterAuth and pass the provider with clientId and clientSecret to the socialProviders option. Example: socialProviders: { paybin: { clientId: process.env.PAYBIN_CLIENT_ID as string, clientSecret: process.env.PAYBIN_CLIENT_SECRET as string } }

Paybin social sign-in client implementation

To sign in with Paybin on the client side, use authClient.signIn.social({ provider: "paybin" }) from the Better Auth client.

Paybin default scopes

By default, the Paybin provider requests the following scopes: openid, email, and profile. These can be customized based on your application's needs.

Paybin custom scopes configuration

To customize Paybin scopes, pass a scope array to the paybin provider configuration. Example: scope: ["openid", "email", "profile", "transactions"]

Paybin user profile field mapping

Paybin returns user information in the ID token following OpenID Connect standards. The provider automatically extracts: id from sub claim, name from name, preferred_username, or email (in order of preference), email from email claim, image from picture claim, and emailVerified from email_verified claim.

Give your agent this brain