# What Happens After You Install Redux

After you install Redux through the Stripe App Store, a few things happen immediately behind the scenes.

### 1) We ingest your billing data

Redux pulls in your historical and current failed payment data. This gives us a full view of how your payments behave across decline codes, card types, issuers, and timing.

### **2) We establish your baseline recovery rate**

We calculate how much Stripe’s native logic is currently recovering for you. This baseline becomes the reference point for all future performance so you always know the incremental lift Redux creates.

### **3) We run a full recovery audit**

Our system analyzes your failure patterns, identifies the biggest sources of lost revenue, and maps out the highest leverage recovery opportunities.

### **4) We send you a detailed audit report**

You receive a clear summary of your baseline, what’s driving your failed payments, and what Redux will do to increase recovery. It also outlines expected lift based on your data.

### **5) You review and approve the plan**

Nothing starts automatically. You review the audit, confirm you want to move forward, and sign off. This ensures you are fully aligned before Redux begins active recovery.

### **6) Redux begins intelligent recovery**

As failed payments occur, Redux classifies the decline, times retries based on customer and issuer behavior, and begins recovering failed payments.

### **7) You track performance in your dashboard**

You’ll see recovered revenue, active recovery campaigns, baseline vs. Redux lift, and LTV boost all in one place.


---

# 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.reduxpayments.com/getting-started/what-happens-after-you-install-redux.md?ask=<question>
```

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.