Paze is a digital wallet for online checkout, operated by Early Warning Services (EWS), the bank consortium that also runs Zelle. Unlike Apple Pay or Google Pay, which require shoppers to manually add cards to a device wallet, Paze auto-enrolls eligible cards that participating banks already have on file. The shopper doesn’t create a new account or enter card details. The card just appears at checkout.

As of 2026, Paze covers more than 200 million eligible credit and debit cards (Early Warning Services, 2025-2026), making it one of the largest card-on-file networks in the US by enrollment count. Merchant acceptance is a different story, which matters if you’re deciding whether to support it.

Key takeaways:

• Paze auto-enrolls more than 200 million eligible cards from participating banks, without any action from the shopper (Early Warning Services, 2025-2026)
• Paze uses network tokenization, the same security model as Apple Pay and Google Pay
• Paze works online only, not at physical point-of-sale terminals, and only for cards issued by participating US banks
• Merchant acceptance lags enrollment: about 28 retailers accept Paze directly, with broader reach coming through PSP partnerships (Fiserv, Nuvei, Worldpay, ACI Worldwide)

What is Paze?

Paze is a checkout wallet that routes the shopper’s existing bank-issued card through a tokenized transaction, so merchants never receive the real card number. The shopper selects Paze at checkout, confirms through their bank’s app or website, and the payment goes through. No new account, no password, no 16-digit number to type.

EWS, the organization behind it, has operated identity and payments infrastructure for US banks for over 35 years. Zelle is its best-known product. Paze is its push into ecommerce checkout, a market where PayPal, Apple Pay, and Google Pay have been dominant for a decade.

Who’s behind Paze: Early Warning Services and the bank consortium

The founding and current participating banks in Paze include (Early Warning Services / PR Newswire, 2024-2025):

• Bank of America
• Capital One
• Chase
• Citi (added later via a separate expansion)
• PNC
• Truist
• U.S. Bank
• Wells Fargo
• Credit unions including Star One

That ownership structure is why Paze auto-enrolls cards. The banks that issue the cards also control the wallet, so they can add eligible cards automatically. Shoppers activate access through their bank’s own app or at mywallet.paze.com rather than through a standalone Paze download.

This also means Paze’s rollout strategy is different from Apple Pay’s or Google Pay’s. Coverage expands as each bank turns on support and as PSPs and acquirers add Paze to their processing stack, not through a centralized platform update.

How Paze works at checkout

At checkout on a participating merchant’s site, a shopper who has Paze-eligible cards sees the Paze option alongside other payment methods. Selecting it opens a confirmation flow through their bank, which returns an authorization without exposing the underlying card number to the merchant.

Paze uses network tokenization, the same technical approach as Apple Pay and Google Pay. The merchant receives a payment token tied to the transaction, not a card number that could be reused or stolen. Multiple consumer finance sources, including Capital One, U.S. Bank, and Wells Fargo, confirm this as consistent behavior across the wallet.

Paze is ecommerce-only. It does not work at physical point-of-sale terminals (The Financial Brand, 2024). That’s a deliberate scope decision on EWS’s part, positioning Paze specifically against guest checkout and card-on-file experiences online rather than trying to compete with NFC-based in-store wallets.

Paze vs. Apple Pay, Google Pay, and PayPal

The clearest difference is enrollment: Apple Pay and Google Pay require the shopper to load cards into a device wallet, PayPal requires an account, and Paze requires nothing from the shopper beyond having a card issued by a participating bank, because the bank pre-enrolls it (Capital One, 2025).

Dimension	Paze	Apple Pay / Google Pay	PayPal
Enrollment	Auto-enrolled by the issuing bank	Shopper manually adds card to a device wallet	Shopper creates an account
Security	Network tokenization	Network tokenization	Account-based, no card number shared
Scope	US-only, online-only, bank-dependent	In-store and online, global, device-dependent	Online, device-independent
Merchant reach	~28 direct retailers, expanding via PSPs	Broad, established for a decade	Broadest of the four, established for a decade

As of July 2025, Paze was accepted at approximately 28 retailers directly, including Sephora, Roku, GNC, Harry & David, and ShopRite, plus thousands of smaller merchants reachable through GoDaddy’s payment system (factually.co, 2025). That number is growing via PSP partnerships but remains a fraction of Apple Pay’s or PayPal’s acceptance footprint.

Why merchants are watching Paze

The 200 million-card enrollment figure is the reason merchants are paying attention. If a significant share of your US customer base banks with BofA, Chase, Wells Fargo, or Capital One, those cards are already enrolled in Paze. Whether they’ll use it at checkout or default to whatever payment option is already familiar is what merchants are still working out.

The merchant-count gap is also real. Payments Dive reported a leadership change at Paze in 2025 explicitly tied to slow adoption, a rare public acknowledgment that the card-enrollment numbers haven’t translated into broad merchant acceptance yet (Payments Dive, 2025). EWS has responded by routing adoption through PSP and acquirer partnerships, with Fiserv, Nuvei, Worldpay, and ACI Worldwide as the main distribution channels (Payments Dive, 2025).

Note: Most merchants who “support Paze” do so because their existing payment processor added it, not because they built a direct integration.

What adding Paze actually takes on the backend

Paze has a merchant SDK, documented at developer.paze.com and in EWS’s own Merchant SDK Guide (January 2025 PDF). The SDK supports three initiation modes:

• Static buttons
• Dynamic buttons
• Automatic initiation

For merchants doing direct integration, it’s a discrete SDK implementation that sits alongside your existing checkout payment methods.

The more significant question for engineering teams is the PSP layer. Because Paze distributes through PSP and acquirer partnerships, the integration path depends on which processors you already route transactions through. If your primary PSP has enabled Paze on their platform, you may get access through a configuration change rather than a new SDK build. If your PSP hasn’t enabled Paze, or if you route across multiple PSPs directly, each one is a separate conversation and potentially a separate integration step.

That’s the pattern that applies to most new payment methods: the work isn’t always the checkout button. It’s enabling a new method across every processor relationship you maintain, and keeping those integrations current as SDKs and APIs update. For teams already managing multiple PSP integrations, Paze is additive to that maintenance surface, not separate from it.

Supporting Paze without a custom integration

EWS has made an implicit bet on PSP distribution, and that points to the right integration strategy for most merchants: don’t build a direct Paze SDK integration if your existing payment processor already supports it or has it on their roadmap.

For teams running payments through a payment orchestration platform, the question of which individual payment methods are supported becomes a platform question rather than an engineering one. When Paze is available through a processor the platform already routes to, it surfaces as a configuration option. That’s the same model that makes adding regional payment methods like FPX or Sofort tractable without a separate build for each one.

Tip: If you’re evaluating whether to support Paze, check whether your existing PSP has already enabled it at the platform level before scoping an SDK integration. The checkout friction reduction from adding a recognized wallet is real only if the wallet shows up for the shoppers who actually have it enabled.

Frequently Asked Questions

What is Paze?

Paze is a digital wallet for online checkout operated by Early Warning Services, the bank consortium behind Zelle. It auto-enrolls eligible credit and debit cards that participating banks already have on file, so shoppers can pay online without entering card details or creating a new account.

Which banks support Paze?

Bank of America, Capital One, Chase, Citi, PNC, Truist, U.S. Bank, Wells Fargo, and participating credit unions including Star One all back Paze as of 2025. Coverage depends on which bank issued the shopper’s card, so check current participant lists directly with Early Warning Services before citing specific figures.

Is Paze the same as Zelle?

No. Both are operated by Early Warning Services but are different products. Zelle moves money directly between bank accounts. Paze is a checkout wallet for paying merchants with a saved card. They share an operator, not a function.

How is Paze different from Apple Pay or Google Pay?

Apple Pay and Google Pay are device-level wallets that require shoppers to load cards manually. They work both in-store and online. Paze is bank-level: cards are auto-enrolled by participating banks, it’s accessed through a bank app rather than a device, and it only works for online purchases, not at physical terminals.

Is Paze safe to use?

Paze uses network tokenization, so merchants receive a payment token instead of the shopper’s actual card number. Multiple sources, including bank FAQ pages from Capital One, U.S. Bank, and Wells Fargo, describe this as consistent behavior. Confirm current certification documentation directly with Early Warning Services for detailed security specifications.

Which merchants accept Paze?

As of July 2025, approximately 28 retailers accepted Paze directly, including Sephora, Roku, GNC, Harry & David, and ShopRite. Thousands of smaller merchants are reachable through GoDaddy’s payment system. Broader acceptance is driven by integrations with PSPs and acquirers including Fiserv, Nuvei, Worldpay, and ACI Worldwide.

Do I need a separate integration to accept Paze?

It depends on your payment stack. If your existing PSP has enabled Paze, you may be able to activate it through configuration rather than a new build. A direct integration uses Paze’s merchant SDK (documented at developer.paze.com). A payment orchestration platform that routes to Paze-enabled processors can expose it alongside other payment methods through the same integration.