Skip to content
deedglassdocs

stripe_live_key_refused

Someone tried to store a Stripe key that starts with sklive or rklive on a Stripe connector.

HTTP 400 · invalid_request_error · not retryable

What happened

Section titled “What happened”

Someone tried to store a Stripe key that starts with sk_live_ or rk_live_ on a Stripe connector. Deedglass connects to Stripe sandboxes only: the key is refused before it is encrypted, so it is never stored, logged or echoed (the message shows its first 8 characters at most). The CLI refuses it before sending anything. A live key that reaches a stored row some other way is refused again before every call, and the connector is disabled.

What to do

Section titled “What to do”

In your Stripe sandbox, open Developers › API keys and create a restricted key (it starts with rk_test_). Store it with deedglass connector credentials set stripe --from-env STRIPE_TEST_KEY. There is no setting that allows live mode.

Example

Section titled “Example”
HTTP 400 · stripe_live_key_refused
{
  "error": {
    "type": "invalid_request_error",
    "code": "stripe_live_key_refused",
    "message": "This is a live-mode Stripe key. Deedglass connects to Stripe sandboxes only. Use a restricted key that starts with rk_test_.",
    "param": "secret.token",
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/stripe_live_key_refused"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) InvalidRequestError with code === "stripe_live_key_refused"
Python (deedglass) deedglass.InvalidRequestError with .code == "stripe_live_key_refused"
Section titled “Related”