Skip to content

How does Revolut explain notifications before showing the system permission prompt?

  • By Ali Abouelatta
  • Published
  • Reviewed
  • 2 min read
  • notifications · permissions · onboarding

Short answer

Revolut’s captured primer describes payment alerts and an up-to-date balance, with distinct enable and defer actions. The next screenshot shows the iOS permission dialog over the primer. This separates the product’s explanation from the operating system’s authorization decision. source[1]

Product explanation, then permission

The first screenshot connects notifications to a concrete banking job: seeing card-payment activity and balance updates. A prominent enable action sits above a quieter Not now action. The second screenshot shows the iOS dialog, including allow, scheduled-summary and deny choices in that captured device state. source[1]

Read repeated frames carefully

The four-screen archive also contains another primer frame and a loading-state frame. These are captured UI states; they do not prove four different onboarding questions or repeated permission requests. A screenshot sequence alone does not establish which system option the person chose or whether future notifications arrived. source[1]

What to carry into another product

Explain the specific information a person will receive before asking for authorization, and distinguish postponing the product prompt from granting system permission. Evaluate whether that explanation helps users make an informed choice. The screenshots provide a design reference, not a measured opt-in uplift.

Real in-market screens

Screens from real, in-market apps, tracked by Lazyweb Research.

  • Payment-alert benefit explanation with enable and defer actions
    Revolut1206 × 2622opens the full image
  • iOS permission dialog over Revolut’s primer
    Revolut1206 × 2622opens the full image

Methodology

Visual inspection of one four-frame public archive. The article illustrates the benefit explanation and system dialog; repeated and loading frames are not counted as distinct product decisions. The update date is page metadata, not a independently verified capture-session date.

Sources

  1. [1]

    Revolut enable-push-notifications capture

    Four archived screens; the page’s update metadata is February 2026. This review inspected all four and illustrates the first two.

    Open source Back to text

Source: Lazyweb Research — proprietary analysis of real, in-market app screens. Cite as Lazyweb Research, 2026-09-09.

Explore the evidence