What Is Paze? The Bank-Backed Digital Wallet Merchants Should Know in 2026

In 2023, Paze was a press release with ambitions. Today it's a live checkout option backed by seven of the largest banks in the United States, covering 165 million eligible cards, with major integrations at Fiserv, Nuvei, Worldpay, and ACI Worldwide. This post explains what Paze is, how it performs, and how it compares to Apple Pay, PayPal, and Zelle so merchants can make an informed decision about adding it to checkout.

The number that frames the whole conversation: 61% of consumers abandoned a purchase in 2024 because their preferred payment method wasn't offered, according to ACI Worldwide. Every wallet decision is a conversion decision, which means every wallet decision is worth making deliberately.

What is Paze, and how does it work?

Paze is a digital checkout wallet created by Early Warning Services (EWS), the same company that built Zelle in 2017. It's offered directly through participating banks and credit unions rather than as a standalone app, which makes it structurally unlike every other major wallet on the market. Think of it less like a new app consumers have to download and more like a feature their bank switched on for them in the background, the way a new employee shows up on their first day already knowing where the coffee machine is.

The seven founding banks are Bank of America, Capital One, Chase, PNC, Truist, U.S. Bank, and Wells Fargo. More than 165 million credit and debit cards are already loaded into the Paze checkout solution, per ACI Worldwide's January 2026 announcement, and the wallet is on track to cover 270 million eligible cards by year end.

Eligible cardholders at participating banks find their cards already present in the wallet and authenticate through their existing bank app or via an email confirmation. No new account, no new password, no app store visit required. For merchants, this means a portion of their checkout audience arrives pre-enrolled, which is an enrollment model with no real parallel among competing wallets.

Paze is an e-commerce-only solution, at least for the moment. It operates as a checkout button on a merchant's website, not a tap-to-pay option at a physical point of sale. Early Warning Services has acknowledged that the line between online and in-store commerce is blurring (curbside pickup being the obvious example), and future functionality may follow. For the moment, Paze is built to fix the part of the payment experience that causes the most revenue leakage: the online checkout form.

The most consequential thing Paze does is keep card numbers out of merchant systems entirely. When a consumer pays with Paze, the merchant receives a network token rather than the raw Primary Account Number, and the actual card number stays with the bank and the card network, never entering the merchant's infrastructure.

What are the advantages of accepting Paze?

Paze makes a merchant-friendly case across four distinct dimensions: cost, transaction performance, consumer trust, and checkout experience. Each one is worth examining on its own terms, because taken together they describe a wallet that earns its place in checkout without asking merchants to absorb new fees or take on integration complexity to get it there.

Zero merchant fees and a real interchange benefit

Paze doesn't charge merchants a wallet fee. The only costs involved are the standard transaction processing fees merchants are already paying, which alone separates Paze from much of its competition. Beyond the zero fee, network-tokenized transactions processed through Paze can qualify for interchange reductions, because card networks treat tokenized card-not-present transactions as lower risk. Visa's network token pricing, for instance, offers up to 10 basis points of reduction on card-not-present transactions, per NMI's analysis of network token economics. Ten basis points sounds modest until it runs across millions of transactions a year.

Fraud rates drop and authorization rates rise

Network tokenization drives a 28% reduction in fraud compared to non-tokenized transactions and delivers approximately a 3% lift in authorization rates based on tokenized usage, per card network benchmarks cited in Paze's own tokenization documentation. Understanding how payment data is protected through tokenization makes it clear why those numbers hold: false declines are a stealthy destroyer of merchant revenue, and research cited by Paze shows that 33% of U.S. consumers drop a retailer entirely after a false decline. A single bad authorization event carries compounding lifetime value consequences that never show up cleanly on a dashboard.

Tokenized credentials also prevent mistyped or invalid card numbers from entering the payment flow, since the consumer is never manually entering a 16-digit number to begin with. The checkout form, historically a reliable source of typos, autofill errors, and abandoned intent, disappears from the equation entirely.

Bank-backed trust converts skeptical shoppers

The average cart abandonment rate sits at 70.22%, calculated from 50 separate studies by the Baymard Institute, and 19% of shoppers who abandon cite distrust of the site with their card information as the direct cause. Paze addresses that concern through its bank-backing. A Paze survey found that 82% of Americans trust their bank's security more than that of outside payment apps, which is the kind of trust transfer that no fintech startup can buy. When a consumer sees a Paze button at checkout, the implied message is that their bank is handling the transaction, not a third party they have never heard of.

There's also a meaningful payment lifecycle management benefit for merchants running recurring billing. Because Paze uses network tokens that update automatically when a card is lost, replaced, or reissued, subscription merchants stop bleeding revenue from stale credentials, with the card updating in the background and neither the merchant nor the consumer required to do anything about it.

Pre-enrolled shoppers arrive ready to buy

Paze's checkout experience is functionally one click. A consumer selects the Paze button, authenticates through their bank app, and the sale is complete. No additional form fields, no confirmation email loop, no new password generated and immediately forgotten. The whole process, on a modern browser, takes a few seconds, which is approximately how long it takes the average shopper to reconsider a purchase when a checkout form asks for their billing zip code for the third time in a week.

For merchants focused on alternative payment methods and checkout conversion, the relevant framing is this: Paze doesn't require consumers to change their behavior, because enrollment already happened at the bank. That's a fundamentally different proposition from every other wallet in the market, all of which require some degree of consumer action before they're useful at checkout.

How does Paze compare to the competition?

Every merchant evaluating Paze will run the same mental calculation: we already accept Apple Pay, PayPal, or both, so what exactly does Paze add? The answer depends on which wallet you are comparing it to, because Paze occupies a different lane with each of them.

Paze vs Apple Pay

Apple Pay is the most entrenched wallet in U.S. physical retail, accepted at over 90% of domestic retailers and carrying 64% brand awareness among consumers, per JD Power data. It has been in the market for over a decade, which means it has had time to become habitual for a large portion of iPhone users. Asking Paze to compete with that head-on is like asking a well-funded startup to challenge a company that already has the top app on every device in your pocket.

The strategic reality is that Apple Pay and Paze aren't chasing exactly the same consumer. Apple Pay's e-commerce functionality runs most cleanly within the iOS and Safari ecosystem. Paze is browser-agnostic and device-agnostic, which means it reaches cardholders that Apple Pay doesn't surface as cleanly for merchants on the open web. For merchants whose audiences skew toward Android, or who sell through non-Safari browser environments, Paze fills a real gap rather than a redundant one.

Both wallets use network tokenization, so the security architecture is comparable. Neither charges merchants a direct wallet fee. The distinction is in reach and ecosystem: Apple Pay runs deep inside its own, and Paze is designed to run wide across a bank-issued card base that device wallets don't fully cover.

Paze vs PayPal

PayPal is the most recognized digital wallet brand in the U.S., with 82% consumer awareness and 37% preference for online purchases, according to JD Power, and 429 million global users. It has the kind of installed base that makes a payments leader feel comfortable putting it in checkout and moving on with their day. Paze has none of that history yet, and pretending otherwise wouldn't serve anyone.

What Paze does have is cleaner economics for merchants. The Spreedly PayPal connection exists precisely because PayPal is a dominant channel, but PayPal's Fastlane may introduce merchant fees. A Paze transaction avoids both an Apple Pay fee and the ACH-steering dynamics that PayPal can introduce, per analyst Andrew Dresner's January 2025 breakdown of wallet economics. For merchants, that means Paze operates closer to a transparent cost structure.

For subscription and recurring billing merchants specifically, Paze's automatic token lifecycle updates make a concrete, measurable difference in decline rates. When a card is reissued, the network token refreshes, the charge succeeds, and the recurring payment stack keeps running without a dunning campaign to clean up the mess.

Paze vs Zelle

Paze and Zelle aren't competing products, and the comparison surfaces mostly because Early Warning Services built both of them. Zelle facilitates direct bank-to-bank person-to-person transfers. Paze is a card-based e-commerce checkout tool. Zelle pays a friend back for dinner, and Paze pays the restaurant that served it. The use cases share a parent company and nothing else.

How has Paze grown since its launch?

Paze's rollout history is a useful corrective to both the hype that surrounded its launch and the skepticism that followed its slow start. The wallet launched in earnest in 2024, with U.S. Bank becoming the first institution to publicly announce a cardholder rollout in September of that year, per Banking Dive. What followed was a steady accumulation of processor partnerships that did more for merchant reach than any individual brand announcement could.

Fiserv added Paze in June 2025. Nuvei followed in September 2025, noting that participating retailers already included Sephora, Roku, and Harry & David, per Digital Transactions. Worldpay partnered with Paze the same month as Fiserv. ACI Worldwide then integrated Paze into its Pay.On orchestration platform in January 2026, projecting support for up to 16 million U.S. e-commerce transactions across its merchant base during the year. Early Warning expanded further in March 2026 with new Citi and Fiserv partnerships targeting market share currently held by Apple Pay and PayPal.

Early Warning has also invested in consumer brand visibility, with jersey patch partnerships at the Atlanta Hawks and New York City FC, and a gaming commerce integration with Xsolla announced through the second half of 2025. These are consumer-facing plays designed to build the brand awareness that Paze still lacks relative to its competitors, the wallet equivalent of printing your name on the stadium before trying to fill the seats.

The honest picture is that Paze is growing steadily without yet achieving the reflexive consumer adoption that Apple Pay and PayPal enjoy. Early Warning's own Chief Partnership Officer acknowledged in March 2026 that the largest addressable opportunity for Paze is reaching the substantial segment of consumers who still use guest checkout and have never adopted any mobile wallet at all, per American Banker. That population is larger than most assume, and converting them requires zero habit change, since those consumers have no existing wallet habit to displace.

For merchants, that framing is the most useful one. Paze is a bet on reaching a pre-enrolled, bank-trusted audience that still types card numbers into forms, and converting them through a checkout experience that asks for nothing new from them at all.

How do merchants add Paze to checkout without a standalone integration?

The practical objection to adding any new payment method is the same one it has always been: another integration, another vendor relationship, another support ticket queue to monitor. That calculation is real, and for merchants already managing multiple gateways and wallet connections, it carries genuine weight. The Spreedly connections ecosystem exists because managing each of those relationships individually is the kind of engineering overhead that compounds in ways nobody budgets for correctly.

Paze is gateway-agnostic, which means it works with any processor that supports network tokens. That architecture is what makes it a clean fit for a payments orchestration layer, with no bespoke build required for each gateway relationship and no maintenance surface area that scales with every new payment method added to checkout. ACI Worldwide's CEO Tom Warsop described the alternative plainly in the January 2026 announcement: "Every new checkout option used to mean another integration project, another vendor relationship, another support headache." Merchants using an orchestration layer connect once and enable Paze, or any wallet that follows it, without touching their core systems.

Spreedly Connect is that single connection. Merchants that add Paze through Connect get access to the wallet, the network token routing, and the gateway-agnostic flexibility that Paze is built for, without rebuilding checkout from scratch for every new payment method the market produces next quarter. Olo used Spreedly to enable mobile wallets including PayPal and Venmo across more than 80,000 restaurant locations, without the complexity of managing each wallet integration independently.

The wallet market isn't done evolving. Having an infrastructure that makes the next wallet decision a configuration rather than a project is worth considerably more than the cost of a single integration.

‍