Skip to main content
​
December 2024

Marqeta platform holiday code freeze

The end-of-year holiday season represents a peak traffic period for many of Marqeta’s card programs and customers. In addition, we are expecting increased transaction volume during this time, based on initial feedback we received.In order to ensure an optimal cardholder experience during the 2024 holiday season, we are instituting a code freeze for the Marqeta platform over the holiday period. Biweekly platform updates will not be deployed from 15 November 2024 until the second week of January 2025.For more information, contact your Marqeta representative.

New Click to Pay feature

Marqeta now supports Click to Pay: an online checkout option that allows consumers to pay without repeatedly entering their card details manually. Currently available for Mastercard-issued cards only, the Click to Pay feature improves security and the customer experience.For more information about Click to Pay, see the Digital Wallets Management API reference.

New Cash Loads Direct feature

With the new Cash Loads Direct feature, your cardholders can deposit funds at selected physical locations, such as a point of sale, that do not belong to their own physical branch network. Once deposited, these funds are then loaded into the account associated with the cardholder’s debit or prepaid card.Typically offered for consumer Demand Deposit Account (DDA) or General Purpose Reloadable (GPR) programs at digital financial institutions, Cash Loads Direct is a creative way to offer cardholders increased flexibility when funding their cards.For more information, contact your Marqeta representative.
​
November 2024

3D Secure webhook enhancement

Marqeta now sends the threedstransition.completion webhook for 3D Secure requests that fail due to an invalid primary account number (PAN).For more information about 3D Secure webhooks, see 3D Secure transition events.

Greater flexibility when configuring ACHR transaction limits

Transaction limits for Automated Clearing House (ACH) credit and debit transactions are transitioning from the general /velocityrules configuration to the ACH Receiving (ACHR) service. Programs can choose to have the same or different limits across credit and debit transactions. The limits you define will be evaluated during NACHA file processing, and any transactions that are beyond the limit will be rejected.
  • Credit: Any credit transactions that are beyond the defined limit will be rejected with reason code R23 (“Credit entry refused by receiver”).
  • Debit: Any debit transactions that are beyond the defined limit will be rejected with reason code R10 (“User advises of an unauthorized, improper, ineligible, or incomplete transaction” or “User advises that the originator is unknown to the receiver and/or the originator is not authorized to debit the receiver’s account”).
For more information or to start using the new transaction limits configuration, contact your Marqeta representative.

New direct deposit transition fields

ACH Receiving now includes the following new fields in direct deposit transition webhooks, as well as when interacting with the /directdeposits/transitions endpoint. These new fields are available for all states: PENDING, REJECTED, REVERSED, APPLIED.
  • current_txn_index
  • total_txns_count
  • nacha_file_creation_time
  • nacha_file_id_modifier
  • bank
For examples on how these new fields are used, see the Direct deposit transition section of the Event Types page.

Merchant to Authentication App Redirection for 3D Secure transactions

Marqeta now supports Merchant to Authentication App Redirection for Mastercard 3D Secure transactions in merchant applications on mobile devices. This feature allows cardholders to authorize their 3D Secure merchant application transactions on the Mastercard network without manually switching between their merchant and authentication applications.To enable the Merchant to Authentication App Redirection feature, Marqeta must configure the mobile application URL to be used for authentication using a universal app link that you provide. Merchants use the mobile app URL to redirect cardholders from their merchant application to the cardholder’s authentication application.Programs should submit a request to Marqeta Product Support to enable this feature and provide the required universal app link.

Stop ACH Payment feature

Marqeta is introducing the Stop Payment feature for ACH Receiving, which fulfills Marqeta’s obligations as the ACH processor per NACHA guidelines.With this feature, ACH debits made by a particular company against a consumer Demand Deposit Account (DDA) or General Purpose Reloadable (GPR) account can be halted when expressly requested by the cardholder. Card programs using ACH Receiving can integrate with the Stop Payment API in order to use this feature.To get started with using the Stop Payment feature, contact your Marqeta representative.

Marqeta’s sub-processor list has been updated as of 19 November 2024

Marqeta engages sub-processors to assist with the provisioning of the card program management and processing services offered to our customers.Our list of sub-processors is available at www.marqeta.com/sub-processors.
​
October 2024

UX Toolkit GA launch

We are excited to share the General Availability (GA) launch of our UX Toolkit.Marqeta’s UX Toolkit is a low-code solution enabling you to integrate essential cardholder functionality into your customer application. The following web components are available as part of this launch:
  • Account details: Provide your cardholders with their account details, including account number, routing number, and available balance.
  • Card activation: Give your cardholders a frictionless way to activate their new cards.
  • PIN management: Enable your cardholders to securely set, manage, and reveal their PIN when needed.
  • View and copy card details: Allow your cardholders to view and copy their card details to the clipboard.
  • Lock/unlock card: Allow your cardholders to lock or unlock their card for fraud prevention.
  • Card actions: Enable your cardholders to conveniently select common card management options.
  • Replace card: Allow your cardholders to quickly replace a lost, stolen, or damaged card.
  • Transaction activity: Display detailed transaction histories, including pending and cleared transactions, merchant name, date, and transaction type.
  • Onboarding: Create a user account on the Marqeta platform, then perform KYC identity verification on potential cardholders.
  • Statements: Give your cardholders a view of their monthly transactions with the option to download a statement as a PDF.
  • Disputes: Equip your cardholders so they can file the main types of disputes on their own.
  • Money movement and funding sources: Provide your cardholders with options to link external payment cards and transfer money into their account.
If you are interested in adding this functionality to your card program, contact your Marqeta representative for more information. To learn more about UX Toolkit and interact with its UI components, see the UX Toolkit Overview page on MQ Docs.

DiVA API update

DiVA API was updated on 24 October 2024. This update improved the system’s reaction to when calls made to DiVA API time out.In the previous DiVA configuration, API calls timed out after 60 seconds, and a 504 (Gateway Timeout) error code was returned. As a result of this update, instead of a 504 error code, DiVA now returns a 409 (Conflict) error code in the event of a timeout.Marqeta made this change to align DiVA API with web standards regarding API responses. The 409 error code indicates to the caller that the timeout is the result of their API call to DiVA API, and therefore allows them to reconfigure their scripts and retry the call.Marqeta does not anticipate that the update will negatively impact API calls made to DiVA. For more information, contact your Marqeta representative.

Platform release 2024.10.28.0

Changed functionality

Fixed: Incorrect velocity control balances in advice messages
An issue that caused incorrect velocity control balances in incremental authorization advice messages has been addressed in this release.

Platform release 2024.10.14.0

Changed functionality

Response code added for Anticipated Amount Verification Transaction declines
Anticipated Amount Verification Transaction (AAVT) is a new transaction type introduced by Visa that allows merchants to verify if a cardholder has sufficient funds for a transaction without placing an authorization hold. AAVT uses a specific message format to communicate the anticipated amount, which enables real-time balance checks.Transaction response code 1939 “Amount not supported” was added to the Marqeta platform to address AAVT Z5 declines. Applies to the Visa card network only.
​
September 2024

Marqeta Dashboard partial outages

From 4:00 PM to 5:30 PM PDT (UTC -7) on 2024-09-12 and 2024-09-19, Marqeta will be performing scheduled maintenance on Marqeta Dashboard. The public sandbox will remain available while maintenance is being performed, but user management functions in Marqeta Dashboard will be intermittently unavailable. During this time, your end users might not be able to access the user management features of Marqeta Dashboard.Marqeta Production Support will contact impacted card programs by email when maintenance activity begins, and again when full functionality has been restored.

Card network certification release notes now available

Card Network Certifications are a collection of standards and protocols set by the card networks such as Mastercard, Visa, Pulse, and Discover. These certifications ensure that all transactions processed through these card networks meet their specific requirements, as related to topics including security, data handling, and interoperability. Changes to these certifications are typically communicated through technical documents provided by the card networks four times a year (two major and two minor updates).The October 2024 card network certification release notes are now available on Marqeta Docs. For a summary of the upcoming changes for each supported card network, as well as any modifications you might need to make to your card program, see Card Network Certifications 2024.

Notable documentation changes

Updated description for the card_art_id field

The description of the digital_wallet_token.card_art_id field has been expanded to include more information about the kinds of metadata included in the referenced card art identifier.For more information about the digital_wallet_token.card_art_id field, see Card Products.

Platform release 2024.9.30.0

Changed functionality

Additional values for the transaction initiation field
To further improve transaction approval rates by correctly identifying the initiator of a transaction, the transaction_initiated_by field now includes three additional allowable values: NETWORK, MARQETA, and WALLET.The full list of allowed transaction initiators is: CONSUMER, MERCHANT, NETWORK, MARQETA, WALLET, UNKNOWN.For more information about these fields, see Transactions.
New account funding transaction type indicator
To support Mastercard article GLB 8418.1, Marqeta now includes a new Mastercard MoneySend transaction type indicator: FAST_REFUND.For more information, see Transactions.
Account funding transactions now include sender data
To support cross-border account funding requirements in Visa article 3.4, account funding transactions now include sender data.For detailed information about account funding transactions, see Transactions.
Fixed: Transaction payloads did not include transaction type and original credit transaction type fields
An issue that caused the NETWORK_FUNDING_TXN_TYPE and OCT_TYPE fields to be excluded from some Mastercard network transactions has been addressed in this release.For more information about these fields, see Transactions.
Fixed: Mastercard transactions did not include MOTO payment channel
The payment_channel field for Mastercard transactions now includes the MOTO enumerated value for mail order and telephone order transactions.

Platform release 2024.9.16.0

Changed functionality

Reverted change: Standardized settlement date for Mastercard transactions
In platform release 2024.9.2.0, Marqeta updated the settlement_date field for transactions on the Mastercard network to ensure consistent data across all card networks.In this release, Marqeta reverted that change. The settlement_date field for transactions on the Mastercard network is defined as in previous versions of the Marqeta platform.
New terminal state for account holders
Marqeta introduces a new terminal state for business and user account holders: TERMINATED.If you have the Admin or Program Manager role, you can transition business and user accounts to the TERMINATED state. The TERMINATED state indicates the permanent and irreversible closure of a business or user account. Unlike the CLOSED state (where you can transition a user to other statuses, depending on your role and the details of the previous status change), you cannot transition an account from the TERMINATED state to any other state.For more information, see Business Transitions and User Transitions.
New account funding transaction types
Effective 18 October 2024, Visa article 2.14 introduces new interregional and regional fee programs for certain money transfer account funding transactions in the Asia-Pacific (AP), Central Europe, Middle East, and Africa (CEMEA), and Latin America and Caribbean (LAC) regions.To support this mandate, Marqeta adds the following new account funding transaction types: AFT_OR_OCT_ELIGIBILITY, CONSUMER_BILL_PAYMENT, REQUEST_TO_PAY. For more information about account funding transaction types, see Transactions.
Changes to support new data requirements in Visa Direct transactions
Effective 18 October 2024, Visa article 3.2 implements changes to support new enhancements in account funding transactions and original credit transactions.To support this mandate, Marqeta now includes the account_owner and payment_facilitator objects in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests. In addition to these new objects, Marqeta includes the following new fields in the acquirer object in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests:
  • city
  • country_code
  • merchant_street_address
  • name
  • postal_code
  • state
  • street_address
For more information on these new objects and fields, see Transactions.
Requirement to support Visa Secure Smart Attempts service for Visa Secure issuers
Effective 18 October 2024, Visa article 3.11 implements changes to add support for the new Visa Secure Smart Attempts service processing. In the event of one of the following conditions, Visa will send a new value in the authorization message if the transaction is low risk and below low payment amount thresholds, as defined by Visa on behalf of the issuer:
  • The issuer’s access control server (ACS) is unavailable
  • The issuer’s account is not enrolled in Visa Secure
  • An ACS is not defined for a given account range
To support this mandate, Marqeta now includes the 3D Secure indicator value FRICTIONLESS_SMART_ATTEMPTS in the cardholder_authentication_method object in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.For more information about the 3D Secure indicator value, see Transactions.
New Business Application Identifier for account funding transactions and original credit transactions
Effective 18 October 2024, Visa article 3.21 implements changes to support a new Business Application Identifier value for account funding transactions and original credit transactions.To support this mandate, Marqeta adds the following new account funding transaction type: LIQUID_ASSET. For more information about account funding transaction types, see Transactions.
New geographic coordinates data fields
Effective 18 October 2024, Mastercard article GLB 8431.1 introduces geographic coordinates for the acceptor and service location as a way to enhance the value and transparency of transaction data.To support this mandate, Marqeta now includes two new fields in the card_acceptor object: geographic_coordinates and service_geographic_coordinates. You will see these fields in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.For more information about these fields, see Transactions.
New memo field in transaction metadata
Marqeta now includes a memo field in the transaction_metadata object in the clearing transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests. This field indicates a credit or debit adjustment in a clearing transaction.For more information about this field, see Transactions.

Platform release 2024.9.2.0

Changed functionality

Standardized settlement date for Mastercard transactions
Marqeta has updated the settlement_date field for transactions on the Mastercard network to ensure consistent data across all card networks. In previous releases, the settlement date has been defined in various ways, such as the date when funds are drawn down by a card network, or the date and time when funds were moved for a transaction.This update standardizes the settlement date to consistently reflect the calendar date on which a transaction was processed and cleared by the card network systems. This change enhances data uniformity, ensuring that the settlement date accurately represents the movement of funds across all card networks, including Mastercard.
Acquirer reference number for Pulse transactions
Marqeta now includes the acquirer reference number for transactions on the Pulse card network in the acquirer_reference_data field in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.For more information about this field, see the Transactions API reference.
Support for Zimbabwe Gold currency codes
Effective 18 October 2024, Marqeta supports the new Zimbabwe Gold alpha currency code ZWG and numeric currency code 924.You will see these new currency codes in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.
​
August 2024

Platform release 2024.8.19.0

Changed functionality

Fixed: Recurring and installment transactions on non-reloadable cards
An issue that allowed non-reloadable cards to be used for recurring and installment transactions has been resolved in this release. This fix applies to the Visa card network only.To address this issue, Marqeta now includes the reloadability field in the card_life_cycle object. For more information about this field, see Card Products.

Platform release 2024.8.5.0

New features

New network funding transaction type field
The Marqeta platform’s network_metadata object now includes a field called network_funding_txn_type that indicates the transaction type code, as provided by the card network. You can find the network_funding_txn_type field in the original credit and account funding transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.For more information about this field, see the Transactions API reference.
New transaction initiated category field
The Marqeta platform’s card_acceptor object now includes a field called transaction_initiated_category that specifies the category of transactions initiated at a point of sale. You can find the transaction_initiated_category field in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.For more information about this field, see the Transactions API reference.
​
July 2024

Platform release 2024.7.22.0

New features

Flexible Credential support
Marqeta now supports Visa Flexible Credential.By integrating Visa Flexible Credential in your program, a single card product can seamlessly toggle between debit and credit payment methods on a per-transaction basis, effectively bringing multiple funding sources to a single card. This feature allows your cardholders to use their debit card for Buy Now, Pay Later (BNPL) credit transactions when you approve that transaction from your Just-in-Time Funding Gateway.For more information about how to incorporate Visa Flexible Credential support in your program, contact your Marqeta representative.

Platform release 2024.7.8.0

Changed functionality

Transaction initiation indicator removed from clearing and reversal transaction messages
The transaction initiation indicator field transaction_initiated_by is no longer included in clearing or reversal transaction messages. You will still see this field in authorization and advice transaction messages.For more information about this field, see Transactions.

Notable documentation changes

Credit substatuses

Marqeta has enhanced our credit account management capabilities by providing new substatuses for classifying credit accounts and credit account holders. You can now flag credit accounts and account holders with substatuses designating bankruptcy, Servicemembers Civil Relief Act (SCRA), Military Lending Act (MLA), deceased, fraud, and power of attorney. Substatuses have automatic downstream implications, so be cautious when applying them.You can learn more about credit substatuses on the following pages:
​
June 2024

Platform release 2024.6.24.0

Changed functionality

PAN entry mode update for the Pulse card network
The Marqeta platform now includes the CHIP_FALLBACK primary account number (PAN) capture method for the Pulse card network. If your card product has config.transaction_controls.allow_chip_fallback set to false, Pulse transactions will be declined, as they now qualify as CHIP_FALLBACK.The pos.pan_entry_mode field is optional, and the CHIP_FALLBACK method indicates that the chip card was processed as a magnetic stripe transaction. For more information, see Transactions and Simulations 2.0 — Card Transactions.
Fixed: Pending refunds impacted available velocity control balances
An issue that caused pending refunds to be included in velocity control balances has been fixed in this release. To enable this fix for your program, contact your Marqeta representative.

Platform release 2024.6.10.0

Changed functionality

New field in transaction card acceptor object
To support Visa article AI13324, the card_acceptor object now includes the merchant_vat_registration_id field. You can find this new field in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests for transactions originating in Belgium, France, and Luxembourg.For more information about Visa article AI13324 and the Merchant Value-Added Tax registration identifier, see the April 2024 section of the Card Network Certifications page.For more information about how the Marqeta platform consumes this field, see the Transactions API reference.

Notable documentation changes

Update to card network certification for Mastercard AN 7776

The release note for Mastercard article AN 7776 — New authentication programs for Canada and the United States has been updated to include more information about how it affects your Mastercard programs. For details, see AN 7776 — New authentication programs for Canada and the United States.
​
May 2024

New features

Marqeta Dashboard User Profile Management general availability release

We are excited to announce the general availability release of the User Profile Management feature. With User Profile Management, you can manage access to the Marqeta Dashboard and perform the following tasks:For more information, see User Profile Management.

Platform release 2024.5.27.0

Changed functionality

New Merchant Category Codes
The Marqeta platform now includes two additional Merchant Category Codes (MCCs) for the Mastercard, Pulse, and Discover card networks:
MCCDescription
3840Rio Hotels
5723Gun and Ammunition Stores
Fixed: Mastercard transactions not exempted from limits despite transaction risk analysis exemption
An issue that applied strong customer authentication low-value payment (SCA LVP) limits despite the presence of a transaction risk analysis (TRA) exemption in the transaction authorization has been corrected in this release. This fix applies to transactions on the Mastercard card network only.

Platform release 2024.5.13.0

The 2024.5.13.0 release of the Marqeta platform contains infrastructure improvements and backend issue fixes only. There are no customer-facing enhancements or fixed issues in this release.
​
April 2024

New features

Account Name Inquiry for Simulations 2.0

With the Simulations 2.0 service, you can simulate and test the Account Name Inquiry (ANI) feature before incorporating it in your application. In addition, the requests of the Simulations 2.0 Postman collection have been enhanced to include ANI support. To learn more about ANI, see Simulations 2.0 — Card Transactions and Transactions with Account Name Inquiry.

Platform release 2024.4.29.0

Changed functionality

New cardholder authentication verification result fields for Mastercard transactions
To support Mastercard article AN 7705, Marqeta now includes two new fields in the cardholder_authentication_data.verification_result object:
  • not_verified_mac_key_validation_passed
  • not_verified_mac_key_validation_failed
For detailed information about these new fields, see the Transactions API reference.

Platform release 2024.4.15.0

Changed functionality

Stand-in processing decline messages for balance inquiries on the Pulse network
The Marqeta platform now includes stand-in processing (STIP) decline messages for declined pindebit.balanceinquiry transactions on the Pulse card network. Such declines occur when a cardholder makes a balance inquiry on an ATM card, but the Pulse card network declines the inquiry due to a network timeout or similar issue.Marqeta includes pindebit.balanceinquiry STIP decline messages in webhook transaction payloads.

Platform release 2024.4.1.0

Changed functionality

Account Name Inquiry feature enabled by default
The Account Name Inquiry (ANI) feature is now enabled by default for all programs. ANI is an additional supported feature within Account Verification, as introduced by Mastercard and Visa card network mandates, effective 12 April 2024. With ANI, originating institutions can verify that the name users are providing during their card registration process matches the name associated with the card on file by the card issuer.For more information about the ANI feature, see About Account Name Inquiry and Using ANI with JIT Funding.
Fixed: Incorrect CAVV authentication amount validation for non-ecommerce transactions
An issue that caused non-ecommerce transactions to undergo CAVV authentication amount validation has been fixed in this release.

Notable documentation changes

Account updaters guide

Marqeta supports account updaters for the Mastercard and Visa card networks. Account updaters are services provided by Marqeta through the card networks to automatically update the primary account number (PAN) of a card whenever it is issued, reissued, updated, or closed.For more information about account updaters, see About Account Updaters.

New Cards guides

Two new Cards guides have been published recently:
  • To learn about the Account Name Inquiry (ANI) feature and how it helps approve or decline transactions on the Marqeta platform, see About Account Name Inquiry.
  • To learn about working with the ANI feature in Gateway Just-in-Time Funding requests and responses, see Using ANI with JIT Funding.
​
March 2024

New features

Data Products and Insights – Quarterly Network Reports

Quarterly Network Reports help Marqeta’s customers and their banks fulfill Visa’s and Mastercard’s quarterly reporting mandates. For more information, see Quarterly Network Reports.

Platform release 2024.3.18.0

Changed functionality

New transaction response code
This release of the Marqeta platform includes a new transaction response code: 1937 JIT balance inquiry failure.For more information about transaction response codes, see Transaction response codes.
Webhooks for clearing transactions from the Visa card network now indicate settlement service
For the Visa card network, webhooks from the Marqeta platform related to clearing transactions will now include the settlement_indicator field, which is used to indicate which service was used for settlement.Possible values include INTERNATIONAL_SETTLEMENT_SERVICE, NATIONAL_NET_SETTLEMENT_SERVICE, CLEARING_ONLY, and VISA_SELECTS_SETTLEMENT_SERVICE. In most situations, however, the value of this field will be either INTERNATIONAL_SETTLEMENT_SERVICE or NATIONAL_NET_SETTLEMENT_SERVICE.
Fixed: Automated fuel dispenser pre-authorization approval limit
An issue related to the eligible pre-authorization approval limit caused some automated fuel dispenser transactions to be approved beyond the velocity control limit in place. This issue has been corrected in this release.
Fixed: Exceptions errors logged correctly
Certain exceptions-related errors such as “Transaction amount limit reached” and “Insufficient funds in program reserve account” were erroneously logged and returned by the Marqeta platform as ERROR instead of as DECLINED in the gpaorders table. This issue has been corrected in this release.
Fixed: Incorrect transaction response code sent to card network
Visa response code 1908 is mapped to network response code R0, but some Visa transactions that were declined using IRC 1908 were instead reported as 96: System Malfunction. The mapping inconsistency has been resolved in this release.

Platform release 2024.3.4.0

Changed functionality

New transaction purpose value for original credit transactions
The original_credit.transaction_purpose field now includes an enumerated value to support Mastercard article AN 7713: HIGH_RISK_SECURITIES. High-risk security transactions indicate the purchase, sale, or brokering of financial instruments such as derivatives, foreign exchange currency options, and cryptocurrency options.For more information, see the Transactions API reference.
Fixed: Automated fuel dispenser reversals did not show correct amount
An issue that caused automated fuel dispenser reversals to appear in webhook payloads with an amount of $0 has been fixed in this release.
Fixed: Differing amounts in gpa.credit and authorization objects
An issue that caused the gpa.credit amount to differ from the authorization amount in a transaction has been fixed in this release. To address this issue, the acquirer_fee for a transaction is now categorized as a credit rather than a debit where appropriate:
JSON
"acquirer_fee_amount" : 1.00,
  "fees" : [ {
    "type" : "ACQUIRER_FEE",
    "amount" : 1.00,
    "credit_debit" : "C"
    }
  ]
​
February 2024

Platform release 2024.2.19.0

The 2024.2.19.0 release of the Marqeta platform contains infrastructure improvements and backend issue fixes only. There are no customer-facing enhancements or fixed issues in this release.

Platform release 2024.2.5.0

The 2024.2.5.0 release of the Marqeta platform contains infrastructure improvements and backend issue fixes only. There are no customer-facing enhancements or fixed issues in this release.
​
January 2024

Marqeta platform holiday code freeze

The end-of-year holiday code freeze is finally over! We are pleased to resume regular deployments to both the sandbox and production environments, per the schedule in place.

Platform release 2024.1.22.0

The 2024.1.22.0 release of the Marqeta platform contains infrastructure improvements and backend issue fixes only. There are no customer-facing enhancements or fixed issues in this release.

Platform release 2024.1.8.0

New features

Mastercard Trace ID
Mastercard supports the use of Trace ID to reference the first authorization for recurring payment transactions and merchant-initiated transactions in support of Payment Service Directive 2 Regulatory Technical Standards (PSD2 RTS) Article 14 in the European Economic Area. This change enables acquirers and issuers to provide the Trace ID from the initial authorization in recurring payment transactions, partial shipment e-commerce transactions, installment payments, and other merchant-initiated transactions.PSD2 RTS Article 14 requires that issuers ensure a cardholder was fully authenticated via strong customer authentication (SCA) during the first authorization in a series of recurring payments, and in other merchant-initiated transactions, prior to approving subsequent authorization requests in the same series. Compliance with PSD2 RTS Article 14 helps you have greater confidence that the transaction or recurring payment arrangement was strongly authenticated as part of the initial authorization. It also improves your ability to optimize approval rate performance, manage product offerings, and enhance consumers’ digital shopping experiences.You can find the Mastercard Trace ID in the new merchant_initiated_original_trace_id field in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests.For more information about this field, see the Transactions API reference.
Final clearing transaction indicator
The Marqeta platform now indicates the final clearing transaction for an authorization in the is_final_clearing field in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests for transactions on the Mastercard network. If you receive a final clearing transaction with this indicator, be advised that you will not receive an expiration for the related authorization.For more information about this field, see the Transactions API reference.

Changed functionality

Electronic commerce indicator updates for Visa
The Marqeta platform now populates the cardholder_authentication_data object’s electronic_commerce_indicator field for single-message (i.e., pindebit) transactions and clearing transactions on the Visa card network.You can use the data from this field to determine transaction dispute eligibility for force-post clearing transactions that lack a related authorization.For more information about this field, see the Transactions API reference.
Deferred authorization indicator now included in Visa transactions
The Marqeta platform now includes the transaction_metadata.is_deferred_authorization field in the transaction payloads of Gateway JIT Funding requests, webhooks, and GET /transactions requests of transactions on the Visa card network.A deferred authorization is an offline authorization made during an interruption of card network connectivity, such as a purchase on a flight. You can use the deferred authorization indicator to ensure that you do not mistakenly decline such offline authorizations.For more information about this field, see the Transactions API reference.

Notable documentation changes

Updated API reference pages

We have updated several API definitions and reference pages to ensure consistency with the Marqeta platform code:

Related topics

2022 Release Notes2020 Release Notes2021 Release NotesRelease Notes2023 Release Notes