Gen Z Doesn't Want to Leave the Feed to Shop

You came to scroll. You left with a receipt.

Imagine watching a short clip about a jacket. You like the fit, tap the product and find a checkout a moment later. Shopping did not begin with a search box or a deliberate visit to a retailer. It began while you were doing something else.

That is the appeal behind social shopping. It is also where the interesting payments question begins: how much of the journey should become effortless, and which details must remain impossible to miss?

The evidence—and its date

Adyen's Retail Report 2025 gives this discussion a specific starting point. Its first chapter reports that 41% of Gen Z choose retailers that let them shop on social media. The chapter also describes the continuing appeal of physical shops and customers' expectations of connected online and offline experiences. [1]

This is evidence published as part of a 2025 report, not a new October 2026 survey. [2] It does not mean every young shopper wants to buy inside a feed, that 41% of purchases happen there, or that physical shops have become irrelevant. Choosing a retailer because it offers an option is different from using that option for every purchase.

The headline is therefore a direction to examine, not a description of an entire generation.

Three journeys hiding inside one phrase

The scenarios and product implications below are OLECH analysis, not additional survey findings or descriptions of a particular platform's current features.

Return to the hypothetical jacket. There are at least three ways that purchase could unfold.

First, the clip introduces the product, but the shopper later searches for the retailer independently. Second, a product link opens the retailer's checkout in a browser. Third, the purchase is completed through an interface that stays inside the social app.

All three can reasonably belong in a conversation about social shopping. They create different handoffs, however. A business that counts product discovery in a feed is not necessarily measuring checkout inside the same app. A shopper who finds something through a creator may still prefer to pay elsewhere.

For anyone assessing a product announcement, the useful question is not simply whether shopping is social. It is which part of the purchase has moved—and which parts have not.

The friction worth removing

Consider a checkout that makes our shopper repeat a size selection, rebuild a basket and type an address that was already supplied. Removing those steps would not have to change what the customer intends to buy. It could simply carry their existing decision forward.

Now consider a different shortcut: a button that makes the final price, seller identity or return route hard to find. That might also reduce the number of things someone reads before paying. It would not be the same kind of improvement.

The distinction is between eliminating repeated work and eliminating useful understanding. A good product can do the first without depending on the second.

This is the standard I would use to judge a social checkout. Can the person explain what they ordered, who they bought it from and what happens next? If a faster purchase makes those answers less clear, speed alone is a poor success measure.

The seller should not disappear behind the creator

In our jacket example, the person in the clip, the app displaying it and the business supplying the jacket could be different parties. The interface should not make the shopper guess whether they are dealing with the creator, a marketplace or an independent retailer.

This is not an accusation about any named platform. It is a design test for a hypothetical purchase.

Imagine a checkout with the seller clearly named beside the order summary, an accessible contact route and delivery information attached to the specific item. Then imagine the same purchase presented mainly through a familiar face and a prominent payment button.

Both might look convincing. Only one has made the underlying relationship easy to explain.

The consumer-facing experience should become simpler without making the businesses behind it less visible. Familiarity with a creator is not a substitute for knowing which seller will send the parcel.

A receipt is part of the product

Suppose the jacket arrives in the wrong size. The shopper remembers the clip but cannot remember the retailer's name. Where does the purchase live now?

A strong experience would make the answer straightforward. The order should be findable without reconstructing a browsing session. The receipt, item details, seller contact and applicable return information should form a coherent record.

A less useful experience might be excellent at the first tap and confusing at the first question. A confirmation screen alone would not solve that problem.

The same test works for product teams: ask someone to locate an order a week later, identify the seller and explain how to start a return. That exercise examines something a checkout completion rate cannot tell you on its own.

These are practical questions, not a statement that every purchase has identical cancellation rights. The applicable terms and protections depend on the actual transaction and jurisdiction.

Why this is a fintech story

The payment is where the browsing decision becomes a financial commitment. That makes checkout an important boundary even when the surrounding experience feels like entertainment.

In a well-designed hypothetical flow, the payment provider could help make the total amount, currency and confirmation clear. The merchant could ensure the receipt connects to the order. The platform could make that information easy to find again. None of those responsibilities is fulfilled merely by keeping the shopper inside one app.

The interesting opportunity for fintechs is therefore not just a smaller payment button. It is continuity: a purchase that remains understandable as it moves between discovery, payment, delivery and support.

A provider could test that continuity with deliberately ordinary questions. Does the order identifier match the confirmation? Can the shopper distinguish a failed attempt from a completed payment? Does the support route correspond to the seller shown at checkout?

The best answer would be visible in the customer journey, not only in an integration diagram.

Not every good shopping journey stays in one place

Picture someone who discovers the jacket in a feed, tries it in a shop and buys it later through a retailer's app. Leaving the feed would not necessarily mean the original discovery failed. It might mean the shopper wanted confidence about fit before paying.

That possibility matters when interpreting the approved title. The point is not to trap Gen Z in an app. It is to avoid making people restart a purchase whenever they move between places that suit different parts of the decision.

An uninterrupted journey and a journey contained entirely within one interface are not identical. A useful handoff can be better than a confusing attempt to do everything on one screen.

What to watch

The next useful evidence will be specific: which shoppers use a feature, what it changes in their purchasing journey and whether the experience remains clear after payment. A striking survey percentage should open that investigation, not close it.

For consumers, the test can stay simple. Before paying, identify the seller and the final amount. After paying, make sure the order and its support information are easy to retrieve.

For product teams, measure more than the distance from a clip to a checkout. Examine the distance from a receipt to an answer when something needs attention.

Social shopping can bring discovery and payment closer together. The better version also keeps responsibility within reach.

Sources and scope

[1] Adyen, Retail Report 2025, Chapter 1: Where we shop and how we pay.

[2] Adyen: Retail Report 2025 overview.

Sources checked on 7 October 2026. These are Adyen's own research materials, not independent studies. The 41% figure is attributed to the report and is not presented as a current purchase-volume statistic. The jacket scenarios, interface comparisons and proposed product tests are illustrative OLECH analysis. No claim is made about the features, terms or legal responsibilities of any specific social platform.