Explain It in 30 Seconds
A customer has more than one way to fund a purchase.
Ordinarily, using another source can mean selecting a different card or credential.
Flexible Credential gives a participating issuer a way to put supported choices behind a common credential.
The cardholder's selection happens through the issuer's permitted experience.
At the merchant, the payment still needs normal acceptance and processing. The issuer must connect the choice to the correct account treatment.
The product simplifies access to funding options; it does not make those options financially identical. [S46][S47]
Where It Sits in Visa
Within Visa, Flexible Credential connects issuer account choices with a common payment credential.
The issuer supplies the accounts and customer interface; Visa supplies the supported credential capability and processing framework.
Unlike a wallet displaying unrelated cards, the offering depends on an issuer's eligible linked program.
The Problem It Solved
Several financial products can require several credentials to carry, maintain or select at checkout.
A participating issuer can instead make its supported funding options accessible through one credential.
That is useful only if the customer understands which account will fund the purchase. Fewer visible cards should not mean less clarity about the financial choice.
How It Works — Simple Version
The August 2024 U.S. merchant FAQ describes an issuer linking a single credential to two or more accounts within that issuer.
Before an eligible purchase, the cardholder selects the funding source, commonly through the issuer's app.
The merchant and acquirer interact with the lead credential, while the issuer's choice determines the supported funding treatment. [S47]
A simplified sequence is:
1. The issuer establishes an eligible program and account links. 2. The customer makes a supported selection. 3. The customer presents the common credential. 4. The transaction information reflects the applicable funding source. 5. The issuer applies the payment to the selected account.
That dated U.S. model is an explanation of a specific implementation, not a worldwide promise that any account at any bank can be linked.
Lead Credential and Funding Source
The lead credential
The customer presents this consistent access point for the supported transaction.
The funding relationship
An eligible linked account determines the financial treatment. Debit and credit can have different consequences behind the same visible card.
The issuer's mapping
Processing must connect the customer's selection to the correct account and records.
The common credential simplifies access; it does not create one undifferentiated balance.
What Changes for the Merchant?
The August 2024 U.S. FAQ describes Account Funding Source and Product ID information in the authorization response and corresponding clearing treatment. [S47]
The merchant need not manage all the customer's account relationships, but still needs the applicable transaction information and acceptance arrangements.
One presented credential does not make every funding choice identical in processing.
A Documented Example: Olive
SMFG's 2023 report describes Olive launching in Japan on March 1.
Its Flexible Pay function offers supported credit, debit and points-payment choices through an app using one card. Development involved SMBC, Sumitomo Mitsui Card, Visa and other participants. [S96]
The case shows the coordination behind a unified interface. It does not establish the same funding mix or account structure in every market.
Choice Happens Within a Program
The issuer defines eligible choices and how to select them.
The U.S. FAQ describes transaction-by-transaction selection and static or dynamic pre-purchase rules. It does not establish universal switching after a purchase or access to unrelated banks' accounts. [S47]
The delivered program, rather than the word flexible, defines the customer's options.
Who Uses It?
Cardholders
They use the supported experience to choose how a purchase is funded.
Their need is understandable access, not simply a larger menu.
Issuers
They assemble the accounts, digital interface and customer proposition.
Their implementation determines whether the choice is actually useful.
Issuer processors
They help connect the customer's selection with the program's transaction handling.
Merchants and acquirers
They accept and process the presented credential within the applicable arrangements.
The roles remain separate even when the customer sees one simple card.
How the Economics Work
An issuer may make its products easier to use, but needs to compare that benefit with technology, servicing and product costs.
Visa supplies a capability within its payment-services ecosystem. The product materials do not establish a universal standalone fee.
For the cardholder, account fees, repayment terms and balance limits remain separate. A unified interface does not make the underlying products financially interchangeable.
What It Depends On
Issuer participation
The institution must offer an eligible program and link supported accounts.
Processing
The selected funding treatment must be reflected correctly in transaction handling.
Digital experience
The customer needs to understand the choice and whether it has taken effect.
DPS describes the capability as API-enabled for issuer frameworks; that does not make integration or support unnecessary. [S48]
Servicing
The institution needs records that explain which funding source applied.
The dated U.S. FAQ directs cardholders questioning an incorrect funding source to their issuer. [S47]
Market and program scope
A capability available in one implementation is not evidence of identical availability elsewhere.
The actual program, rather than the product's name, defines the supported experience.
What Depends on Flexible Credential
Participating issuers can build account-selection experiences around the capability.
Their apps, processing and customer service need a consistent record of the selection. Otherwise, a simple interface can conceal a transaction funded differently from what the customer intended.
Why It Matters to Visa
Visa can make its credential useful across several supported issuer products without requiring a separate visible card for each.
That extends the issuer relationship around the payment interface. Its value depends on clear selection and correct transaction treatment, not the removal of visible cards alone.
Before / After
Several products, several credentials
The customer selects separate payment instruments to access different funding relationships.
One supported credential, linked choices
The issuer provides a common access point with an eligible account-selection experience.
Access changes; account terms and issuer responsibilities do not.
What Most People Misunderstand
“It links every bank account worldwide.”
Participation and eligible issuer programs define the scope.
“One card means one pooled balance.”
The underlying funding relationships remain distinct.
“The customer can always change the funding source after buying.”
The documented U.S. model concerns pre-purchase selection. It is not proof of a universal retrospective feature.
“The merchant sees no relevant funding distinction.”
Transaction information and applicable treatment still matter.
Key Milestones
March 2023 — Olive
SMFG's documented launch illustrates a collaborative app-based use of the payment functionality in Japan. [S96]
May 2024 — Naming change
The U.S. FAQ states that Visa Multiple-Account Access Service was renamed Visa Flexible Credential effective May 2024. [S47]
Current Flex Credential terminology
Visa's current product material uses Flex Credential positioning.
A name change does not, by itself, establish a new independent financial institution or identical features in every market. [S46]
Evidence
- [S46] Current product positioning and scope of marketing research.
- [S47] The explicitly dated U.S. merchant model, transaction treatment and naming history.
- [S48] Issuer-processing context.
- [S96] SMFG's original Olive development account.
The general before/after comparison explains the customer-access mechanism. It does not extend a regional program into a worldwide availability claim.