How to config stripe. Is this a bug?

[Novapixel1010]

This how I configure stripe to work. Everything I am using is in sandbox mode.

Cal.com version: 5.5.2

I open prisma at 192.168.1.213:5555 go to apps then stripepayment and insert in the keys space. As shown below:

{
  "client_id":         "ca_Sut6LBB1IjCHN",
  "client_secret":     "sk_test_51Rz3INJK5PbUErat3LKMQmhNkK2Pxh1qIJ6CD90bsOnn7YlhFyA00zyaVD55G",
  "public_key":        "pk_test_51Rz3INJK5PbUEr0kn1DztyJM5Vg7O2nE9xNXilO2xlcDx7LVIXC00pnGbMAr5",
  "webhook_secret":    "whsec_J8H6SdcLUTjrV6",
  "PAYMENT_FEE_FIXED": "0",
  "PAYMENT_FEE_PERCENTAGE": "0"
}

I striped some of the details and rotated the test keys. so really credentials will be longer

It almost worked until I got to the end of setting up the account and got this error:

@calcom/web:start: [Error: No authentication was provided. Send your secret API key using the Authorization header, or as a client_secret POST parameter.] { @calcom/web:start: type: 'StripeAuthenticationError', @calcom/web:start: raw: [Object], @calcom/web:start: rawType: 'invalid_client', @calcom/web:start: code: undefined, @calcom/web:start: doc_url: undefined, @calcom/web:start: param: undefined, @calcom/web:start: detail: undefined, @calcom/web:start: headers: [Object], @calcom/web:start: requestId: 'req_Oj8A1giIDLDj8T', @calcom/web:start: statusCode: 401, @calcom/web:start: charge: undefined, @calcom/web:start: decline_code: undefined, @calcom/web:start: payment_intent: undefined, @calcom/web:start: payment_method: undefined, @calcom/web:start: payment_method_type: undefined, @calcom/web:start: setup_intent: undefined, @calcom/web:start: source: undefined @calcom/web:start: }

So in the ENV variables I added STRIPE_PRIVATE_KEY="sk_test_51Rz3INJK5PbUErat3LKMQmhNkK2Pxh1qIJ6CD90bsOnn7YlhFyA00zyaVD55G" and it worked.

I have tried using just ENV variables but then stripe won't work at all. It wouldn't even let me install the app. This is the ENV variables I tried.

NEXT_PUBLIC_STRIPE_PUBLIC_KEY="pk_..."
STRIPE_PRIVATE_KEY="sk_live..."
STRIPE_CLIENT_ID="ca..."
STRIPE_WEBHOOK_SECRET="whsec_..."
PAYMENT_FEE_FIXED=0
PAYMENT_FEE_PERCENTAGE=0

Also the payment stays pending

The dashboard for stripe

[dosubot[bot]]

Stripe integration in Cal.com can be configured using both environment variables and the Prisma app keys under apps > stripepayment. ENV variables act as global secrets, while the database entry allows per-app overrides. Cal.com checks both sources depending on context, so missing or incorrect secrets in either place can cause authentication errors like the one you saw. The recommended approach is to use the app-specific environment variables feature in the Cal.com app store for storing API keys, rather than only general ENV variables or only the Prisma app keys (source).

If payments stay pending, it's often due to incomplete Stripe webhook callbacks, misconfigured secrets, or missing workflow actions. Make sure your webhook secret is correct and that Cal.com is receiving and processing Stripe webhook events successfully. Both environment and Prisma keys need to be set correctly for the integration to work and for payment status to update (note).

Your experience does not appear to be a bug in Cal.com v5.5.2, but rather a misconfiguration or incomplete setup. Double-check that all required secrets are present and valid in both the app store and your ENV, and confirm webhook delivery from Stripe to Cal.com.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[Novapixel1010]

The bot is wrong "ENV variables" have not worked for a long time now. Check issue for more proof #9699 and #6994 Also this still doesn't answer why payments are still pending. Stripe is in sandbox mode but everything should still work that's why stripe has a sandbox mode is so you can test everything.

[dosubot[bot]]

You're right—ENV variables for Stripe have not worked for a long time in Cal.com. This is confirmed by multiple user reports and maintainer responses in issue #6994, where users found that even with all Stripe ENV variables set, the app would not allow configuration or activation via ENV alone. The only reliable way to configure Stripe is to manually insert the credentials into the database (the keys column of the App table for the stripepayment app). This is still the case as of v5.5.2.

The root cause is a mismatch between the app slug and the schema key, which prevents default key creation and UI editing for Stripe, so ENV variables are ignored or bypassed in practice. There have been no recent changes to fix this, and the issue remains open and unresolved as of late August 2025. More details and workarounds are documented in #6994.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}