The WebApp

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.

​

Two ways to build the Consumer experience

A Program has two ways to surface Paylead value to Consumers:

• Build natively: the bank’s app calls the Paylead API 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 flows:

• Offer catalog: browsing the Offers surfaced to the Consumer.
• Offer detail: the full terms of a single Offer (eligible Brand, Reward terms, validity period, and channel).
• Pool (cagnotte) management: tracking the Consumer’s Cashback 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 and viewing the ones the Consumer already owns.
• Post-onboarding consent management: letting the Consumer review and adjust their Perks consent after enrollment.

Loyalty 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).

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.
• Animation: engagement and notifications (see Animate your program).
• Transaction sharing: pushing or having Paylead pull transactions (see transaction lifecycle).
• Ventilation set-up: configuring how Cashback is paid out (see Ventilation).

​

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), Rewards are attributed, and payouts run through Ventilation. The WebApp simply renders these to the Consumer.

​

What’s next