Connecting Stripe Connect

Edited

Overview

Stripe Connect is how Chamberly orchestrates online payments while your chamber retains full ownership of its Stripe account and funds. You connect once, and Chamberly handles checkout sessions, webhooks, and refunds on your behalf.

Before you start

  • Confirm subscription is Pro or Premier under Settings > Billing.

  • Have ready: chamber EIN, bank account/routing for payouts, an admin's identity info.

  • Confirm the chamber's primary admin will complete the Stripe identity check.

Step-by-step

  1. Go to Settings > Payment.

  2. Click Connect Stripe.

  3. You'll be redirected to Stripe's hosted onboarding.

  4. Enter business details, tax ID, and bank info.

  5. Complete identity verification (driver's license or passport upload).

  6. Stripe redirects back to Chamberly with a success state.

  7. The Settings > Payment page now shows Stripe connected with a green status.

What happens next

  • Online payment becomes available immediately.

  • Chamberly subscribes to Stripe webhooks for your account so order statuses stay in sync.

  • Your chamber dashboard shows real-time payment activity from Stripe.

Tips & best practices

  • Complete identity verification quickly — Stripe holds payouts until verification finishes.

  • Use a finance team email as the Stripe primary contact so payout notifications go to the right person.

  • Enable Stripe two-factor auth for the underlying account.

FAQ

Can I use an existing Stripe account?
Yes. During Connect onboarding, choose Sign in to existing Stripe account.

What if onboarding fails halfway?
Click Resume Stripe onboarding from Settings > Payment to pick up where you left off.

How long until payouts arrive?
Stripe's standard schedule is two business days for the first payout, then according to your chosen cadence.

Related articles

  • Online payments with Stripe overview

  • Disconnecting or reconnecting Stripe

Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.