Stripe

What it enables in Codexa

• Store your Stripe secret key (and optional publishable key) encrypted in the workspace, with a connection test against the Stripe API.
• Keep the team's Stripe credentials in one place; copy them into project environment variables when a generated app needs Stripe Checkout or webhooks.

• test

Setup

Fields on the workspace connection form. Password-type fields are encrypted before storage and never shown again.

1. Open Settings → Integrations in your workspace (requires the admin or owner role).
2. Choose the provider, give the connection a name, and fill in the fields listed above. Secret fields are encrypted before they are stored and are never sent back to the browser.
3. Click Test connection. Codexa makes a single read-only request to the provider to confirm the credentials work.
4. Save. The connection is now available to projects in this workspace.

Required permissions and scopes

• A secret key (sk_test_… or sk_live_…) or a restricted key (rk_…). For the connection test a key with read access to the balance is enough.

Limitations

• This connection is separate from Codexa's own billing: paying for a Codexa plan does not require it.
• Codexa does not create products, prices or webhooks for you; the generated code does that against your account.
• Secrets are not injected into running sandboxes automatically; add them as project environment variables.