Enabling Payments on a Weave Location
Why This Matters
Before you can test any payment write-back feature, you need a location with payments enabled. This lesson shows you exactly how to do that — including the Stripe onboarding flow — so you can set up your own test environments.
What You'll Learn
- What a payments-disabled location looks like in Weave (the 'payments not enabled' state)
- How to enable payments: the setup flow that redirects to Stripe
- What Stripe's role is: Weave uses Stripe for payment processing infrastructure
- The dev environment setup: using dev-environment defaults to enable payments on a test location
- Common issues during payments enablement (inactive state after setup) and why they occur
- How to verify payments are enabled and what the enabled state looks like
Watch Video
Lesson Summary
Enabling payments on a Weave location involves a Stripe onboarding flow. When you open the payments tab for a location that doesn't have payments enabled, you see a 'not enabled' state with a setup button. Clicking it redirects to Stripe's platform where you complete onboarding. In the dev environment, use the default Stripe test credentials. After completion, you're redirected back to Weave. The location should now show the payments tab with full functionality. If the location shows as inactive after setup, it's likely a dev environment-specific issue (as shown in the demo). Once active, the location can be used to test payment write-backs.