0%
Preparing for landing
← All work
Simpaisa

Raast R2P Instruction Page

A bank-specific instruction page that auto-detects each user's bank from their IBAN and shows them exactly where to approve a Request-to-Pay, lifting payment success from 31% to 65%.

Role / Product Manager (sole PM)Year / 2025Status / Live in production · 14 banks
Live prototype, UBL variant

Try the real thing.

This is the production instruction page, running live in the frame — swipe through the steps and watch the auto-redirect timer.

Open full-screen ↗
Raast R2P bank-specific instruction carousel
Raast R2P bank-specific instruction carousel
Live prototype, UBL variant

Best on your phone.

Open the real UBL instruction page and try it at your own screen size.

Try it now on your phone ↗
+33.7ptsPAYMENT SUCCESS UPLIFT
14 banks~85% OF MOBILE-BANKING USERS
The problem

Pakistani bank apps bury the payment-approval screen 3–6 taps deep, with different labels and step counts across 14 different UIs. When Simpaisa handed a customer off to their bank app, most couldn’t find where to approve. Baseline success sat near 31%, with roughly 70% session abandonment.

What I did

A single responsive instruction page served as the redirect URL: a swipeable carousel of real, bank-specific app screenshots telling each user exactly what to tap. It reads like calm institutional bank guidance, with no Simpaisa branding, and ships in timer and no-timer variants for short- and long-expiry flows.

Vanilla HTML/CSS/JSOKLCH tokensTouch carouselDeeplinks
THE INSIGHT

The failure was informational, not motivational.

Users wanted to pay. They had already committed. They simply could not find the approval screen inside their own bank app. They were lost in the wrong menu, under time pressure, with no precedent for this payment method.

If you show someone exactly what their screen will look like before they see it, and tell them precisely what to tap, the drop-off collapses. That was the entire bet.

DESIGN DECISIONS

Screenshots over text. Bank, not brand.

Real screenshots became the primary content, unambiguous regardless of literacy. Simpaisa stayed invisible so the page read as official bank guidance and earned trust through restraint, not marketing.

One responsive template powered all 14 banks, each with sourced screenshots, plain-language captions, and verified navigation paths. It stays maintainable and fast to update when a bank ships a redesign.

OUTCOME

A 33.7-point lift, now live across the country.

In a controlled single-merchant pilot, payment success rose 33.7 points, from 31% to 64.7%. The page is now live across all 14 banks, reaching roughly 85% of Pakistan’s mobile-banking population, and measurably increased merchant confidence in pushing R2P.