Skip to content
AppDues
Log in
Contact salesSign up

Viewing In-App Purchase Data Inside Stripe

Support teams often face the same puzzle: a customer subscribed on one platform but uses the product on another, and the full billing history is scattered. According to the published announcement of the Stripe app, the integration places subscription-platform context next to Stripe billing details inside the Stripe dashboard. This guide explains what the integration shows, what it deliberately does not do, and how to decide when to leave Stripe for the subscription dashboard. Confirm current availability and listing details against the Stripe Marketplace entry before you rely on them.

The problem: split billing history

Picture a subscriber who paid through Stripe on the web, then signed in on a phone. Each system holds a fragment of that person's story, and an agent trying to reconstruct the whole trail has to hop between tools. Per the published announcement, the Stripe app closes that gap: inside Stripe, it presents enriched subscriber data next to the billing records Stripe already holds, so one screen can answer more of the question.

What the Stripe app surfaces

According to the announcement, two timestamps appear automatically beside the customer's Stripe details: the last app version the customer used and the last time they opened the app. Those two fields often explain a support ticket on their own. Someone on an outdated build may just need an update prompt rather than a refund; someone who has never opened the app may be a candidate for a refund decision. The screenshot below shows the combined view.

Adding your own context with subscriber attributes

Beyond the default data the SDK collects, you can attach custom subscriber attributes to each customer. Per the announcement, those attributes appear in the Stripe app too, giving support agents extra context when deciding how to handle a case. Typical uses include internal account notes or plan metadata that helps an agent understand the customer's situation without switching tools.

The read-only boundary

A crucial distinction: per the announcement, the subscriber data shown inside Stripe is read-only. It is displayed alongside Stripe records but is not merged in a way that lets you filter Stripe data by subscriber fields. If your task requires querying or segmenting on subscriber attributes, the Stripe app is not the right surface. This is a visibility feature, not a data-joining feature.

When to switch to the subscription management platform dashboard

Some investigations still need the full subscription dashboard. When that happens, per the announcement, the Stripe app provides links that open the dashboard directly to the right customer and context, so the agent does not have to search again. Use the checklist below to decide which surface fits the task.

Decision checklist: Stripe app vs. subscription dashboard

Stay in the Stripe app when: you need to confirm a customer's last app version or last opened time; you want to read custom subscriber attributes next to billing details; or you are handling a refund question that hinges on app usage. Switch to the subscription dashboard when: you need to filter or segment on subscriber data; you need the full subscription history beyond what the app displays; or you need to make changes rather than read. In both cases, per the announcement, the app's links can carry you to the right customer record without a manual search.

Worked example: the never-opened app

Suppose a customer writes in asking for a refund on a subscription purchased through Stripe. In the Stripe app, the agent sees the last opened timestamp is empty and the last seen app version is absent. That pattern suggests the customer never opened the app after subscribing. The agent can then make an informed refund decision with the billing record and usage evidence side by side, rather than bouncing between systems. If the case needs deeper history, per the announcement, the agent follows the link into the subscription dashboard for the same customer.

Frequently asked questions

Does the Stripe app let me filter Stripe data by subscriber fields?

No. The subscriber data visible in Stripe is read-only and is not merged in a way that supports filtering Stripe records by subscriber data. For filtering or segmentation, use the subscription dashboard.

Which fields does the Stripe app show automatically?

It shows the last seen app version and the last opened timestamp, both collected automatically by the subscription platform, alongside the customer's Stripe billing details.

Can I add my own data to the Stripe view?

Yes. Subscriber attributes you define are visible in the Stripe app, giving support agents extra context alongside the default fields.

How do I get to the full subscription record from Stripe?

Use the links in the Stripe app; they open the subscription dashboard directly to the matching customer and context.