Question 1

Should I use a restricted key?

Accepted Answer

Yes, always. Stripe's restricted keys let you grant only the specific read permissions Ana needs. Create a dedicated TextQL restricted key with read-only access to the resources you want to analyze. This gives you a clean security boundary and clear audit trail in Stripe.

Question 2

Does Ana read Stripe metadata?

Accepted Answer

Yes. Every Stripe object supports custom metadata fields, and the connector exposes them. Ana can filter, group, and join on any metadata key you use, which is especially powerful when Stripe metadata encodes customer IDs, product tiers, or feature flags.

Question 3

How are Stripe keys secured?

Accepted Answer

Restricted keys are encrypted at rest in TextQL's credential vault and injected by our egress proxy at the network layer. Ana's Python sandbox never sees the raw key value. You can rotate the key any time from the TextQL admin console without changing any prompts.

Question 4

Can Ana issue refunds?

Accepted Answer

Technically yes with write permissions, but we strongly recommend keeping the TextQL key read-only. Create a separate, tightly scoped write key if you want to automate refunds or subscription changes, and audit its usage closely to prevent errors.

Question 5

Does Ana see PCI data?

Accepted Answer

No. Stripe never returns raw PAN or full card data through its API, and Ana only sees tokenized card references, last4 digits, and brand. This preserves PCI compliance automatically. Ana cannot inadvertently expose card data because the API never provides it.