Stripe setup

Stripe integration (webhooks + testing)

Use Stripe webhooks so payments and downstream conversions reflect in your Refer Labs dashboard reliably.

Open dashboard

Required environment variables

Stripe requires server-side secrets and webhook signing to be configured in your deployment environment.

STRIPE_SECRET_KEY
NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY
STRIPE_WEBHOOK_SECRET

Validate configuration via the Status page.

Webhook endpoint

Stripe should send events to the webhook endpoint below (configured in Stripe Dashboard → Developers → Webhooks).

Webhook URL

https://referlabs.com.au/api/stripe/webhook

Testing checkpoints (do these in order)

Confirm Stripe env vars are set (Status page).
In Stripe Dashboard, create a webhook pointing to /api/stripe/webhook and copy the signing secret into STRIPE_WEBHOOK_SECRET.
Run a test payment (Stripe test mode) and confirm events deliver successfully in Stripe’s webhook logs.
Confirm the related transaction/commission data updates in the Refer Labs dashboard (admin analytics/payments pages).
If anything doesn’t appear, verify webhook signature errors first, then confirm event type support.

Common troubleshooting

401/400 signature errors: webhook secret mismatch between Stripe and Vercel env vars.
No events delivered: webhook URL typo or blocked by WAF/proxy.
Test vs live mismatch: ensure you set the correct keys and webhook secret for the mode you’re testing.

Optional: Stripe CLI quick test

# Login once
stripe login

# Forward events to your local server (development)
stripe listen --forward-to http://localhost:3000/api/stripe/webhook

# Trigger a test event
stripe trigger payment_intent.succeeded