Back to the library
Payment Processing
2026-11-22 9 min read

Visa Pay Credentials and What They Mean for Merchants

Visa Pay is live. The credential is not a card, the holder is not a cardholder, and the acceptance chapter does not mention it even once.

JA

By Jeffrey Anderson

visa rulesdigital walletstokenizationpayment credentialsacceptance
Visa Pay Credentials and What They Mean for Merchants
Key takeaways
  • Visa Pay became effective 24 October 2026 under Section 4.38.1 (ID# 0031255), marked New in that edition.
  • Visa split the definition of Transaction (ID# 0025175) so a Visa Pay Credential Holder, not a cardholder, is the counterparty.
  • A Visa Pay Credential is a Visa-issued token that is expressly not issued as a Card (ID# 0031254).
  • Cardholder rules carry over to Visa Pay Credential Holders by default, unless Visa expressly states otherwise (ID# 0031256).
  • All five existing carve-outs are issuer obligations, including no required PIN under Section 1.4.4.1.
  • The underlying BIN must be charge, debit, or prepaid. Credit is not on the list, and crypto or stablecoin funding is permitted.
  • Chapter 5, Acceptance, contains no reference to Visa Pay, so merchant obligations arrive entirely through the default.

Visa Pay went live on 24 October 2026, and it introduces a payer your acceptance rules have never described. A Visa Pay Credential is not a card. The person holding one is not a cardholder. Visa says the credential may be used at any Visa-accepting merchant, so you will see these transactions whether or not you have heard of the program.

Section 4.38.1 of the Visa Core Rules and Visa Product and Service Rules (ID# 0031255) is marked "New" in the October 2026 edition. It sets the participation requirements. The more consequential change is quieter, and it sits in the glossary.

Visa rewrote the definition of a transaction

The word "Transaction" is the most load bearing term in the rulebook. Visa split it in two (ID# 0025175, last updated October 2026). It is now the use of either:

  • A Payment Credential, "effective 24 October 2026, other than a Visa Pay Credential", to make a payment or exchange value between a cardholder (or an issuer) and a merchant (or an acquirer)
  • A Visa Pay Credential, to make a payment or exchange value between a Visa Pay Credential Holder (or an issuer) and a merchant (or an acquirer)

Read that second limb again. The counterparty is not a cardholder. Every rule you have ever read that says "Cardholder" was written before this limb existed.

What a Visa Pay Credential actually is

The definition (ID# 0031254) is specific. A Visa Pay Credential is a Visa-issued token provisioned to a member that:

  • Is provisioned through, and for use within, the Visa Pay program by an approved participant
  • Is assigned to, or associated with, an existing account held by the member's customer
  • Enables the initiation and processing of transactions using that account
  • Is not issued as a Card
  • Is enabled solely for use cases approved by Visa

So it is a token sitting on top of someone's existing account. It is closer to what you already handle than it sounds, because it moves through the Visa Token Service like any other token. Issuers must enroll in the Visa Digital Enablement Program and participate as a Token Requestor to get one.

The holder is not a cardholder, and the rules bridge that by default

Visa defined the new party too (ID# 0031256): "An individual account holder to whom a Visa Pay Credential is assigned or associated." Then comes the sentence that does the real work:

Applicable Visa Rules setting forth Issuer and other Member responsibilities in relation to Cardholders apply in respect of Visa Pay Credential Holders, unless expressly stated otherwise.

That is a default, not an equivalence. The cardholder rules carry over, except where Visa has carved them out. So the practical question is never "does this rule apply to Visa Pay" in the abstract. It is whether Visa has said otherwise for that specific rule.

Where Visa has already said otherwise

Five carve-outs exist in the October 2026 edition. All five are issuer obligations, which is why the default is comfortable for a merchant today.

RuleSectionCarve-out
ID# 00040191.4.4.1No PIN required
ID# 00040814.1.12.4No cardholder inquiry service, emergency cash, or emergency card replacement
ID# 00309604.1.21.1Exempt from Europe cash-back personalization
ID# 00298698.6.1.1Out of Visa Account Updater on a commercial BIN
ID# 00269894.1.14.1Click to Pay enrollment follows the BIN type

The PIN exemption is worth a moment. Section 1.4.4.1 requires an issuer to make a PIN available to each cardholder, and a Visa Pay Credential is now listed as an exception alongside non-reloadable prepaid cards. Do not design a flow that assumes a PIN is there to fall back on.

The Visa Account Updater line matters more if you bill on a schedule. In the US the Table 8-2 enrollment requirement covers all BINs except a listed set, and that set now reads "Visa Commercial Card BINs or, effective 24 October 2026, Visa Pay Credentials issued using a commercial BIN". Prepaid Card BINs are excluded on the same list. So a charge or debit BIN credential is clearly inside VAU and your recurring billing updates reach it, while a commercial one is expressly outside. Do not assume account updates will follow every Visa Pay Credential.

A bank account, a wallet, or a crypto account can fund one

Section 4.38.1 requires issuers to allow any of three funding sources for the connected account: a bank account, a wallet, or non-fiat currency, with Visa naming "a cryptocurrency or stablecoin account" as the example.

One hard limit comes with it. Footnote 1 points to Section 4.1.1.6 (ID# 0030709), which opens "Card Fronting is not permitted" and bars an issuer from allowing a purchase funded back-to-back from another payment credential or card. A Visa Pay Credential may sit on a crypto balance. It may not sit on someone else's Visa card.

This is not the same thing as selling crypto, and the distinction is easy to lose. The five special condition indicators in Section 7.4.14.1 describe what the customer is buying. Nothing there is triggered by how the credential in front of you happens to be funded. If a Visa Pay Credential Holder funds an account with stablecoins and then buys a mattress, you sold a mattress.

The BIN behind it is never a credit BIN

Section 4.38.1 gives an exhaustive list. The underlying BIN must be one of a charge BIN, a debit BIN, or a prepaid BIN. Credit is absent from that list.

If the credential comes off a commercial BIN, the issuing member must ensure it is used to pay for business-related goods and services, under Section 4.14.1.1. And Visa Accept is available only for Visa Pay Credentials issued on a consumer debit or prepaid BIN, per footnote 3, which narrows the casual seller route considerably.

Which use cases you will actually see

Visa must approve both the program and the specific use cases before launch. The permitted set is listed in the rule:

  • Contactless, including push provisioning to third-party wallets
  • Scan to pay, including Visa QR and approved non-Visa QR standards
  • A card-absent environment transaction
  • Click to Pay
  • Original Credit Transactions and Account Funding Transactions, including person-to-person transfers, subject to regional availability
  • Visa Accept

A pass-through digital wallet operator gets a shorter list. Footnote 2 limits it to contactless, scan to pay, and card-absent environment transactions.

Nothing in the acceptance chapter mentions it

Here is the finding that should shape how you plan. Chapter 5, Acceptance, contains zero references to Visa Pay. So does the dispute resolution chapter, apart from one appendix listing. There is no dedicated merchant acceptance rule and no dedicated dispute rule for this credential.

What Appendix A does do is add the Visa Pay Service Description to the Visa Supplemental Requirements List (ID# 0028043), marked "All, where available". That document is not published. The operational detail therefore sits outside the public rulebook, and the public rules hand your obligations over through the default in ID# 0031256.

That is a reasonable place for Visa to start. It is a thin place for a merchant to stand if a dispute arrives from a payer who is not a cardholder, holding a credential that is not a card, funded by an account you cannot see.

Frequently asked questions

Do I have to accept a Visa Pay Credential?

The rules do not create a separate acceptance decision. Issuers must tell the holder that the credential "may be used at any Visa-accepting Merchant", and the transaction reaches you as a Visa transaction, so your existing acceptance obligations are what govern.

Will it look different at the terminal?

Not usually. It arrives as a token through the Visa Token Service, across contactless, scan to pay, card-absent, or Click to Pay. The absence of a PIN is the one difference worth building around.

Can a Visa Pay Credential be a credit account?

Not under Section 4.38.1 as written. The underlying BIN must be a charge, debit, or prepaid BIN, and credit is not on the list.

Does a crypto-funded credential make my sale a crypto transaction?

No. The special condition indicators apply to what is being bought, not to the funding behind the credential. A normal purchase stays a normal purchase.

Where do my dispute rights sit?

With the cardholder rules, by default. ID# 0031256 extends member responsibilities toward cardholders to Visa Pay Credential Holders unless Visa expressly states otherwise, and so far every stated exception is an issuer obligation.

JA

Jeffrey Anderson, Merchant Placement Specialist

Merchant placement specialist at Gray Merchants. Jeffrey works directly with acquiring-bank underwriting teams across the firm’s 70+ banking relationships to place high-risk and hard-to-place businesses, structure multi-MID accounts, and keep flagged merchants processing. His writing draws on the placement files he works every week: what underwriters ask for, why accounts get declined, and what keeps an approved account open.

Talk to a specialist

Tell us about your business

Share a few details and a specialist reviews your industry, volume, and processing history, then comes back with the right path. No obligation.

  • Underwriting decision in 24 to 48 hours
  • $0 setup fee, dedicated MID
  • Specialist replies within 4 business hours
  • Every term disclosed in writing before you sign

Request a call from a specialist

Are you currently processing?

No obligation. A specialist replies within 4 business hours.

Visa Pay Credentials and What They Mean for Merchants | Gray Merchants