Builder Settings
Stripe Payments
Connect app-level Stripe configuration used by checkout and payment components, including environment mode, publishable key setup, product sync, and optional account mapping.
Free tier users see upgrade gating instead of editable settings.
Use matching publishable key type for the selected mode.
Product updates should be re-synced after Stripe dashboard changes.
Stripe configuration controls
Select payment environment
Switch between test and live mode depending on validation versus production charging workflows.
Store publishable key
Configure app-level publishable key (pk_test_... or pk_live_...) for frontend payment flows.
Optional account mapping
Set Stripe Account ID (acct_...) for account-level routing scenarios.
Sync product data
Pull product/price updates from Stripe to keep in-app commerce displays aligned.
Configure Stripe safely
Configuration flow
- Open App Settings & Deploy → Stripe Payments.
- Select test mode first.
- Enter publishable key matching selected mode.
- Optionally add Stripe Account ID.
- Save configuration and run product sync.
Go-live checklist
- Validate full checkout in test mode.
- Switch to live mode and provide live publishable key.
- Re-sync products before production release.
Common mistakes to avoid
Using mismatched key and mode
Ensure pk_test is used with test mode and pk_live is used with live mode.
Entering secret keys in Builder
This UI is for publishable config only; keep secret key handling in secure backend infrastructure.
Skipping post-change sync
After Stripe catalog updates, run sync so products and prices in app remain accurate.