Digital Wallets: Pass-Through vs Staged Explained

Digital wallets split into two kinds, and the difference decides whose name lands on your customer's statement. Visa calls them Pass-Through Digital Wallets and Staged Digital Wallets, and it defines each one precisely in the Visa Core Rules and Visa Product and Service Rules (18 April 2026).

Merchants tend to treat "wallet" as one category. It isn't. One kind hands you the card and steps out of the way. The other stands between you and the cardholder for the entire transaction.

Pass-Through: The Wallet Gets Out of the Way#

A Pass-Through Digital Wallet stores and transmits a payment credential, works at more than one merchant, and completes the transaction by "transferring the Payment Credential directly to the Merchant."

Then the line that matters most (ID# 0029533):

"After receiving the Payment Credential, the Merchant finalizes the Transaction with its Acquirer, and the Pass-Through Digital Wallet is not involved in the Authorization, Clearing, or Settlement payment flow."

So it's your transaction end to end. Your acquirer, your interchange treatment, your billing descriptor, your dispute position. The wallet handed you a credential and left.

Staged: Two Transactions Wearing One Coat#

A Staged Digital Wallet works differently, and the name is literal. Visa defines it as functionality that uses both an account assigned to the cardholder and a payment credential to fund that account, completing a transaction "in any order" as two stages (ID# 0029532):

• Purchase: the wallet uses the cardholder's wallet account to pay the retailer.
• Funding: the payment credential funds or reimburses the wallet, and "the Digital Wallet Operator deposits the Transaction for the funding amount with its Acquirer."

Read that second stage carefully. The card transaction is deposited by the wallet operator with the wallet operator's acquirer. Not yours.

Whose Name Is on the Statement#

This is the practical consequence, and Visa spells it out in Table 7-7.

For the funding leg of a staged wallet, the required merchant name is the "Name of DWO" and the merchant outlet location is "the country where the DWO is located."

Your business name is not in that record. The cardholder's statement shows the wallet company.

That table is the whole argument for caring about the distinction. Everything you do to make your descriptor recognisable is undone on a staged wallet, because the funding record was never yours to label.

The Processing Flags#

Staged wallet funding transactions carry a specific signature. Table 7-7 requires MCC 6051 for account funding, a business application identifier of WT, a Staged Digital Wallet indicator, an AFT indicator, and the appropriate card-absent or e-commerce indicator.

Stored value digital wallets are a near neighbour with different codes: MCC 4829, 6012, or 6540, and a business application identifier of FT.

If the wallet can be used to buy cryptocurrency, or the cardholder says the funding will go toward crypto, additional identifiers apply and a high-integrity-risk MCC may be required instead.

Card Fronting Is Not Allowed#

Worth knowing because it comes up whenever someone proposes a clever wallet structure.

Section 5.8.20.1 states plainly that "Card Fronting is not permitted," and that an acquirer "must not allow Back-to-Back Funding from a Payment Credential to another Payment Credential or card" (ID# 0030708). There's a narrow exception for approved programs in the European Economic Area and the United Kingdom.

Funding one card with another card, through a wallet, is not a structure available to you in the US.

A Third Category: The Merchant Wallet#

Visa also defines a Merchant Wallet, and the boundary is narrower than most people assume. It's a wallet usable at a single merchant corporation, or across "limited categories of spend within one line of business," which the rules define as fewer than three MCCs in that line (ID# 0030992).

The rules note a merchant wallet "may evolve into either a Stored Value Digital Wallet or Staged Digital Wallet, depending on the functionality" it grows. If you're building stored balances into your own product, that's the line you're walking toward, and crossing it changes which rulebook applies to you.

Both Can Now Be Driven by an AI Agent#

Effective 18 April 2026, both wallet types may be used to complete an agentic transaction under section 4.1.24.5. Chile follows on 17 June 2026.

That's a recent addition rather than long-standing rule, and it connects to the wider agentic payments framework Visa switched on this year.

What This Means for Your Account#

If you take Apple Pay or Google Pay, you're taking pass-through wallet transactions. They're ordinary card transactions with a token instead of a raw number, and they behave like your other card volume.

If your customers pay you through a staged wallet, the card leg isn't yours. You don't control that descriptor, the interchange on it isn't your interchange, and the cardholder's relationship for that leg is with the wallet company. That's a real difference in a portfolio, and it's the same structural pattern as processing through a payment facilitator rather than on your own MID.

Neither is wrong. But they aren't the same product, and pricing or dispute expectations built on one won't transfer to the other.