How To Use Visa Flexible Credential

Visa Flex Credential

How to Use Visa Flex Credential APIs

In the Visa Flex Credential (VFC) Managed service, the issuer is provided a set of APIs to manage the basic functions of the Credential; Create, Replace, Update, and Delete to engage with VFC.

This is an overview of how to onboard and apply the configuration to use VFC Accounts and APIs. The goal of integrating with VFC API is to enroll, configure and retrieve credential settings.

The VFC APIs cover enrolling/managing credentials and creating, modifying, and deleting, rules and relationships.

Card Enrollment API

Use the Card Enrollment API to enroll the Credential in Visa system for usage in VFC Accounts and returns a document ID which can be used in subsequent API calls instead of the Credential.

The Card Enrollment API supports the following functions:

Enrolls the PAN in Visa system for usage in VFC Accounts and returns a documentId which can be used in subsequent API calls.
Deletes the PAN from Visa Transaction Controls and VFC participation.
Updates any of the attribute fields for an existing documentId.
Procures all the relevant parameters for the card being queried.

Relationship Management API

Use the Relationship Management API to accept the document ID of the Primary (Lead) Credential in the relationship as a path query parameter.

The Relationship Management API supports the following functions:

Accepts the documentId of the primary card in the relationship as a path query parameter. Multiple secondary cards can be added to the primary card in a relationship for a single API call.
Replaces the existing relationship where the documentId in the path is the primary with the secondaries specified in the API.
Returns secondary card details related to the primary card referred by the path parameter–documentId.
Deletes the relationship where the path parameter, documentId is the primary.

Rules Management API

Use the Rules Management API to create new rules for the Primary (Lead) Credential document ID in the path parameter.

The Rules Management API supports the following function:

Customer rules profile and cards mapping stored in Visa system.
Changes the rules associated with a primary PAN documentId. The existing rule with the same priority as the input rule will be replaced.
Returns the rules associated with the primary PAN documentId in the path parameter.
Deletes the rules for a given Lead PAN’s documentId.
Deletes a specific rule(s) for a given Lead PAN’s documentId and rule ID.

Authorization Decision API

Use the Authorization Decision API to request an authorization decision recommendation based on Cardholder rules.

The Authorization Decision API supports the following function:

Requests an authorization decision recommendation for a pending transaction based on issuer-defined and/or cardholder rules.

Transaction Search API

Use the Transaction Search API to retrieve a list of authorization decision records for completed transactions.

The Transaction Search API supports the following function:

Retrieves decision records associated with a specific card or document identifier.

Notification Delivery Callback API

Use the Notification Delivery Callback API to receive notifications about authorization decision details.

The Notification Delivery Callback API supports the following function:

Delivers outbound notifications to an issuer-configured endpoint when alerts are enabled.

Possible Control Types


Category	Control Type	*Description*
Simple Rules	One-Time Override	TCT_ONE_TIME_OVERRIDE	This rule temporarily overrides all the existing rules by issuer/consumer and draws from the funding source assigned in this rule for the upcoming transaction. This rule is executed only once, after which the One-Time Override reverts to an inactive state. All pre-configured rules in play by issuer/consumer (prior to the One-Time Override) continue to apply for future transactions after the One-Time Override becomes inactive.
Time-Based Rule	TCT_DEFAULT	This rule targets the designated funding source if the transaction occurs within the specified time frame between startTime and endTime.
Default Payment Method	TCT_DEFAULT	This rule targets a designated default funding source for the transaction in the absence of other smart rules.
Smart Rules	Amount-Based Rule	TCT_DEFAULT	This rule targets a designated funding source if the transaction amount falls within the minAmount and maxAmount range. This rule can be combined with other rule types.
Merchant-Category Based Rule	MCT_ADULT_ENTERTAINMENT, MCT_AIRFARE, MCT_ALCOHOL, MCT_APPAREL_AND_ACCESSORIES, MCT_AUTOMOTIVE, MCT_CAR_RENTAL, MCT_DINING, MCT_ELECTRONICS, MCT_GAMBLING, MCT_GAS_AND_PETROLEUM, MCT_GROCERY, MCT_HOTEL_AND_LODGING, MCT_HOUSEHOLD, MCT_PERSONAL_CARE, MCT_SMOKE_AND_TOBACCO, MCT_SPORT_AND_RECREATION	This rule targets a designated funding source if the transaction is initiated at a merchant from a pre-set merchant category e.g., AIRLINE.
Transaction Type-Based Rule	TCT_ATM_WITHDRAWAL, TCT_AUTO_PAY, TCT_BRICK_AND_MORTAR, TCT_CONTACTLESS, TCT_CROSS_BORDER, TCT_E_COMMERCE, TCT_FUNDS_TRANSFER, TCT_PURCHASE_RETURN, TCT_BNPL, TCT_OCT	This rule targets a designated funding source if the transaction is of a particular transaction type based on various transaction attributes.
Currency Based Routing	TCT_MULTICURRENCY	This rule targets enhanced cross-border transactions by utilizing multiple currencies. Multi-Currency is currently offered for both debit and prepaid transactions.
Individual Merchant-Based Rule	MCT_CAID	This rule targets a designated funding source if the transaction is initiated at a merchant with a specific Card Acceptor ID. Card Acceptor ID (CAID) is an Issuer Rule—Issuers can provide the list of Merchant IDs to configure in the back end.
Fallback Rules	Fallback	FALLBACK	This rule allows for the designated funding source to be utilized if the funding source specified in the matched smart rule cannot be applied or a match with a smart rule can’t be established. Mandatory Fallback must be set as an issuer rule with the lowest priority.