Finance · US iPhone listing

ASO Audit: PayPal

Does their ASO suck?

Listing creative score · first three captured iPhone screenshots

3/10The app deserves better.

PayPal's first headline and first screen are doing different jobs. Then the sequence changes to sending money and card rewards. Three financial propositions, no finished customer story. The brand is doing the joining-up.

ASO Audit: PayPal illustration: A multipurpose payment tool opens into security, transfers and rewards.
Gabriel Machuret in an ASO Guru T-shirt: inspecting the conditions.

Gab’s verdict · 3/10Gabriel Machuret

Editorial illustrationBuyer protection in the headline. Pay-later shopping in the picture.See the actual listing screenshots ↓
Listing snapshot · what I checked

What I actually checked

One storefront, one language and a dated capture. This is an independent editorial audit, not a client case study.

Store & market
Apple App Store · United States
Language & device
en-US · iPhone
Captured
30 September 2026
Creative reviewed
First 3 still screenshots; video and other devices excluded
Observed app name · 24/30 characters

PayPal - Pay, Send, Save

Observed subtitle · 30/30 characters

Debit card, rewards, pay later

Gab’s take · Five criteria. Two points each.

Why this gets 3/10

Buyer protection and transfer controls are relevant product information. Keep them. The headline needs to match the pictured job, and the important terms should not whisper beneath the offer. Choose one customer job, show the relevant action and make its terms readable. A protection headline should demonstrate the protected purchase context. Reward percentages should not become the loudest part of an otherwise incomplete explanation.

  1. Reason to care

    1/2

    Buyer protection is useful but mismatched to the pictured pay-later screen.

  2. Product evidence

    1/2

    Sending controls appear without a completed transfer example.

  3. Readable at a glance

    1/2

    Large headlines work while important qualifications stay small.

  4. A useful sequence

    0/2

    Shopping, transfers and rewards split the opening conversation.

  5. A reason to choose

    0/2

    Security and reward claims need more visible scope.

0: not earned · 1: useful but incomplete · 2: clearly demonstrated. Judged on the dated opening creative; public metadata provides context. These points assess creative execution, not private conversion or ranking performance. Read the scoring criteria · See all ten verdict levels

Three things worth your attention

The screenshot teardown

Inspect the numbered original, read the problem, then compare the proposed fix. The publisher’s creative stays unchanged.

What the visitor sees → what I’d change

The screen misses the headline

Look at the original: The headline discusses protection, while the phone content highlights pay-later shopping.

Why I’m flagging it: Pay-later offers do not demonstrate buyer protection.

Brief this change

Use a matching purchase-protection example or change the headline accurately.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The transfer resets the audience

Look at the original: The interface makes a person-to-person sending action visible.

Why I’m flagging it: Person-to-person sending interrupts the shopping proposition.

Brief this change

Build a focused transfer treatment or continue the same purchase story.

See how the proposed sequence fits together ↓

What the visitor sees → what I’d change

The reward needs its conditions

Look at the original: The creative presents a card reward tied to a chosen spending category and displays terms notes.

Why I’m flagging it: The percentage dominates category and account qualifications.

Brief this change

Enlarge current eligibility and limits alongside one card example.

See how the proposed sequence fits together ↓
Figure 1. First three still screenshots from the US iPhone listing, captured 30 September 2026. Creative belongs to the app publisher and is reproduced for analysis. Publisher claims inside screenshots are not independently verified.

What I’d put on the table

Proposed copy for discussion. These are not current listing fields or tested winners.

Observed listing

PayPal - Pay, Send, Save

Debit card, rewards, pay later

Proposed alternative

PayPal: Send Money & Pay

Payments, shopping, debit card

Name 24/30 · Subtitle 30/30 characters
Metadata comparison. A proposed alternative to review against the current listing.

This alternative prioritises transaction language and a plain list of product areas. It deliberately avoids repeating a percentage reward, a credit promise or a claim about fee-free transfers.

The tradeoff: Removing saving and pay-later wording would reduce emphasis on two existing acquisition propositions. The proposal needs query and campaign evidence; it is not a recommendation to eliminate those products from the wider listing.

Gab’s proposed direction

Give each screenshot a job.

Read the sequence from top to bottom on mobile, left to right on desktop. These are message-layout sketches, not screens from PayPal or tested results.

  1. 01Make the benefit clear

    Proposed headline

    Send or request a payment

    Illustrative layout · verify the real flow

    Put this in the frame: The current verified send/request interface with conditions appropriate to the selected territory.

    Why it earns the space: Lead with a job that can be understood without a promotional offer.

  2. 02Show useful evidence

    Proposed headline

    Use PayPal when you shop

    Illustrative layout · verify the real flow

    Put this in the frame: A current relevant shopping or checkout flow, with any protection wording reviewed against applicable terms.

    Why it earns the space: Make the headline and interface describe the same transaction.

  3. 03Move the decision forward

    Proposed headline

    Explore card options

    Illustrative layout · verify the real flow

    Put this in the frame: A verified card destination with accurate eligibility and offer information.

    Why it earns the space: Show the wider product without suggesting every installer receives the same benefits.

The test: Does the existing send/request screenshot work better as the opening than the shopping/protection screenshot? The sketch gives the designer a direction; the actual product and access conditions decide what can ship.

Want this level of detail for your app?

Bring the listing. I’ll help you decide what to keep, what to fix and what to test.

Talk to Gabriel →
Compare three alternatives

Three alternatives—and what they make clearer

Observed competitor metadata

Venmo ↗

Send Money, Debit card

Venmo uses a short brand name and a subtitle covering money sending and a debit card.

The lesson: Compare the first job visitors recognise, not whether a competitor has a shorter title.

Observed competitor metadata

Cash App ↗

Money. Debit Card. Bitcoin.

Cash App names money, a debit card and Bitcoin in its subtitle.

The lesson: A broad finance proposition can become a list. PayPal should explain which use case leads rather than add another unrelated service.

Observed competitor metadata

Wise: Global Money Transfer ↗

Send payments internationally

Wise explicitly centres international transfers and payments.

The lesson: Transfer intent may be domestic or international. Do not borrow cross-border vocabulary without checking the relevant PayPal product and territory.

Competitor comparison. US listing names and subtitles captured 30 September 2026. These are positioning comparisons, not ranking or revenue comparisons.
Keyword ideas and their evidence

The keyword questions I’d investigate

Intent candidates grounded in the listing—not fabricated search-volume or difficulty scores.

send money / request money

Visitor’s job: Pay another person or request a payment.

Evidence: The second screenshot shows the send interface and the name includes sending.

Decision: Research the precise transaction intent; validate fees and eligibility before writing supporting copy.

online payments / shopping wallet

Visitor’s job: Use an account during online shopping.

Evidence: The first screenshot shows shop offers and a purchase-protection message.

Decision: Investigate checkout intent separately from credit and rewards intent so the first frame can match one clear job.

debit card / spending rewards

Visitor’s job: Understand a card and its conditional benefits.

Evidence: The subtitle and third frame advertise the card and rewards.

Decision: Retain as an evidence-backed research cluster, not a promise of universal availability or a reason to overstate returns.

The unseen keyword field may already cover some of these terms. Build an evidence-backed keyword shortlist before making a metadata change.

What the selected reviews tell us

What three reviewers can teach us

The chosen 2018–2021 accounts illustrate protection, eligibility and business-versus-consumer intent. They are deliberately historical and cannot verify current offers, support quality, fees or functionality. The business account is included to expose a sampling mismatch, not endorse a feature claim.

Sample: 3 selected accounts from 8 displayed reviews. Dates: 24 February 2018–24 January 2021. No sentiment percentage is calculated.

15 October 2020 · 5/5 stars

“transaction dispute”

A 2020 reviewer described confidence in third-party purchases and an experience with dispute support.

What I’d investigate: Research how current prospective users understand protection. One historical account does not establish universal coverage or support outcomes.

Listing review source · Review ID 6536936111

24 January 2021 · 4/5 stars

“pre approved”

A 2021 reviewer described confusion between a promotional message and access to a card.

What I’d investigate: Check whether current acquisition copy creates incorrect eligibility expectations; do not infer that the same promotion or issue exists today.

Listing review source · Review ID 6909624388

24 February 2018 · 5/5 stars

“virtual terminal”

A 2018 reviewer described using several PayPal business products.

What I’d investigate: Separate consumer-app intent from business-platform intent. This account is too old and broad to verify present features in the consumer app.

Listing review source · Review ID 2243944324

A displayed review can be old, unusually positive or internally inconsistent with its star rating. These accounts suggest questions; they do not establish current defects or typical customer experience. Use the Review Research Desk to keep evidence and interpretation separate.

What I’d do first

01

The screen misses the headline

Pay-later offers do not demonstrate buyer protection.

Deliverable: Use a matching supported purchase-protection example or change the headline accurately.

Creative brief and current-product check
02

The transfer resets the audience

Person-to-person sending interrupts the shopping proposition.

Deliverable: Build a focused transfer treatment or continue the same purchase story.

Creative brief and current-product check
03

The reward needs its conditions

The percentage dominates category and account qualifications.

Deliverable: Enlarge current eligibility and limits alongside one supported card example.

Creative brief and current-product check
Open the full test plan

One test worth running

Does the existing send/request screenshot work better as the opening than the shopping/protection screenshot?

Audience
Eligible US English iPhone default-page traffic; interpret the result alongside campaign mix rather than assuming every visitor seeks transfers.
Control
Current shopping/protection, send/request and card-reward sequence.
Treatment
Swap the first and second stills only, keeping all wording, offer notes and later creative unchanged.
Method
Run an eligible App Store product page optimization order test. Review claim accuracy first. Test a newly matched shopping creative separately so it does not confound the ordering result.
Primary measure
Platform-reported download conversion for eligible randomized visitors.
Guardrails
In separate comprehension research, check that visitors do not infer universal protection, guaranteed card access or unconditional rewards.
Decision rule
Set a practical lift and sample plan from actual baseline traffic; read the full interval at the planned review point. An unclear result keeps the existing order pending better intent evidence.
What could muddy the result
Changes to reward offers, card availability, merchant campaigns and the relative share of transfer versus shopping traffic can alter interpretation.

Check Apple’s current product page optimization guidance and custom product page guidance before configuring a test. Write your experiment brief.

How the ten-point scale works

So, does their ASO suck?

1–3: thumbs down · 4–6: thumbs up and down · 7–10: thumbs up

  1. 1/10

    Yeah. It really does!

    The basics need a serious rethink.

  2. 2/10

    I hope no agency is getting paid for this.

    Too many obvious things have been left unfinished.

  3. 3/10PayPal is here

    The app deserves better.

    There is a useful product here. The listing needs to show it.

  4. 4/10

    Recognisable. Not convincing.

    Some basics work, but the opening wastes attention and under-explains the benefit.

  5. 5/10

    Fine. A dangerous place to stop.

    There is usable creative here, but too much of the sales argument is left to the visitor.

  6. 6/10

    Useful. Still leaving too much unsaid.

    Real strengths, undermined by meaningful gaps in the opening story or execution.

  7. 7/10

    Good. The product proof earns it.

    A clear, useful demonstration with specific refinements still needed.

  8. 8/10

    Good. Now sweat the details.

    The main promise is clear and supported. Refinement matters more than reinvention.

  9. 9/10

    Whoever did this knows their stuff.

    Clear positioning, thoughtful choices and very few loose ends.

  10. 10/10

    Okay, now you’re showing off.

    An unusually clear, convincing storefront worth learning from.

An editorial verdict on the captured storefront, not a measured ASO score or an assessment of an agency’s private work.

Try this on your app · worksheet and assignment

Your ASO assignment

  1. Use a matching supported purchase-protection example or change the headline accurately.
  2. Build a focused transfer treatment or continue the same purchase story.
  3. Enlarge current eligibility and limits alongside one supported card example.

What would change my mind?

  • Current product terms and eligibility verified by the product owner.
  • Default-page traffic split between sending, shopping and card intent.
  • Recent consumer-only review sample and conversion baseline.
Sources and capture dates

Sources and scope

No private analytics, search-rank dataset or internal keyword field was supplied. Review quotations are short excerpts; explanations are our summaries. App names and screenshots belong to their respective owners. We are not affiliated with PayPal. Read our editorial methodology.

Your app. Your priorities.

Get an audit you can actually use.

Send your listing, market and the problem you want to solve. I’ll explain the scope and fee before work starts. Your budget should buy decisions, not a longer PDF.

Apply the method to your app

Build a relevant keyword shortlist, plan your screenshot sequence or get help with the creative decisions.

More app teardowns

Browse the complete app teardown library →

Enough theory. Your app next.

Let’s fix what’s holding your listing back.

Send your app link, target market and the problem. We’ll start there.