October 2026
Visa network certification
Marqeta is certified with the October 2026 VisaNet Business Enhancements, effective 23 October 2026.Marqeta changes to support this release of Visa
Article 1.1 - Mandate to support the Digital Commerce Authentication Program for domestic and cross-border transactions
Effective 23 October 2026, Visa is expanding Digital Commerce Authentication Program (DCAP) coverage to card-not-present transactions in Canada, Central Europe, Middle East and Africa (CEMEA), Latin America and Caribbean (LAC), and the remaining Asia Pacific (AP) countries, in addition to the existing U.S. domestic coverage. To support this mandate, Marqeta will continue to surface thedigital_commerce_authentication_indicator field for these newly covered regions.
Qualifying transactions will also carry additional account_owner data.
The account_owner object already includes email_address, dob, nationality, occupation, and country_of_birth, and Marqeta already parses account owner address data (street, city, region, postal code, and country) from the same Visa dataset, ahead of exposing it as a new public field.
For more information about the digital_commerce_authentication_indicator and account_owner fields, see Transactions.
Article 2.1 - Changes to Merchant Category Codes
Effective 23 October 2026, Visa is adding four new Merchant Category Codes (MCCs) and their required merchant names across all regions: 3306 (Scoot Ltd, FLYSCOOT), 3884 (Chateraise Hotel Group), 3885 (Ab-Accommo), and 3886 (Noguchikanko Group). This is a purely additive change and doesn’t introduce a new field, edit, or response code. To support this mandate, Marqeta will surface the four new MCC values in thecard_acceptor.mcc field in JIT payloads, webhooks, and the transaction API.
Processing behavior doesn’t change, and no action is required.
For more information, see Transactions.
Article 2.5 - Mandatory changes to Visa Resolve Online
Effective 23 October 2026, Visa is implementing mandatory changes to Visa Resolve Online (VROL) for cancelled recurring transaction and lodging-related disputes. To support this mandate, Marqeta will add new fields toPOST /cases.
For a dispute with dispute_reason set to CANCELLED_RECURRING_TRANSACTION, where the transaction’s card_acceptor.country_code matches one of the following countries, Marqeta will add a new merchant_facilities_withdrawn field to certify that the merchant facilities were withdrawn.
When you set merchant_facilities_withdrawn to true, you must provide the date the lodging facility withdrew or cancelled its services, or made them inaccessible to the cardholder, in the new facilities_withdrawn_date field.
For a dispute with
dispute_reason set to NOT_AS_DESCRIBED_OR_DEFECTIVE_MERCHANDISE, involving lodging services (merchandise_or_services set to SERVICES and a merchant category code (MCC) of 7011 or in the range 3501–3856), Marqeta will add a new date_cardholder_checked_out_from_hotel field to capture the date the cardholder checked out of the lodging facility.
For more information, see Disputes (Visa).
Article 2.8 - Changes to the Digital Commerce Authentication Program to support account funding transactions
Effective 23 October 2026, Visa is extending its Digital Commerce Authentication Program (DCAP) to cover Account Funding Transactions (AFTs) for issuers in the Asia Pacific, CEMEA, and Europe regions. Visa will now send the DCAP indicator to issuers on AFT authorization responses (in Field 111) and on BASE II draft data. There are no changes to the existing DCAP requirements, and testing isn’t required. To support this mandate, Marqeta will set thevdcap_qualified value to true on account funding transactions that carry the DCAP indicator, in the same transaction API surface where it appears today for other transaction types.
No new field is introduced, and no action is needed from you.
For more information, see Transactions.
Article 2.19 - Changes to support the processing of account owner data
Effective 23 October 2026, Visa is changing the numerical format of the account owner date of birth, sent in a single location, for all transactions. The date of birth will use theyyyymmdd format instead of the older ccyymmdd format.
No testing is required.
To support this mandate, Marqeta will pass the account owner date of birth through to you exactly as Visa sends it.
On or after 23 October 2026, the account owner date of birth you receive will be in the new yyyymmdd format.
If your systems read this field assuming the older century-byte format, update your parsing before the effective date.
For more information, see Transactions.
Article 3.2 - Changes to support account funding transactions with a debt repayment indicator
Effective 23 October 2026, Visa is adding support for Account Funding Transactions (AFTs) that carry a debt repayment indicator in the AP, CEMEA, Europe, and LAC regions (excluding the United States, Canada, and Puerto Rico). Acquirers can populate Special Condition Indicator value9 (Payment on existing debt) along with Business Application Identifier BP or CP, for AFTs with MCCs 6012, 6051, or 7322.
The impact for issuers is awareness only.
To support this mandate, Marqeta will surface the special_condition_indicator value DEBT_PAYMENT for debt repayment AFTs in the affected regions, using the mapping already in place.
No new field is introduced, and no action is needed from you.
For more information, see Transactions.
Visa changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.Article 2.7 - Changes to support the customer-related data in the Digital Commerce Authentication Program for issuers
Effective 23 October 2026 across all regions, Visa is continuing to support Digital Commerce Authentication Program (DCAP) transactions that carry customer billing address data. No changes to the Marqeta platform were necessary to support this mandate.Article 2.10 - Changes to response code processing
Effective 23 October 2026, Visa is implementing changes to response code processing. Issuer use of incorrectly applied response codes12, 15, and 57 will be reclassified to response code 05 (Do not honor), and authorizations reclassified this way are included in the generic response code totals.
Excessive use of generic response codes above Visa’s published thresholds results in system integrity fees.
No changes to the Marqeta platform were necessary to support this mandate.
Article 2.11 - Changes to response codes for fraud declines
Effective 23 October 2026, Visa is adding a new response code 83 (Fraud/security) in Field 39 as its highest-priority decline reason. Visa is also adding several new stand-in processing (STIP) reason codes (9212 and 9221 through 9226) in Field 63.4 that identify fraud-condition and Purchase Fraud Detection block declines. This response code and these reason codes were optional starting 17 July 2026, and will become mandatory with the October 2026 release. Marqeta has made all necessary changes to support this mandate, but these changes will not be visible to you.Article 2.14 - Introducing the Visa Infinite Privilege and Visa Infinite Private Deferred Debit products in the Europe region
Effective 23 October 2026, Visa is introducing the Visa Infinite Privilege Deferred Debit and Visa Infinite Private Deferred Debit consumer products for issuers in the Europe region. These products are identified by the existing deferred debit account funding source combined with product ID value I1 (Visa Infinite Privilege) or I2 (Visa Infinite Private). No changes to the Marqeta platform were necessary to support this mandate.Article 2.16 - Changes to Visa Commercial Choice Omni and Visa Commercial Choice Travel programs
Effective 23 October 2026, Visa is restricting the commercial virtual card account ranges for Visa Commercial Choice Travel (product ID X^) and Visa Commercial Choice Omni (product ID X1) to domestic transactions under certain conditions. No changes to the Marqeta platform were necessary to support this mandate.Article 2.18 - Changes to regional fee programs for certain Visa consumer and business products
Effective 23 October 2026, Visa is changing existing AP and CEMEA regional fee programs that apply to transactions associated with certain Visa Infinite, Visa Infinite Privilege, Visa Infinite Private, and Visa Infinite Business products. No changes to the Marqeta platform were necessary to support this mandate.Article 2.20 - Enable cross-border processing for Visa Accept transactions
Effective 23 October 2026, Visa is changing the Visa Accept program to allow cross-border transactions. No changes to the Marqeta platform were necessary to support this mandate.Article 2.22 - Changes to support Automated Fuel Dispenser (AFD) acquirer confirmation advice messages
Effective 23 October 2026, Visa is allowing an additional existing MCC to be sent in0120 Automated Fuel Dispenser (AFD) acquirer confirmation advice messages for domestic and cross-border fuel and non-fuel purchase transactions.
Marqeta has made all necessary changes to support this mandate, but these changes will not be visible to you.
Article 2.23 - Changes to support a new purchase identifier format
Effective 23 October 2026, Visa is implementing a new purchase identifier format to support the Visa Recurrent service. No changes to the Marqeta platform were necessary to support this mandate.Article 3.7 - Changes to the Visa Token Service to identify multi-device provisioning
Effective 23 October 2026, Visa is adding a new Provisioning Context Indicator (Tag 81) to the Visa Token Service, carried in Field 125 for wallet provider data. It identifies whether a token came from multi-device provisioning or an authorized device transfer. Marqeta has made all necessary changes to support this mandate, but these changes will not be visible to you.Article 11.3.1 - Changes to support the Commercial Enhanced Data Program (TC 10/20s)
Effective 23 October 2026, Visa is adding the Acquirer Reference Number to existing Visa-generated fee collection and funds disbursement transactions to support the Commercial Enhanced Data Program (CEDP) for acquirers and issuers. No changes to the Marqeta platform were necessary to support this mandate.Mastercard network certification
Marqeta is certified with the October 2026 Mastercard Release 26.Q4, effective 23 October 2026.Marqeta changes to support this release of Mastercard
GLB 13264.1 - Identifying issuer-initiated person-to-person payment and funding transactions
Effective 23 October 2026, Mastercard is introducing two new transaction type values,C09 and F09, to identify issuer-initiated person-to-person payment and funding transactions.
To support this mandate, the Marqeta platform will classify C09 and F09 transactions as person-to-person, the same way it already handles the related transaction types Mastercard introduced previously.
Once this update is live, issuer-initiated person-to-person payment transactions will be correctly identified as person-to-person in your spend-control settings and in the transaction data Marqeta provides you.
Until then, these transactions will continue to process normally, but they won’t carry the person-to-person tag, which could affect your reporting or program configuration if you rely on that classification.
For more information, see Transactions.
US 13301.1 - Updating the delivery of Single Message System Transmission Files
Effective 25 October 2026, Mastercard is aligning the Sunday delivery schedule for the Single Message System Transmission File (T461) and the 250-byte Batch Data File with the standard Monday through Saturday schedule. To support this mandate, Marqeta will move the first Sunday delivery of the T461 file earlier, from 10:00 CT (16:00 UTC) to 05:00 CT (11:00 UTC), about five hours earlier than the current schedule. Delivery on other days of the week doesn’t change.GLB 13368.2 - Introducing Token Assurance Method values for tenured tokens and two-factor authentication
Effective 23 October 2026, Mastercard is adding two new Token Assurance Method (TAM) values to inbound authorization and clearing messages:12 (two-factor authentication) and 25 (Tenured Token, for tokens used in Mastercard Digital Enablement Service (MDES) remote commerce with a sustained transaction history).
To support this mandate, Marqeta will decode and persist these new values alongside the existing 10 (Account Verification) and 11 (one-factor authentication) values, with no regression to how existing TAM values are processed.
GLB 13877.1 - Introducing MDES Token Spend Controls
Effective 23 October 2026, Mastercard is introducing Token Spend Controls on individual MDES tokens. Token Spend Controls enables token requestors to set granular spend restrictions, such as spend limits, single-use tokens, and merchant category code (MCC) or geographic restrictions. When a tokenized transaction violates one of these controls, Mastercard declines it before the transaction reaches Marqeta and sends an advice message explaining why. To support this mandate, Marqeta will recognize these Token Spend Control declines and populate theadvice_reason_code and advice_reason_details fields in the transaction API and webhooks with the specific decline reason, such as 0069 (MCC limit) or 0072 (geographic restriction).
Mastercard changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.GLB 13177.1 - Enhancing reconciliation of clearing outputs
Effective 23 October 2026, Mastercard is enhancing reconciliation processing for the Dual Message Clearing System, adding a transaction-level reconciliation identifier to financial, reconciliation summary, and financial position detail messages for inbound and early reconciliation files. No changes to how you interact with the Marqeta platform or handle transactions are required to support this mandate.Discover network certification
No applicable changes were communicated to Marqeta by Discover.Pulse network certification
No applicable changes were communicated to Marqeta by Pulse.July 2026
Visa network certification
No applicable changes were communicated to Marqeta by Visa.Mastercard network certification
The Marqeta platform is certified with the July 2026 Mastercard Release 26.Q3, effective 24 July 2026.Marqeta changes to support this release of Mastercard
GLB 12451.1 - Revised standards for enhancing indicators for purchases of cryptocurrencies
Effective 24 July 2026, Mastercard is introducing enhanced cryptocurrency transaction classification standards to improve transparency and risk management across the network. This change adds granularity to how cryptocurrency purchases are identified, distinguishing more volatile cryptocurrencies (such as BTC and ETH) from fiat-backed stablecoins (such as USDC and USDG) and central bank digital currencies (CBDCs). No new fields are required to support this mandate. The classification is surfaced through a new allowable value,STABLECOIN_CBDC_PURCHASE, on the existing pos.special_condition_indicator field in GET /transactions responses and transaction webhooks.
Starting 24 July 2026, transactions that are stablecoin or CBDC purchases will arrive with the
STABLECOIN_CBDC_PURCHASE value, rather than the generic CRYPTOCURRENCY_PURCHASE value. If your program decisions or reports on pos.special_condition_indicator, review any logic that treats CRYPTOCURRENCY_PURCHASE as a catch-all for all crypto purchases to ensure that your risk and approval rules account for the more specific value.
For the full list of allowable values for the pos.special_condition_indicator field, see the Transaction object.
Mastercard changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.GLB 12912.1 - Introducing Interregional Interchange Rates
Mastercard is introducing interregional consumer credit interchange rates globally. No changes to the Marqeta platform were necessary to support this mandate.AP 12920.1 - Introducing Intraregional Interchange Rates in the Asia/Pacific Region
Mastercard is introducing intraregional consumer credit interchange rates in the Asia/Pacific region. No changes to the Marqeta platform were necessary to support this mandate.Discover network certification
No applicable changes were communicated to Marqeta by Discover.Pulse network certification
No applicable changes were communicated to Marqeta by Pulse.April 2026
Visa network certification
Marqeta is certified with the April 2026 VisaNet Business Enhancements, effective 17 April 2026.Marqeta changes to support this release of Visa
Article 1.1 - Mandate to support the Digital Commerce Authentication Program for domestic and cross-border transactions
Effective 17 April 2026, Visa is mandating that all global issuers must receive and process Digital Commerce Authentication Program (DCAP) data fields for e-commerce transactions. To support this mandate, when Marqeta receives DCAP authentication data from Visa, Marqeta will now parse associated customer-related data containing consumer contact and billing address information for e-commerce transactions that have undergone enhanced authentication. Marqeta will then populate this customer-related data in the newdcap_authentication_data object in GET /transactions payloads.
NoteMarqeta will only receive and populate this data for DCAP-authenticated transactions.
digital_commerce_authentication_indicator field to support this mandate, which appears in JIT payloads, webhooks, and GET /transactions API calls.
Below is an updated list of this field’s allowable values:
Additionally, the Marqeta platform now parses the consumer contact and billing address data that Visa sends in Field 56 for DCAP-authenticated e-commerce transactions, and surfaces it in a new
digital_commerce_authentication_program object. This object is included in Gateway JIT Funding requests, transaction webhooks (authorization, authorization.advice, and authorization.clearing), and the GET /transactions/{token} and GET /transactions API responses.
Marqeta populates these fields only for DCAP-authenticated transactions; the object is omitted when no DCAP data is present.
For more information on this new object, see the Transactions API reference.
Article 2.1 - Changes to Merchant Category Codes
Effective 17 April 2026, Visa will implement changes to support new Merchant Category Codes (MCCs). To support this mandate, Marqeta will now return MCC values in thecard_acceptor.mcc field in JIT payloads, webhooks, and GET /transactions calls. You do not need to take any action for this change to take effect, as the Marqeta systems will update this field internally.
Article 2.5 - Mandatory changes to Visa Resolve Online
In compliance with Visa network mandates, Marqeta will make changes to questions and response options for the following reason codes. These updates will go into effect on 17 April 2026. Marqeta will require you to provide a text response to the question"Explain why credit was issued late and details of ongoing negotiations between the cardholder and the merchant" in the "explain_credit_issued_late_details_of_negotiations" field. This response is only required if the difference between the transaction processing date and the date provided for either of the following fields is greater than 120 days:
"credit_voucher_transaction_receipt_or_refund_acknowledgement_date""date_cardholder_returned_cancelled_merchandise"
"Merchant refused to provide return authorization" response option (written as MERCHANT_REFUSED_RETURN_AUTHORIZATION in the /cases API) for the "merchant_refuse_advise" field.
Additionally, Marqeta will require Yes or No responses for the following questions:
Article 2.12 - New fraud type classifications in Fraud Reporting System
Effective 17 April 2026, Visa will expand the list of fraud type classification values in Fraud Advice and Activity Reports for account funding transactions (AFTs) and original credit transactions (OCTs). To support this mandate, Marqeta will require customers to send thefraud_type_classification field in POST /cases payloads for fraudulent Visa account funding transactions (AFTs) if the fraud_type is MANIPULATION_OF_ACCOUNT_HOLDER.
The fraud_type_classification field now accepts the following additional values:
CHARITY_SCAMHOLIDAY_AND_TICKET_SCAMUTILITY_SCAMLOAN_SCAMPARENT_GRANDPARENT_RELATIVE_SCAMJOB_SCAM
Article 2.17 - Visa Account Screen Clearing File (ASCF) auto-enablement
Previously, clearing return participation was only enabled if you requested to use the Account Screen Clearing File (ASCF) service for your program. Effective 17 April 2026, Visa will automatically enable the ASCF service for all issuers. Programs can disable the ASCF service or switch to an all-respond Account Screen Authorization File (ASAF) and ASCF clearing return configuration through a standard Client Information Questionnaire (CIQ) update request. Standard CIQ update fees apply for either change. When this change goes live, Marqeta will default all newly-enabled programs to a stand-in processing (STIP)-only ASAF with ASCF clearing return configuration. This configuration handles both authorization and clearing as described below:- Authorization: When the Marqeta platform is in STIP, Visa will check authorizations against the ASAF. If the primary account number (PAN) is listed on the ASAF, Visa will decline authorizations for that PAN on behalf of Marqeta. Unless it is in STIP, the Marqeta platform handles the authorization decision directly without Visa’s intervention.
- Clearing: Visa will check all clearings against the ASCF at all times, regardless of whether Marqeta is in STIP. If the PAN is listed on the ASCF, Visa will block the clearing.
04- Pick up card (no fraud)07- Pick up card, special condition14- Invalid account number41- Lost card, pick up43- Stolen card, pick up46- Closed account
05 (Do Not Honor) or 54 (Expired Card) remain on the ASAF only. They receive STIP-only authorization protection, but they do not receive clearing protection.
ASCF downgrade behavior: Visa might downgrade a PAN’s action code on the ASAF from an ASCF-eligible code to a STIP-only action code (05 or 54) if Marqeta approves a transaction on that PAN after it was listed. When this happens, the PAN loses ASCF clearing protection. To avoid this downgrade, programs must ensure that cards included in the exception file are being declined by Marqeta at the time of authorization.
Enabling an all-respond configuration: Programs that want Visa to check the ASAF for all authorizations, not only during STIP, can submit a standard CIQ update request to switch to an all-respond ASAF with ASCF clearing return configuration. Standard CIQ update fees apply. Under this configuration, Visa will check all authorizations against the ASAF and decline for listed PANs, even when the Marqeta platform is available (not in STIP). Clearing behavior remains the same.
Fees: Visa charges a monthly fee of $0.05 per PAN for ASCF residency. There are no changes to existing fees for programs that already have an ASCF enabled. For programs that do not currently have the ASCF service enabled, Visa will begin charging this fee when ASCF is auto-enabled on 17 April 2026. The allocation of network fees depends upon the structure of each program’s contract.
Article 10.3.1 - Changes to support domestic account funding transaction mandate in Brazil
Visa will require acquirers and issuers in Brazil to support the recipient tax identification for account funding transactions (AFTs) containing money transfer or non-money transfer business application identifiers (BAIs). To support this mandate, Marqeta will reject domestic AFTs from Brazil that do not include recipient tax identification. This change only affects programs that use AFT processing for domestic transactions from Brazil, and also use one of the following Business Application Identifiers (BAIs):BBBPFTWT
Visa changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.Article 2.9 - Introducing the Visa Infinite Plus Credit product in Canada
Visa will introduce a new consumer Visa Infinite Plus Credit product that will be issued by card issuers in Canada. Transactions on Visa Infinite Plus cards will show the new product type in the transaction data. No action from you is required.Article 2.10 - New and expanded Visa Infinite, Visa Infinite Privilege, and Visa Ultra High Net Worth products
Visa is expanding the Visa Infinite, Visa Infinite Privilege, and Visa Ultra High Net Worth (UHNW) product offerings across multiple regions. No changes to the Marqeta platform were necessary to support this mandate.Article 2.14 - Changes to the Digital Commerce Authentication Program to support token passkeys and account funding transactions
Visa will implement changes to enable Digital Commerce Authentication Program (DCAP) for account funding transactions (AFTs) with tokens. Thedigital_commerce_authentication_indicator field includes values 05 (VISA_PAYMENT_PASSKEY_VTS) and 07 (VTS_DATA_ONLY) for passkey-authenticated transactions. No changes to the Marqeta platform were necessary to support this mandate.
Article 2.16 Changes to support PIN processing for account verification transactions
Visa will implement changes to support PIN verification during the processing of account verification messages. No changes to the Marqeta platform were necessary to support this mandate.Article 2.18 - Changes to the Card Verification Value 2 service
Visa will implement changes to the Card Verification Value 2 (CVV2) data presence indicator values and CVV2 result codes to enhance CVV2 processing in card-not-present (CNP) transactions. No changes to the Marqeta platform were necessary to support this mandate.Article 2.19 - New Visa Secured Enhanced Card Credit product in the United States
Visa will introduce a new consumer Visa Secured Enhanced Card Credit product that will be issued by card issuers in the United States region. Transactions on Secured Enhanced cards will show the new product type in transaction data. No changes to the Marqeta platform were necessary to support this mandate.Article 3.2 - Changes to support cross-border account funding transactions and original credit transactions
Visa will implement new processing rules for certain data in cross-border money transfer and non-money transfer account funding transactions (AFTs) and original credit transactions (OCTs) destined to Australia, New Zealand, and Saudi Arabia. Visa will decline transactions on behalf of Marqeta when required fields are not populated from the acquirers for AFTs or OCTs. No changes to the Marqeta platform were necessary to support this mandate.Article 3.7 - Changes to support token assurance method
Visa will implement changes to update the token assurance method (TAM) value for card-on-file and e-commerce enabler token types in certain conditions for Tap to Add Card transactions. Marqeta has made all necessary changes to support this mandate, but these changes will not be visible to you.Article 3.10 - Changes to clearing and settlement advices
Visa will implement changes to allow partial reversals of card-not-present pre-authorization transactions on Interlink in the United States and United States territories. No changes to the Marqeta platform were necessary to support this mandate.Article 5.4 Requirement to support certain fields in V.I.P. and BASE II
Visa will add new tags in V.I.P. and new fields in BASE II. No changes to the Marqeta platform were necessary to support this mandate.Article 9.2.1 - Enhancement to the Visa Direct Strategic Alliance Fee program to include recycling payouts
Visa is enhancing the Visa Direct Strategic Alliance Fee Program to include fees for recycling payout original credit transactions (OCTs). No changes to the Marqeta platform were necessary to support this mandate.Article 9.2.2 - New Europe regional interchange fees for Visa and V Pay transactions in Switzerland
Visa will introduce two new Europe regional interchange fee programs for Visa Consumer and V Pay transactions originating from merchants in Switzerland on credentials issued from the European Economic Area (EEA). No changes to the Marqeta platform were necessary to support this mandate.Article 10.1.2 - Changes to Colombia domestic processing
Visa will implement changes to support domestic data requirements for Colombia domestic transactions. Changes will be made to an existing field and clearing record, and new processing rules will be added. No changes to the Marqeta platform were necessary to support this mandate.Article 11.2.1 Updates to Credit Voucher—MOTO and E-Commerce fee program for certain digital currency transaction types
Visa will update the Credit Voucher—MOTO and E-Commerce fee program for transactions made with certain types of digital currencies. No changes to the Marqeta platform were necessary to support this mandate.Article 11.2.3 - Changes to Visa Business, Corporate, and Purchasing Fee programs
Visa will eliminate certain fee programs applicable to Visa Business, Visa Corporate, and Visa Purchasing credit transactions. No changes to the Marqeta platform were necessary to support this mandate.Article 11.2.4 - Mandate to support United States domestic original credit transactions on the Plus network for non-Visa branded proprietary card products
To support increased reach of Visa Direct for United States issuers, Visa will require issuers to receive domestic original credit transactions (OCTs) and Fast Funds on the Plus network (0004) for non-Visa branded proprietary card products.
No changes to the Marqeta platform were necessary to support this mandate.
Article 11.2.6 - Changes to interchange fee programs for Visa consumer credit card-not-present transactions
Visa will introduce new fee programs and also modify existing fee programs for consumer credit card-not-present transactions. These changes will impact fee edit criteria, fee descriptors, fee program indicators (FPIs), and rates that apply to Visa Consumer Credit card-not-present transactions. No changes to the Marqeta platform were necessary to support this mandate.Article 11.3.1 - Changes to support money transfer original credit transactions
Visa will implement changes so that sender address data no longer needs to be included for domestic money transfer original credit transactions (OCTs) less than $3,000. No changes to the Marqeta platform were necessary to support this mandate.Mastercard network certification
The Marqeta platform is certified with the April 2026 Mastercard Release 26.Q2, effective 17 April 2026.Marqeta changes to support this release of Mastercard
GLB 12192.1 - Enhancing indicators for purchases of cryptocurrencies
Effective 17 April 2026, Mastercard is enhancing indicators to distinguish between different types of cryptocurrency used for purchases. To support this mandate, Marqeta will expand cryptocurrency transaction support to include Mastercard’s new Transaction Type Identifier (TTI) valueP76 for fiat-backed stablecoins and central bank digital currencies, in addition to the existing P70 support for floating cryptocurrencies.
Note
P76 transactions will be mapped to the existing CRYPTOCURRENCY_PURCHASE special condition indicator to ensure that your existing cryptocurrency authorization rules continue to work without modification.Mastercard changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.AP 11873.1 - Modifying intracountry interchange programs and structures in Australia
Mastercard is modifying intracountry point-of-sale (POS) credit, debit, and prepaid interchange programs and structures in Australia. No changes to the Marqeta platform were necessary to support this mandate.AP/LAC 12505.1 - Enhancing intracurrency settlement process in the Asia/Pacific, Latin America, and Caribbean regions
Mastercard is enhancing the settlement process for single-message intracurrency activity in the Asia/Pacific, Latin America, and the Caribbean regions. No changes to the Marqeta platform were necessary to support this mandate.GLB 12129.1 - Revised standards for acceptor business codes
Mastercard is revising standards regarding acceptor business codes (also known as merchant category codes, or MCCs). These revisions include the addition of new hotel and airline MCCs, and also clarifications of descriptions for existing MCCs. No changes to the Marqeta platform were necessary to support this mandate.GLB 12203.1 - Supporting United States dollars as primary currency in Somalia
Mastercard is updating its systems to recognize USD as the primary transaction currency in Somalia, aligning with the country’s existing currency usage patterns. This change applies to Mastercard’s internal currency conversion and settlement processing only.GLB 12242.1 - Introducing enhanced acceptor and digital receipts data
Mastercard is introducing data fields to provide enhanced acceptor details and SKU-level digital receipts for dual-message clearing system messages in markets where Mastercard switches transactions. No changes to the Marqeta platform were necessary to support this mandate.GLB 12251.1 - Introducing Crypto Card Indicators
Mastercard is introducing a Crypto Card Indicator to identify cryptocurrency card transactions and account ranges. No changes to the Marqeta platform were necessary to support this mandate.GLB 12254.1 - Enhancing identification of partner service providers
Mastercard is enhancing the identification of partner service providers in the transaction process. No changes to the Marqeta platform were necessary to support this mandate.GLB 12489.1 - Supporting interchange compliance in New Zealand
Mastercard is supporting interchange compliance in New Zealand. No changes to the Marqeta platform were necessary to support this mandate.Discover network certification
The Marqeta platform is certified with the April 2026 Discover Release, effective 17 April 2026.Discover changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.Section XVI - Updated TVi-2 Cryptogram and Multi-Cryptogram
Discover has made changes to Field 122 to support the use case of TVi-2 and 3DS cryptograms within the same transaction. No changes to the Marqeta platform were necessary to support this mandate.Pulse network certification
The Marqeta platform is certified with the April 2026 Pulse Release, effective 12 April 2026.Pulse changes with no impact on your card program
Marqeta has completed the development work required for these mandates, although the modifications are not visible to you. There are no changes to how you interact with the Marqeta platform or how you handle transactions.Section 2 - AFT and ACT Scope Expansion
Pulse will be implementing changes to account funding transfer (AFT) and account credit transfer (ACT) transactions. No changes to the Marqeta platform were necessary to support this mandate.Section 3 - Transaction identifier for Pulse returns
Pulse will start assigning a transaction identifier to all Pulse return transactions. No changes to the Marqeta platform were necessary to support this mandate.January 2026
Visa network certification
No applicable changes were communicated to Marqeta by Visa.Mastercard network certification
The Marqeta platform is certified with the January 2026 Mastercard Release 26.Q1, effective 26 January 2026.GLB 11730.1 - Enhancing Mastercard transaction insights: authorization match
Mastercard is revising and expanding the advice detail code values and descriptions used with On-behalf Service (OBS 33) for Mastercard Send and other transaction-blocking service flows. Mastercard is updating values for the following fields:- DE 48 (Additional Data: Private Use), subelement 71 (On-behalf Services)
- DE 60 (Advice Reason Code), subfield 2 (Advice Detail Code)