# Stripe keys

_{This page means}

| This page is | This page is not | | ----------------------------------------- | --------------------------------------------------- | | _{Habits for money-adjacent keys} | _{Stripe’s full Connect or Radar reference} |

_{The habit}

_{Live keys move real money and real customers.}
_{Test keys move sandboxes. Mixing them in speech (“our Stripe key”) is how incidents start.}

_{When the UI or validation rejects a key shape, believe the rejection.}
_{Fix the key class at Stripe first, then re-save and run Test.}

_{Three habits}

{% stepper %} {% step %} _**First** _{Name environments out loud: “test dashboard,” “live dashboard,” “test key,” “live key.”} {% endstep %} {% step %} _**Second** _{Restricted keys at Stripe are a good practice when you can express least privilege for your automation.} {% endstep %} {% step %} _**Third** _{After any incident, rotate at Stripe, then} _**`Remove`** _{and re-save in ARIA if you need a clean slate.} {% endstep %} {% endstepper %} ***

_{Ask a question}

_{Who is allowed to toggle live mode in your Stripe account?}
_{If everyone is, tighten humans before you tighten software.}

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ariaagi.com/security-and-privacy/stripe-keys.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.