> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paylead.fr/llms.txt
> Use this file to discover all available pages before exploring further.

# The WebApp

> How Paylead delegates part of the Consumer journey, across both Perks and Loyalty, to an embedded webview inside the bank app.

The **WebApp** is a Paylead-hosted application reached via a webview inside the Program Manager's mobile app. It lets a Program delegate part of the Consumer-facing journey to Paylead instead of building every screen natively.

<Info>
  This page explains *what* the WebApp is and *what it delegates*. For *how to integrate it* (opening the webview, the functions it exposes) see the [WebApp (MFP)](/program/webapp/overview) tab.
</Info>

## Two ways to build the Consumer experience

A Program has two ways to surface Paylead value to [Consumers](/glossary#consumer):

* **Build natively:** the bank's app calls the [Paylead API](/program/user-journey/quickstart) and renders Offers, Rewards, and the loyalty card wallet itself. Maximum control over the UI.
* **Embed the WebApp:** the bank opens Paylead's webview at the right place in its app. Paylead renders the experience; the bank app only provides the native WebView that hosts it.

Most Programs mix both: native entry points, with the WebApp handling the richer flows.

## What the WebApp handles

When a Program embeds the WebApp, Paylead renders these flows so the bank does not build them natively.

**[Perks](/glossary#perks) flows:**

* **Offer catalog:** browsing the [Offers](/glossary#offer) surfaced to the Consumer.
* **Offer detail:** the full terms of a single Offer (eligible [Brand](/glossary#brand), [Reward](/glossary#reward) terms, validity period, and channel).
* **Pool (cagnotte) management:** tracking the Consumer's [Cashback](/glossary#cashback) [pool](/glossary#pool) (balance, pending and validated Rewards, and payout history).
* **Reward listing:** the full list of Rewards the Consumer has generated through Perks Offers.
* **Voucher purchase and list:** buying [Vouchers](/glossary#voucher) and viewing the ones the Consumer already owns.
* **Post-onboarding consent management:** letting the Consumer review and adjust their Perks consent after enrollment.

**[Loyalty](/program/user-journey/loyalty-journey) flows:**

* **Loyalty account creation and connection.**
* **Merchant loyalty space:** the branded loyalty area for each partner.
* **Loyalty card wallet:** storing and managing the Consumer's loyalty cards (can also be built natively).

<Warning>
  The WebApp is **mandatory** for the loyalty account creation and connection flows. A Program cannot build these natively; they must run inside the WebApp.
</Warning>

This shortens the bank's build: instead of implementing each screen against the API, the bank embeds a maintained, consistent experience.

## Customization

The WebApp is **customized to blend into each bank's UX**: it is not a generic, off-brand surface. The bank can also adjust the UI to fit its own marketing needs, so the embedded experience stays consistent with the rest of the app.

## Early access to new features

Embedding the WebApp also means **getting Paylead's new features first**: improvements ship inside the WebApp ahead of the API surface, so Programs on the WebApp benefit from them in preview without extra build work.

## What stays native (the Program's responsibilities)

Even with the WebApp, the Program still owns these natively:

* **Consumer enrollment** into the [Program](/glossary#program).
* **Animation:** engagement and notifications (see [Animate your program](/program/user-journey/guides/animate-your-program)).
* **Transaction sharing:** pushing or having Paylead pull transactions (see [transaction lifecycle](/program/user-journey/concepts/transaction-lifecycle)).
* **Ventilation set-up:** configuring how [Cashback](/glossary#cashback) is paid out (see [Ventilation](/program/user-journey/concepts/ventilation)).

<Tip>
  We recommend the bank surfaces, natively, the Consumer's profile statistics and/or partner Brand logos, which reinforce the value of the Program right inside the bank's own UI and guide the Consumer toward the Perks and Loyalty services.
</Tip>

## How it fits the journey

The WebApp is a delivery surface, not a separate product. Behind it, the same mechanics apply: transactions flow in (see [transaction lifecycle](/program/user-journey/concepts/transaction-lifecycle)), Rewards are attributed, and payouts run through [Ventilation](/program/user-journey/concepts/ventilation). The WebApp simply renders these to the Consumer.

## What's next

<CardGroup cols={2}>
  <Card title="WebApp (MFP) integration" icon="smartphone" href="/program/webapp/overview">
    The technical guide to embedding and opening the WebApp in your bank app.
  </Card>

  <Card title="Loyalty journey" icon="medal" href="/program/user-journey/loyalty-journey">
    The loyalty wallet the WebApp can surface to Consumers.
  </Card>
</CardGroup>