# Stripe Console

Analyze and act on your Stripe data using a single conversational interface.

The Stripe Console lets you query data, manage customers, and so on. Type your question, and Console learns from your conversations and retains context over time. You can ask follow-up questions about results, or act on what you find without starting over.

## Join the waitlist 

### Interested in getting access to the Stripe Console?

Console is in private preview. Add your email address to join the waitlist.

```bash
curl https://docs.stripe.com/preview/register \
  -X POST \
  -H "Content-Type: application/json" \
  -H "Referer: https://docs.stripe.com/dashboard/console" \
  -d '{"email": "EMAIL", "preview": "stripe_console"}'
```

## How Console works

Console uses a combination of persistent business context, conversation history, and reusable skills:

- **Business context:** Define business-specific terms and thresholds that Console applies automatically going forward.

- **Conversation history:** Corrections and refinements from past conversations improve accuracy without the need to teach the Console again.

- **Skills:** Save repeatable processes as skills that Console can use to answer questions and take actions.

Console uses generative AI supported by a third party. Always review and verify its responses, because they might contain mistakes.

## What Console can do

To start a new conversation, select **New conversation**. Each conversation maintains its own context, so you can run multiple queries independently. To revisit a previous conversation, open the conversation history from the sidebar.

> #### Feedback
> 
> To share feedback on a Console response, type `/feedback` into a conversation. Your feedback helps improve Console’s accuracy.

### Query and diagnose data 

Console lets you ask questions and get structured, sourced answers from your Stripe data. Among other things, it can chart revenue, find customers with failed payments, and analyze subscription churn. When you ask a diagnostic question—such as what caused a revenue change—Console returns a list of potential root causes.

### Take action on results 

After diagnosing a problem or identifying an opportunity, you can act on the results directly. Actions include retrying failed payments, issuing refunds, creating coupons, adjusting subscriptions, and drafting customer communications.

## Console use cases 

The following use cases show how Console handles common tasks, from answering questions and diagnosing issues to taking action.

### Investigate a revenue drop 

1. **Ask:** “Why did revenue drop 12% this week?”
2. **Diagnose:** Console shows root causes, including enterprise downgrades, increased churn among small and mid-sized businesses, and a spike in failed payments, along with the dollar impact of each.
3. **Get more details:** “Select the failed payments cause.”
4. **Review:** Console shows 19 recoverable payments totaling 4,200 USD. You retry them with a 10% discount offer.

### Recover failed payments 

1. **Ask:** “Find failed payments over 500 USD from the last 7 days.”
2. **Review:** Console returns a table of results with customer details, failure reasons, and amounts.
3. **Retry:** “Select the recoverable payments and retry them.”

### Analyze subscription churn 

1. **Ask:** “Show me customers who churned last month because of price.”
2. **Review:** Console returns a table of matching customers and churn details.
3. **Refine:** “Show their usage in the 3 months before churn.”
4. **Diagnose:** Console reveals that most were power users, suggesting price sensitivity rather than low engagement.

### Build a report 

1. **Ask:** “Chart MRR and churn for Q4 compared to Q3.”
2. **Review:** Console shows a chart of MRR and churn for Q4 compared to Q3.
3. **Refine:** “Add a column for net revenue retention.”
4. **Review:** Console updates the chart to include net revenue retention.

## What Console can do for Connect platforms 

### Understand your embedded payments business 

1. **Ask:** “Explain my month-over-month growth across my connect payments business. Build a report.”
2. **Review:** Console explains how your embedded payments business grew, covering top-growing connected accounts, how payment method mix affected margins, and potential connected account churn.

### Investigate negative margin connected accounts 

1. **Ask:** “Show me my negative margin connected accounts last month”
2. **Review:** Console returns a table of negative margin connected accounts with volume, margin, and take-rate details, along with the total dollar impact.
3. **Get more details:** “What is driving this negative margin”
4. **Diagnose:** Console shows root cause of negative margin.

### Streamline KYC data collection 

1. **Ask:** “How can I speed up the KYC process for my merchants?”
2. **Review:** If you have already collected business information during your own onboarding, Console recommends passing that data to Stripe using the Accounts API, reducing the amount of information merchants need to enter manually.

### Improve account verification experience 

1. **Ask:** “What does Stripe recommend I do to speed up account verification for my merchants?”
2. **Review:** Top platforms make KYC feel structured and manageable. Console recommends clear, plain-language guidance for each section, progress indicators, explanations for why sensitive information is needed, and access to support and FAQs.