Connect Stripe payments
Use your own Stripe account to collect customer payments. Workspace payment settings are separate from your Stacks subscription billing.
Prepare access
An administrator opens Settings → Payments. In Stripe, choose the correct account and test or live environment. Keep your server-side API key private. Restricted keys should grant the operations required by the integration; inspect provider permission errors rather than assuming a key’s format proves access.
Save the connection
Enter the Stripe Secret Key. The Publishable Key field is optional for the current hosted-checkout integration. Save Changes stores the credentials; saving is not a completed payment test.
Configure the webhook
Create a Stripe webhook endpoint using the exact URL displayed on this workspace’s Payments page, including its account identifier. Follow the event guidance on that screen and paste the endpoint’s signing secret into Stripe webhook signing secret. The whsec_ signing secret is different from an API key; use the secret for the matching endpoint and environment.
Verify the full journey
Use a test environment before collecting live payments. Confirm checkout completes, the webhook is delivered and the corresponding Stacks invoice or booking updates. A return to the success page alone is not payment verification. Review setup warnings and provider logs if an update is missing.
Fees and records
Stripe controls processing charges and payout timing; consult its current account terms. Recording an offline payment, cancelling an invoice and refunding a Stripe payment are separate actions.
Official provider instructions
Reviewed against the application on September 11, 2026. Available actions depend on your role and workspace configuration.