March 2026
2026.3.30
New message reason in Digital Wallet
Marqeta will add a new message reason, Out of date credential - expired PAN, for digital wallet token transitions. Marqeta terminates tokens that are associated with expired PANs as part of Visa’s best practices. Card programs will receive this updated message reason in such use cases.
2026.3.20
New transaction types and fields
In April 2026, Marqeta will add two feature-flag-enabled transaction types:
-
fee.collection.debit
-
fee.collection.credit
These new transaction types include the following optional payload fields:
-
sub_type - Transaction subtype
-
network_metadata.message_reason_code - Message reason code, as provided by the card network
To enable the transaction types and fields listed above for your program, contact your Marqeta representative.
Additionally, Marqeta will add a new payload field for all transactions:
cardholder_impact - Indicates whether this transaction impacts the cardholder ledger
February 2026
2026.2.20
Updates to Disputes reason codes
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 April 18, 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"
Marqeta will remove the "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:
| Question | Field name | When is a response required? |
|---|
"Did cardholder cancel before ship date?" | "did_cardholder_cancel_before_shipping" | Required if the value for "did_cardholder_cancel" is true. |
"Did the merchant accept cancellation?" | "did_the_merchant_accept_cancellation" | Merchandise - Required if the value for "did_cardholder_cancel_before_shipping" is Yes and the cancellation_date is no more than 15 days prior to submitting the dispute.
Services - Required if the value for "did_cardholder_cancel" is Yes and the cancellation_date is no more than 15 days prior to submitting the dispute. |
Domestic Account Funding Transactions in Brazil
Effective April 17, 2026, Marqeta will reject domestic Account Funding Transactions (AFTs) from Brazil that do not include recipient tax identification, in compliance with Visa network mandates.
This change only affects programs that use AFT processing for domestic transactions from Brazil and use one of the following Business Application Identifiers (BAIs):
Expanded cryptocurrency transaction support
Effective April 17, 2026, Marqeta will expand cryptocurrency transaction support to include Mastercard’s new Transaction Type Identifier (TTI) value P76 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, ensuring that your existing crypto authorization rules continue to work without modification.
January 2026
2026.1.16
New optional field in the Transactions API
Marqeta will soon add a new optional field called outgoing_response_code to the network_metadata object in the Transactions API. This field allows card networks to expose the network response code in transaction payloads.
November 2025
2025.11.20
New field to connect recurring Visa transactions
Marqeta will soon add a field called original_network_transaction_lifecycle_id to the Transaction object for Visa transactions. This field will connect an original transaction to all subsequent activities throughout the transaction lifecycle. For example, recurring transactions for a subscription service will all connect to the same original_network_transaction_lifecycle_id.
October 2025
2025.10.3
Coming soon - New object for Strong Customer Authentication (SCA) framework
Marqeta will add the strong_customer_authentication object to classify both issuer and acquirer exemptions for contactless transactions. This object will categorize different types of exemptions within the SCA framework. Marqeta will also provide a field for enabling the strong_customer_authentication object. Set the ENABLE_STRONG_CUSTOMER_AUTHENTICATION field to true to enable the object for your card product.
This field will only be applicable to contactless transactions. For card not present e-commerce transactions, use the existing issuer/acquirer exemption field within the cardholder_authentication_data object.
Coming soon - New transaction response codes for JIT timeouts
Marqeta will soon launch two new transaction response codes for JIT timeouts or errors, not including 200 or 402 responses.
Currently, Marqeta uses a single response code (1016) when either a JIT gateway timeout or error occurs, or when there is a transaction decline without a given reason.
For example, when a JIT gateway timeout or error occurs for an authorization, Marqeta sends the following response code and memo:
| Field | Code | Memo |
|---|
response | 1016 | "Not sufficient funds" |
decline_reason field, Marqeta sends the following response code and memo:
| Field | Code | Memo |
|---|
response | 1016 | "Not sufficient funds" |
| Field | Code | Memo |
|---|
response | 1033 | "JIT Response Timeout or Error" |
decline_reason field:
| Field | Code | Memo |
|---|
response | 1034 | "JIT Response No Decline Reason" |
