UAE Launches Lean Ziina One-Tap Pay by Bank Experience

Table of Contents

• 1. UAE introduces seamless one-tap bank payments
• 2. Step 1: Launch of One-Tap Pay by Bank Experience
• 3. Step 2: Secure Connection of Bank Accounts
• 4. Step 3: Transition to Recurring Payments
• 5. Step 4: Infrastructure Support for Seamless Payments
• 6. Step 5: Simplifying Financial Products for Users
• 7. Conclusion: The Future of Payments in the UAE
• 7.1 Embracing Innovation
• 7.2 The Road Ahead for Digital Payments

UAE introduces seamless one-tap bank payments

• Lean Technologies and Ziina launched the UAE’s first One-Tap Pay by Bank experience under the Open Finance framework.
• Users connect a bank account once, then top up a Ziina wallet with a single tap—no credential re-entry or bank-portal redirects.
• Built on Lean’s Deposits solution, the launch signals Pay by Bank is moving beyond one-off transfers toward recurring, everyday usage.
• The partnership pairs Ziina’s consumer app flow with Lean’s Open Finance infrastructure to reduce payment friction.

One-Time Setup, Repeat Top-Ups
Before this launch, “Pay by Bank” in the UAE was typically experienced as a one-time, instant bank payment flow that users had to repeat each time.
What’s new here is the reusable setup: connect once (with consent), then repeat wallet top-ups with a single in-app tap—aimed at making account-to-account payments feel like an everyday payment method rather than an occasional transfer.

Step 1: Launch of One-Tap Pay by Bank Experience

Lean Technologies and Ziina have launched what they describe as the UAE’s first “One-Tap Pay by Bank” experience under the country’s Open Finance framework—an important marker for account-to-account payments in a market that has been steadily building the regulatory and technical rails for API-driven money movement.

At its core, the feature is designed around a simple consumer promise: connect your bank account once, then fund your Ziina wallet in the future with a single tap. That “one-tap” framing matters because it targets the most common friction points in bank transfer-based payments—repeated authentication steps, credential entry, and being pushed out of the app into a bank portal to complete the flow.

The capability is built on Lean’s Deposits solution and delivered inside Ziina’s wallet experience. In practical terms, it turns Pay by Bank from something that feels like a one-off bank transfer into something closer to an “account on file” payment method—without relying on cards. The companies position this as a sign that the UAE’s Pay by Bank ecosystem is maturing: regulation is live, infrastructure is in place, and product teams can now focus on the kind of low-friction experiences that drive habitual use.

The launch is also a partnership story. Ziina brings the consumer-facing payment journey—where speed and simplicity determine whether a feature becomes part of daily behavior. Lean brings the Open Finance connectivity and payment initiation infrastructure that makes “tap once” possible while staying within a regulated framework.

Connect and Top Up Securely
1) First-time setup (once): In Ziina, choose Pay by Bank → select your bank → complete the bank’s authentication/consent step.
Checkpoint: you should land back in Ziina with the bank account shown as a connected funding source.
2) Later top-ups (repeat): Tap “Top up” → choose the connected bank account → confirm.
Checkpoint: no re-entry of bank credentials and no redirect out to a bank portal for each top-up.
3) Ongoing control: If you change banks, lose a device, or simply want to stop using it, remove/revoke the connected account from the app’s linked accounts/consents area.

Step 2: Secure Connection of Bank Accounts

The “one-tap” experience hinges on a secure first step: a user connects their bank account, and that connection can then be used for future wallet top-ups without repeating the same setup each time. Lean and Ziina emphasize that this removes two common sources of drop-off in bank-based payments: re-entering credentials and being redirected to a bank portal.

This is where Open Finance becomes more than a policy label. Under an Open Finance framework, connectivity and payment initiation are designed to be consent-based and API-driven. The user’s permission is central: the account connection is established with customer consent, and the resulting setup enables subsequent payments to be initiated with far less friction than traditional bank transfer flows.

Lean’s Deposits solution is the named building block behind the feature. While the companies do not publish a step-by-step technical diagram, the product outcome is clear: a bank account becomes a reusable funding source for Ziina, allowing repeat top-ups without repeating the same authentication journey.

Security and trust are not optional in this model; they are prerequisites for adoption. The companies position the experience as “securely connect once,” suggesting that the initial linking process is the moment where identity, consent, and authorization are handled—so that later payments can be initiated quickly while still operating inside the rules of the Open Finance regime.

The result is a shift in user perception: Pay by Bank stops feeling like a manual bank transfer and starts feeling like a native payment method inside the wallet. That change—more than any single technical detail—is what enables the next step: recurring behavior.

Secure Account Connection Essentials
What “securely connect once” typically includes in Open Finance-style linking

• Clear consent: what you’re authorizing (e.g., wallet top-ups), and which account(s) it applies to
• Strong authentication at setup: the bank verifies it’s really you (often via the bank’s own auth flow)
• In-app confirmation: you return to Ziina and can see the connected account as a funding source
• Consent management: a place to view connected accounts and remove them if you no longer want one-tap top-ups
• Expiry/renewal behavior: what happens when the connection times out or needs re-authorization (varies by implementation)

Step 3: Transition to Recurring Payments

Until now, Pay by Bank in the UAE had been available primarily as single, instant payments. Lean’s vice president of sales, Omar Hamada, framed the significance of this launch in exactly those terms: the market had “live” Pay by Bank, but it was limited to one-time transactions. The Lean–Ziina implementation is presented as proof that the infrastructure can support recurring, low-effort payment experiences—the kind that become part of how people pay every day.

“Pay by Bank has been live in the UAE for some time, but until now, it has only been available as single instant payments.”
Omar Hamada, Vice President of Sales, Lean Technologies

That distinction—single payment versus recurring experience—can sound subtle, but it is often the difference between a feature that exists and a feature that scales. One-off payments are useful, yet they don’t necessarily change habits. Recurring, low-friction flows do, because they reduce the “activation energy” required each time a user wants to move money.

Ziina’s co-founder and head of engineering, Talal Toukan, linked the product decision to a high-frequency user action: funding the wallet. If wallet top-ups are among the most common actions in the app, then shaving off steps is not a cosmetic improvement; it is a direct bet on engagement and retention.

“People expect financial products to be as simple and intuitive as the best consumer technology they use every day.”
Talal Toukan, Co-Founder and Head of Engineering, Ziina

The companies also position this as a broader market signal: with regulation live and rails available, the competitive frontier shifts from “can we initiate a bank payment?” to “can we make it feel effortless enough to be used repeatedly?” In that framing, One-Tap Pay by Bank is less a single feature and more a template for how Open Finance payments can evolve—from capability to convenience.

Step 4: Infrastructure Support for Seamless Payments

The Lean–Ziina launch is explicitly described as being “under the Open Finance framework,” and that matters because it implies a regulated environment for data access and payment initiation via APIs. The companies present the release as evidence that the UAE’s underlying infrastructure is ready for more advanced payment journeys—specifically, journeys that don’t require users to repeatedly authenticate or bounce between apps.

Lean’s role is positioned as infrastructure: Open Finance connectivity and the Deposits solution that supports the “connect once” model. Ziina’s role is experience: the consumer-facing interface where a wallet top-up can be reduced to a single tap. Together, they are demonstrating how account-to-account payments can be packaged into a smoother digital flow.

This is also why the announcement frames the moment as a step in the “maturation” of account-to-account payments in the region. In many markets, the early phase of Pay by Bank is dominated by proofs of concept and one-time transfers. The next phase is about reliability, repeatability, and user experience—turning a regulated payment initiation capability into something that can compete with the convenience users associate with other payment methods.

Lean’s broader footprint provides context for why it can play this infrastructure role. The company is described as supporting more than 400 companies, processing over $5 billion in transaction volume, and connecting upwards of 2 million accounts. Those figures don’t prove the success of this specific feature on their own, but they do indicate that Lean operates at a scale where production-grade connectivity is the baseline expectation.

In short, the “one tap” is the visible tip. Underneath it is a combination of regulated Open Finance rails, API connectivity, and a deposits/top-up use case that is common enough to justify optimizing every step.

Partner Operating Scale Context
Scale context (publicly reported company figures)

• Lean Technologies: reported as supporting 400+ companies, processing $5B+ in transaction volume, and connecting 2M+ accounts.
• Ziina: reported as serving 260,000+ users.

These numbers are best read as “operating scale” context for the partners—not as performance results for the new one-tap feature itself.

Step 5: Simplifying Financial Products for Users

Both companies repeatedly return to one theme: users now judge financial products by the standards of consumer technology. That expectation is not abstract; it shows up in the smallest moments—like how quickly someone can fund a wallet.

Ziina’s Talal Toukan described wallet funding as one of the most common actions, making it a natural target for simplification. The One-Tap Pay by Bank experience is therefore positioned as a user-centric redesign: remove steps, keep the user inside the app, and make money movement feel “more effortless.”

That emphasis on simplicity is also a strategic statement about where Open Finance value will be created. Once the regulatory framework exists and payment initiation is possible, differentiation shifts to product design: consent flows that don’t confuse users, top-ups that don’t require repeated setup, and payment experiences that feel consistent with what people already expect from modern apps.

The launch also underscores a broader point about account-to-account payments: they can support increasingly seamless digital payment journeys when the infrastructure and the interface are designed together. Lean describes the capability as combining Ziina’s consumer payment experience with Lean’s Open Finance infrastructure—an explicit acknowledgment that neither layer alone is enough. Infrastructure without a great UX remains niche; UX without regulated connectivity can’t deliver on the promise.

In the near term, the most visible benefit is speed and reduced friction for Ziina users topping up their wallets. In the longer term, the same design principle—connect once, pay repeatedly with minimal effort—sets a direction for how Pay by Bank can become a default behavior rather than an occasional alternative.

Designing Seamless Repeat Payments
A simple UX framework for “connect once, pay repeatedly” products

• Reduce steps in the repeat action: optimize the second, third, and tenth top-up—not just the first-time setup.
• Keep users in one place: avoid unnecessary redirects that feel like you “left the app” mid-payment.
• Make consent legible: say what’s being authorized, for what purpose, and what the user can change later.
• Design for recovery: show clear states for “connected,” “expired,” “needs re-auth,” and “removed.”
• Earn trust with control: make it easy to revoke a connection and switch funding sources.

Conclusion: The Future of Payments in the UAE

Embracing Innovation

The Lean–Ziina One-Tap Pay by Bank launch is best understood as a maturity milestone: Pay by Bank in the UAE is no longer framed only as “instant, one-time transfers,” but as a foundation for recurring, low-friction payment experiences under Open Finance.

By enabling users to securely connect a bank account once and then top up a wallet with a single tap, the partnership targets the everyday moments that determine adoption. It also demonstrates a practical division of labor that is becoming common in fintech: infrastructure providers build regulated connectivity, while consumer platforms translate that capability into intuitive product journeys.

The Road Ahead for Digital Payments

The announcement suggests the next competitive wave in UAE payments will be less about whether Open Finance payments can be initiated—and more about how seamlessly they can be repeated. With regulation live and infrastructure in place, the focus shifts to building experiences that users trust and return to.

If One-Tap Pay by Bank becomes a pattern others follow, it could accelerate the normalization of account-to-account payments for routine actions like wallet funding—moving Open Finance from a framework on paper to a payment behavior in daily life.

Benefits and Adoption Hurdles
What gets better—and what still needs to go right
Benefits

• Faster repeat top-ups: less friction for a high-frequency action
• Fewer drop-off points: fewer redirects and repeated credential steps
• Stronger “habit potential”: easier for Pay by Bank to become a default behavior

Adoption hurdles

• User understanding: people need to trust what “connect once” means and how to undo it
• Bank coverage and consistency: the experience is only as smooth as the participating bank flows
• Renewal moments: if/when re-authorization is required, that step must be clear and low-friction

Perspective note: This analysis is written from the viewpoint of Martin Weidemann (weidemann.tech), drawing on hands-on work building and scaling payment products and infrastructure across regulated markets—where the biggest adoption gains often come from reducing repeat authentication, redirects, and other UX friction in high-frequency flows like wallet top-ups.

This article reflects publicly available information at the time of writing and focuses on product and user-experience implications of the launch. Bank coverage, consent durations, and in-app flow details may vary by provider and can change as Open Finance implementations evolve. Any scale metrics are offered as general context and should not be read as evidence of outcomes for this specific feature.