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 · Plugins · all subjects

dodopayments/configuration

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

Dodo Payments environment variables required

Two environment variables are required for Dodo Payments integration: DODO_PAYMENTS_API_KEY (your API key) and DODO_PAYMENTS_WEBHOOK_SECRET (your webhook secret).

Dodo Payments client initialization

The DodoPayments client is initialized with a bearerToken set to the DODO_PAYMENTS_API_KEY environment variable and an environment property set to either 'test_mode' for testing or 'live_mode' for production.

Dodo Payments plugin server-side setup

The dodopayments plugin accepts the following configuration: client (required, DodoPayments instance), createCustomerOnSignUp (optional, auto-create customers on user signup), and use (required, array of plugins to enable including checkout, portal, and webhooks).

Dodo Payments checkout plugin configuration

The checkout plugin within dodopayments accepts: products (array of products with productId and slug, or an async function returning products), successUrl (URL to redirect after successful payment), and authenticatedUsersOnly (boolean, default false, requires user authentication).

Dodo Payments webhooks default endpoint

The default webhook endpoint for Dodo Payments is /api/auth/dodopayments/webhooks.

Dodo Payments webhooks plugin configuration

The webhooks plugin within dodopayments accepts: webhookKey (required, the webhook secret from environment variables) and onPayload (async callback function that receives the webhook payload with an event_type property).

Give your agent this brain