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

Stablecoin and NFT Transaction Coding in Visa's Rules

Visa now codes stablecoins, CBDCs, native tokens and NFTs differently. Five special condition indicators, and the wrong one is a coding error.

JA

By Jeffrey Anderson

cryptocurrencynftvisa rulesmcc codeshigh-risk
Stablecoin and NFT Transaction Coding in Visa's Rules
Key takeaways
  • Section 7.4.14.1 (ID# 0030883) sets five special condition indicators: 1 for a CBDC or tokenized deposit, 2 for a fiat-backed stablecoin, 3 for a blockchain native token or coin, 4 for an NFT, and 7 for anything unknown or unqualifying.
  • Visa's stablecoin definition requires fiat reserves held in cash, government securities, fully collateralized repos or similar liabilities of a central bank, at a licensed financial institution. A crypto-backed token does not qualify for indicator 2.
  • Acquiring non-fiat currency uses a money-movement MCC of 4829, 6012, 6540 or 6051, while buying an NFT or buying goods through a fiat-to-crypto conversion uses the merchant's own primary business MCC.
  • Indicator 4 is mandatory where an NFT is bought as an asset or investment and optional where it is incidental to a good or service, with Visa naming a concert ticket, an airline ticket and a club membership as examples.
  • Footnote 2 overrides the MCC column entirely: if a transaction relates to a high-integrity-risk merchant, the applicable high-integrity-risk MCC must be used instead.
  • An original credit transaction disbursing funds from a staged or stored value wallet after selling or converting non-fiat currency needs the business application identifier and the special condition indicator, the same requirement that applies to crypto-converting gambling payouts.

Stablecoins, central bank digital currencies and blockchain native tokens now carry different transaction codes in Visa's rules. There are five special condition indicators, and picking the wrong one is a coding error on a transaction type that is already under heavy scrutiny.

Section 7.4.14.1 of the Visa Core Rules and Visa Product and Service Rules (ID# 0030883) sets them out:

  • 1 for a central bank digital currency (CBDC) or a tokenized deposit
  • 2 for a stablecoin (fiat-backed)
  • 3 for a blockchain native token or coin
  • 4 for an NFT
  • 7 if the type is unknown at the time of the transaction, or does not qualify for any other indicator

Indicator 7 is the catch-all, and the rule is explicit that "Any other type of non-fiat currency must be identified with the special condition indicator 7". So an unclassifiable asset is not an excuse to omit the field.

Visa's Own Definitions

The rule defines each category, and the definitions are narrower than the industry's loose usage.

A CBDC is "digital currency issued by a central bank, reserve bank or other national monetary authority."

A tokenized deposit is "equivalent to existing deposits, held by a licensed depository institution, recorded on a blockchain." Both of those share indicator 1.

A stablecoin (fiat-backed) is defined at length: "digital assets that maintain financial reserves in a fiat currency in the form of cash, government securities, repurchase agreements that are collateralized fully with government securities, and/or other very liquid recognized liabilities of a central bank or reserve bank, held by a licensed financial institution, recorded on a blockchain."

Read what that excludes. The reserves must be fiat and must sit in that specific set of instruments, held by a licensed financial institution. A token that calls itself a stablecoin while backing itself with other crypto, or with commercial paper outside that list, does not meet Visa's definition. It falls to indicator 3 or 7, not 2.

A blockchain native token or coin is "a digital currency inherent on a blockchain required for performing on-chain transactions such as for payment of fees, that is neither CBDC, a tokenized deposit or stablecoin (fiat-backed)." So indicator 3 is defined partly by exclusion.

An NFT is "a unique digital identifier that is recorded on a blockchain, and is used to certify ownership and authenticity of an asset. It cannot be copied, substituted, or subdivided."

Four Transaction Types, Two Different MCC Rules

Table 7-9 covers four situations, and the split that matters is which MCC applies.

Buying non-fiat currency with a card, a staged digital wallet or a stored value digital wallet uses a money-movement MCC: 4829 wire transfer money orders, 6012 financial institutions, 6540 non-financial institutions stored value card purchase or load, or 6051 non-financial institutions covering foreign currency and non-fiat currency. It also needs the applicable business application identifier and the special condition indicator.

Buying an NFT uses "The MCC that describes the primary business of the Merchant/retailer" instead. So an art platform codes as an art platform, not as a crypto exchange.

Buying goods or services where fiat converts to non-fiat accepted by the merchant, including through back-to-back funding, also uses the merchant's own primary business MCC, plus the indicator. The wallet mechanics behind back-to-back funding are in pass-through versus staged wallets.

An original credit transaction disbursing funds from a staged or stored value wallet after the sale or conversion of non-fiat currency goes back to the money-movement codes, 4829, 6012, 6540 or 6051, with the BAI and the indicator. That is the same identifier requirement that applies to gambling winnings payouts when an OCT converts non-fiat to fiat.

The NFT Indicator Is Sometimes Optional

This is the most practical distinction in the rule, and it turns on why the customer is buying.

Indicator 4 applies where "the Cardholder purchases an NFT as an asset or for investment purposes (for example: digital media or artwork)."

Its use is optional where the "Cardholder purchases a good or service that is incidentally delivered as an NFT", and Visa gives three examples: a concert ticket, an airline ticket, and a club membership.

So an NFT ticket is not treated as a crypto purchase. If you sell event access and the token is just the delivery mechanism, you are not obliged to flag it as an NFT acquisition. If you sell the token itself as the thing of value, you are.

That distinction is worth getting right in both directions. Flagging a concert ticket as an NFT investment invites the risk treatment that comes with crypto coding. Failing to flag a genuine NFT sale is a coding error.

Two Footnotes That Override the Table

The table has two footnotes and both change the answer.

The first: if dynamic currency conversion is offered as part of acquiring non-fiat currency or purchasing an NFT, all the DCC rules apply. Those are strict, and the pre-selection prohibition in particular catches people out. They are covered in dynamic currency conversion rules.

The second is the one to read twice: "If any Transaction is related to a High-Integrity Risk Merchant, the applicable High-Integrity Risk Transaction MCC must be used."

That overrides the MCC column entirely. The high-integrity-risk categories and how Visa classifies them are in quasi-cash, gambling and crypto. If you fall inside one, the table's tidy answers do not apply and the high-integrity-risk code wins.

Why the Coding Matters Downstream

Two reasons beyond compliance for its own sake.

The first is disputes. The crypto legs of the main ecommerce dispute conditions turn on delivery to the wallet address the cardholder supplied, and your defence is the destination wallet address or a blockchain transaction hash that Visa requires to be searchable on an open-source website. That is set out in merchandise not received. Coding a transaction as something it is not makes that defence harder to line up.

The second is that the indicators are new enough that issuer risk models are still being tuned against them. A transaction coded 2 for a fiat-backed stablecoin and a transaction coded 3 for a native token are not the same risk to an issuer, which is presumably why Visa separated them. Getting the indicator right is how you end up in the right bucket rather than the worst one.

What To Check

  1. Confirm your processor is populating a special condition indicator at all, not just an MCC. The indicator is a separate field from the category code.
  2. Map each asset you sell to one of the four defined categories, and default to 7 only where none genuinely fits.
  3. Check your stablecoin assumption against Visa's reserve definition rather than the token's marketing.
  4. Decide, per product, whether an NFT is the asset or the delivery mechanism, and code consistently.
  5. If you are in a high-integrity-risk category, use that MCC and ignore the table's MCC column.

The broader question of which code describes your business is in merchant category codes, and if you are operating as an on-ramp rather than a retailer, ramp provider rules is the closer fit.

FAQ

What are Visa's special condition indicators for crypto?

Five values under Section 7.4.14.1: 1 for a CBDC or tokenized deposit, 2 for a fiat-backed stablecoin, 3 for a blockchain native token or coin, 4 for an NFT, and 7 where the type is unknown at the time of the transaction or does not qualify for any other indicator.

Does buying an NFT use a crypto MCC?

No. An NFT acquisition uses the MCC that describes the primary business of the merchant or retailer. The money-movement codes 4829, 6012, 6540 and 6051 apply to acquiring non-fiat currency, not to NFT purchases.

Do I have to flag an NFT concert ticket as an NFT?

No. Indicator 4 is optional where the cardholder buys a good or service that is incidentally delivered as an NFT, and Visa's examples are a concert ticket, an airline ticket and a club membership. It applies where the NFT is bought as an asset or for investment.

What counts as a stablecoin under Visa's rules?

A digital asset maintaining reserves in fiat currency as cash, government securities, fully collateralized repurchase agreements, or other very liquid recognized liabilities of a central or reserve bank, held by a licensed financial institution and recorded on a blockchain. A token backed by other crypto does not qualify and should not carry indicator 2.

What if my business is high-integrity risk?

Footnote 2 to Table 7-9 overrides the MCC column: where any transaction relates to a high-integrity-risk merchant, the applicable high-integrity-risk transaction MCC must be used.

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.

Stablecoin and NFT Transaction Coding in Visa's Rules | Gray Merchants