Problem Strategy Systems Interaction Design System Validation Leadership

Payment Method Discoverability - Amazon

Payment Method Discovery Across the Shopping Journey

Payment method discovery exploration — Search, PDP and Cart
My Role
Senior UX Designer
End-to-end ownership across Search, PDP, Cart & Checkout payment discoverability

Problem Statement

Customers weren't abandoning checkout because instalments were unavailable. They were abandoning because they didn't know they existed. Flexible payment options on Amazon MENA were invisible until checkout — by which point most customers had already decided to leave.

In one of the fastest-growing markets for instalment payments, customers couldn't discover or evaluate flexible payment options until the final checkout step — far too late to influence their purchase decision. Affordability signals were absent at Search, the Product Detail Page, Add-to-Cart confirmation, and Cart: the four moments where purchase intent is actually formed. Options like instalments and bank-linked offers existed, but without surfacing them earlier, they had no effect on conversion.

This led to the Instalment & Payment Discovery initiative: a redesign of how payment methods are surfaced across key pre-checkout touchpoints — Search, PDP, Add-to-Cart confirmation, and Cart. The goal was not just visibility, but delivering contextual, personalised, and timely affordability cues at the moments that shape whether a customer buys at all.

Identifying when customers need payment information

Before designing any screen, I worked out where in the journey payment information actually changes a decision. Purchase intent forms at Search, the Product Detail Page, Add-to-Cart confirmation and Cart, yet payment options only appeared at checkout. The next three sections cover the market opportunity, the customer pain points, and the design strategy that followed from them.

Opportunity

The MENA region is a uniquely high-opportunity market for payment innovation. Instalment adoption in the UAE alone grew 65% year-on-year through 2023–24, with providers like Tabby and Tamara acquiring millions of users. Yet Amazon's payment discovery experience had not kept pace with this behavioural shift.

The data told a clear story: customers who encountered instalment options before checkout were 2.4× more likely to complete a purchase using them. The challenge wasn't building a better checkout — it was redesigning discoverability for the entire pre-checkout journey.

$8.2B
MENA instalment market projected by 2026, up from $4.8B in 2024
65%
YoY growth in instalment users across UAE & Saudi Arabia in 2023
76%
Average cart abandonment rate in MENA e-commerce — highest at payment stage
2.4×
Higher instalment completion rate when payment options are surfaced pre-checkout

Customer Pain Points

Through session recordings, funnel analysis, and 22 in-depth user interviews across UAE, Saudi Arabia, and Egypt, five structural pain points emerged — each compounding the others and collectively suppressing instalment adoption across the platform.

01
Payment Method Invisibility
Payment discovery was limited entirely to checkout. Customers navigating Search and PDP had no signal that instalment options were available — making affordability a late and often irrelevant revelation.
02
Offer and Benefit Disconnection
Bank-linked discounts, cashback offers, and instalment promotions were surfaced in isolation from each other. Customers had no unified view of what they could save, so most simply didn't try.
03
Affordability Blindness
High-value items above AED 500 were routinely abandoned not due to inability to pay, but because customers didn't realise they could split the cost. Seeing "AED 950" felt final; "AED 89/mo" would have kept them in the journey.
04
Fragmented Payment Journey
Customers experienced inconsistent payment messaging across Search, PDP, Cart, and Checkout — different providers, different formats, different logic. There was no coherent narrative from browse to buy.
05
Payment Decision Paralysis
Customers with multiple eligible payment methods (Tabby, Tamara, bank instalments, credit card EMI) faced an overwhelming, unguided choice at checkout with no personalisation or ranking logic. The result: hesitation, longer decision time, and increased abandonment.
💡
Core Insight
In usability sessions, 79% of users who abandoned a high-value cart said they would have considered an instalment plan — if they'd known it was available. The problem wasn't demand. It was discovery.

Design Approach

This was not a simple "show more information" project. It required a new design logic — one that knew when to show payment options, which options to prioritise for each customer, and how to present them without disrupting the primary shopping intent.

I established three design principles to prevent payment discovery from becoming another layer of checkout complexity.

Progressive Disclosure
Each touchpoint introduces payment context at the right depth. Search: a single line. PDP: a scannable offer row. Cart: a structured decision card. Checkout: a full plan selector.
Personalised Payment Ranking
Personalisation engine logic surfaces the most relevant payment method per customer: lowest monthly payment → linked bank offers → recently used methods → co-branded credit card upsell. No one-size-fits-all.
Zero Primary-Flow Disruption
Every payment signal was designed to be ignorable — tappable for more, but never blocking. Add to Cart, Buy Now, and Proceed to Checkout retained their visual dominance throughout.

Connecting Search, Product Detail, Cart, and Checkout

Based on the four-touchpoint pain-point analysis, I designed a connected payment discovery system that carries instalments and bank offers through the entire pre-checkout journey — Search, PDP, Add-to-Cart confirmation (HUC), and View Cart — rather than treating each page as a separate redesign.

I built every solution on the same three principles from my design approach: progressive disclosure, personalised payment ranking, and zero primary-flow disruption. The same ranking logic powers each touchpoint, so the message stays consistent as customers move from browse to buy. Together, they turn payment from a checkout-only step into a conversion lever at the discovery stage.

Search
A single line of instalment context on the product card.
Product Detail Page
A scannable offer row, above the fold.
Cart
A structured decision card with basket-building prompts.
Checkout
A full plan selector, by which point customers already know their options.

Making complex payment options easier to understand

Instalment plans, bank offers, coupons and partner rules all compete for attention. At each touchpoint I reduced them to what a customer needs to decide at that moment, and made every signal ignorable so Add to Cart, Buy Now, and Proceed to Checkout kept their visual dominance.

🧭
Key Design Decision
I initially prioritised the lowest monthly payment because it reduced price perception. However, testing showed that partner branding created more trust for first-time BNPL users. I therefore used a hybrid pattern: the monthly amount as the primary message, and partner identity as the trust signal.

Instalment & Payment Discovery

The Problem
The Search Results Page is where purchase intent begins, yet it provided zero payment signals. Customers browsing high-value electronics had no way to filter, identify, or anticipate which products had instalment options — payment stayed invisible until the very end, and every customer saw the identical, unpersonalised experience.
The Solution
Redesigned product cards to surface instalment context directly on Search, consolidating instalment amounts, coupon savings and bank offers into a single value proposition. Added an “Instalments Available” filter and tied the ranking logic to the personalisation engine so the most relevant payment partner surfaces per customer — e.g. Tabby for 0% intent, Emirates NBD for card-linked users.
  • Instalments at search level can lift click-through by 18–22%; monthly framing reduces price-anchoring friction
  • Eligible products gained improved visibility and ranking based on payment signal quality
Search Results — before, no payment signal

Before — no instalment or payment signal

Search Results — after, instalment and payment discovery

After — instalment & payment discovery

Offers & Instalment Discovery

The Problem
The PDP is the highest-intent moment in the journey, yet instalments were buried below the fold in a generic “other payment methods” link — never seen by 60%+ of users who decided above the fold. Bank discounts and instalment options were shown separately with no combined savings view, and prices were never reframed as a monthly amount, so the strongest conversion lever on the page was never activated.
The Solution
Introduced a structured “Offers for you” row — a scannable, above-fold section surfacing the two most relevant payment offers per customer, with a “See all offers” link for deeper exploration. Combined savings across instalment, coupon and bank discount were shown together for the first time, and eligible items now display a monthly amount alongside price.
  • In A/B testing, surfacing “AED 89/mo” on the PDP reduced perceived price by 31% and lifted add-to-cart rate by 22% on items above AED 400
  • Customers could combine offers to save up to 35%, previously invisible
PDP — before, hard to discover payment methods

Before — payment buried below the fold

PDP — after, offers and instalment discovery

After — “Offers for you” row

Reachable Offers & Instalments

The Problem
The Add-to-Cart confirmation drawer — the moment right after a customer commits to a product — carried zero payment signals and no basket-building prompt. Research showed this is a high-receptivity moment: customers are briefly in consideration mode before returning to browse, and it was going entirely unused.
The Solution
Extended the confirmation drawer with a dynamic, threshold-based prompt (“Spend AED 50 more to unlock 15% off with HSBC”) and an instalment-eligibility line (“Eligible for 0% instalments with Tabby”), reusing the same ranking logic that powers Cart and PDP so the message stays consistent as customers move through the journey.
Add-to-Cart confirmation — before, no offer or instalment visibility

Before — no reachable-offer or instalment visibility at Add-to-Cart

Add-to-Cart confirmation — after, reachable offers and instalments

After — reachable offers & instalment prompts at Add-to-Cart

Payment & Instalment Discovery

The Problem
View Cart was the last upstream touchpoint before checkout, with no payment context at all. A customer with a cart of AED 1,200 had no idea they could split it, no visibility of linked bank offers, and no incentive to add more to unlock threshold-based benefits — each saving lived in a different, disconnected UI zone.
The Solution
Turned the cart from a passive summary into an active affordability tool: a persistent basket-building prompt (“Add AED 50 to unlock instalments”), a linked bank offer row, and an inline instalment plan card (4–12 months) — all visible before checkout, ranked by cart value, customer profile and behaviour history.

“I had no idea I could pay in four. I just saw the total and thought — that's a lot. If it said I could pay AED 237 today, I would have done it right there.”

View Cart — before, no payment or instalment visibility

Before — no payment or instalment visibility

View Cart — after, payment and instalment discovery

After — basket-building & instalment discovery

Creating reusable, accessible components

A multi-touchpoint system only holds together if it is built from shared parts. I extended the Amazon MENA design system with a component library, so Search, PDP, Add-to-Cart confirmation and View Cart share one visual and interaction language.

  • Reusable payment components extending the Amazon MENA design system, used across all four touchpoints
  • One ranking logic and one message pattern reused across Search, PDP, Add-to-Cart confirmation and Cart
  • Annotated Figma specs and interaction documentation prepared for developer handoff
  • Launched across all four touchpoints together, so the journey stays consistent
  • The payment design system I advanced at Amazon includes 20+ reusable, WCAG-accessible components

Explaining the research, prototype testing, and evidence behind decisions

Each decision in this case study is tied to evidence: research before design, prototype and A/B testing before launch, and measured results after. Below: the evidence base, the prototype used for leadership alignment, and the launch results.

22
Moderated interviews across UAE, KSA and Egypt
450K+
Sessions analysed to pinpoint exact drop-off points
60%+
of PDP users never scroll past Add to Cart (eye-tracking), which set the above-fold placement
3–4
Layout variants per touchpoint, testing copy framing, placement and disclosure depth

Prototype Walkthrough

An interactive prototype built for leadership alignment — demonstrating the end-to-end instalment discoverability experience across Search, PDP, and Checkout.

Results After Launch

The redesign launched across Search, PDP, Add-to-Cart confirmation and View Cart together. The results below come from the launched experience, backed by the research and testing described above.

Improving payment discoverability did not just lift conversion. It gave customers confidence earlier in the journey, so instalments became part of how they decided what to buy, not a late surprise at checkout.

18–25%
Increase in Instalment Adoption
More customers chose an instalment plan once their options were visible before checkout, instead of discovering them at the last step.
3–5%
Checkout Conversion Uplift
More customers completed checkout after seeing affordability options earlier in the journey.
15–35%
Increase in Offer Engagement
More customers interacted with the payment offers surfaced across Search, PDP and Cart.

What I led, and what the team and partners contributed

End-to-end ownership meant leading the design, research and handoff, while depending on product, engineering, legal and partners for what they own. This is where that line sits.

What I led
  • Ran 22 moderated interviews and analysed 450K+ sessions to find the drop-off points
  • Designed 3–4 layout variants per touchpoint and tested copy, placement and disclosure depth
  • Led compliance reviews with Tabby, Tamara and the bank partners, and closed 140+ annotations from the tracker I maintained
  • Led the six-week A/B testing phase across three UAE cohorts, Australia and Singapore
  • Prepared handoff: annotated Figma specs, interaction documentation and the component library
  • Built the interactive prototype used for leadership alignment
What the team and partners contributed
  • Amazon MENA Product and Payments: aligned with me on the current-state map (14 touchpoints) and the shared success metrics
  • Personalisation engineering: worked with me to define the ranking logic, including 12 edge cases
  • Tabby, Tamara, Al Hilal, HSBC and ENBD: set brand, disclosure and eligibility constraints, and reviewed weekly Figma prototypes
  • Legal and product experience review: signed off before launch

From Pain Points to a Shipped, Multi-Touchpoint System

Six months of cross-functional design work, spanning Amazon MENA product, payments, legal, and three external instalment partners.

01.
Discovery, Research & Stakeholder Alignment

Kicked off with cross-functional alignment across Amazon MENA Product, Payments, instalment partners (Tabby, Tamara), bank partners (Al Hilal, HSBC, ENBD) and legal — mapping the current-state experience across 14 touchpoints and defining shared success metrics. In parallel, I ran 22 moderated interviews across UAE, KSA and Egypt and analysed 450K+ sessions to pinpoint exact drop-off points; eye-tracking on PDP confirmed 60%+ of users never scroll past the Add to Cart button, validating an above-fold placement strategy.

Stakeholder Workshops User Interviews Funnel Analysis
02.
Concept Exploration & Personalisation Logic

Designed 3–4 layout variants per touchpoint — testing copy framing (monthly amount vs partner branding), placement logic (inline vs overlay) and disclosure depth — reviewed with partners via weekly Figma prototype cadences. In parallel, worked with the personalisation engineering team to define the ranking logic behind payment surfacing: lowest monthly payment → linked offers → recently used methods → co-branded card upsell, covering 12 edge cases including ineligible products, cart thresholds and failed authorisations.

Figma Concept Testing Personalisation Logic Edge Case Mapping
03.
Partner Compliance & Legal Alignment

Led rounds of compliance review with Tabby, Tamara and bank stakeholders, resolving constraints on logo usage, interest disclosures, eligibility messaging and co-branding hierarchy. Maintained a centralised compliance tracker, closing 140+ annotations ahead of launch readiness.

Brand Compliance Legal Review Partner Alignment
04.
A/B Testing, Handoff & Launch

I treated payment discoverability as a potentially global customer problem rather than assuming it was unique to MENA. I used cross-market learning to evaluate the underlying customer need, looking at how it shows up across countries, payment ecosystems and shopping behaviours, while accounting for differences in payment-provider availability, customer eligibility, local regulations and purchasing behaviour. This helped me distinguish reusable design principles from market-specific implementation decisions.

As the design evolved, I led a six-week A/B testing phase across three UAE cohorts, Australia and Singapore, comparing the proposed experience against the existing approach. It gave a structured way to assess whether surfacing instalment information earlier in the shopping journey could improve discoverability and influence customer decisions.

I then prepared the handoff, with annotated Figma specs, interaction documentation and a component library extending the Amazon MENA design system. The experience launched across Search, PDP, View Cart and Add-to-Cart Confirmation together to keep the journey consistent, with full product experience sign-off obtained beforehand. Combining problem discovery, cross-market learning, iterative design and validation produced an experience that meets local customer needs while supporting a more scalable approach to payment discovery.

A/B Testing Dev Handoff PXBR Sign-off
Tools Used