Stripe

Orchard does not process payments on your behalf — each tenant brings its own Stripe account. Paste your API keys below, then click Test connection to verify. Get keys at dashboard.stripe.com/apikeys.

Webhook endpoint

Paste this URL into your Stripe dashboard under Developers → Webhooks → Add endpoint. The signing secret that Stripe returns goes into the form below.

Test mode

Not configured

Admin
Settings
Integrations
Stripe

Stripe

Webhook endpoint

Paste this URL into your Stripe dashboard under Developers → Webhooks → Add endpoint. The signing secret that Stripe returns goes into the form below.

Test mode

Not configured

Live mode

Not configured

Save Stripe credentials

Test connection

Test-mode routing

Routes storefront Stripe calls to your test credentials for the duration of the token (4 hours). Production default is always live. Each flip writes an audit row.

Warning:

Test credentials are not yet configured for this tenant. Mint a token below to test the routing path, but save test keys in the form above first to exercise an actual checkout.

Integration mode

Direct (tenant's own Stripe account)Connect (Orchard platform account)

Direct is the standard path. Connect is reserved for tenants opted into Orchard's managed payment flow.

Stripe environment

TestLive

Secret key

Encrypted with AES-256-GCM in the per-tenant vault. Never displayed after saving — only the last 4 chars are kept in public_config for the redacted preview.

Publishable key

Webhook signing secret

From the endpoint you configured at the URL above. Required in both modes — signatures are verified per tenant.

Calls stripe.balance.retrieve() (direct mode) or stripe.accounts.retrieve(account_id) (connect mode) against the credentials currently stored for the selected environment. Nothing is written.

Environment

TestLive