https://www.marqeta.com/docs/developer-guides/release-notes/rss.xml
Marqeta rolls out Card Issuing and Processing platform releases in phases.
If you don’t see a feature in your environment yet, you will after Marqeta updates your environment to the new version.
Platform release numbers, such as V.2026.8.31.0, identify the release, not the date it becomes available.
Changes to network report field names
Action requiredBreaking changeMarqeta is standardizing network report field names to follow lowercasesnake_case format consistently. Effective 27 April 2026, Marqeta will update the field names of the following network reports:Additionally, unused or deprecated columns will be reserved for future use. For example, the
HASHED_PAN column in the T112 report will be renamed to reserved_1.NoteThis update will initially apply only to new Marqeta customers. Existing Marqeta customers will continue to receive reports with their current field name format until otherwise notified.
PIN validation fraud check feature flag implementation
Platform release: V.2026.3.30.0Sandbox release date: April 23, 2026Production release date: April 27, 2026Marqeta has created a new fraud-check feature flag. You can use the fraud-check feature when making a PIN change request via a widget to support offline PIN updates. This check was designed to prevent fraudulent transactions when offline PIN verification fails at the terminal and no PIN is present in field52 of the incoming authorization message.When the feature flag is set to TRUE, the system performs an authorization fraud check to verify that the online PIN is present and matches the most recent PIN update made by the cardholder. This validation helps prevent unauthorized card usage by confirming that the PIN entered during the transaction is consistent with the PIN update, ensuring that the legitimate cardholder who possesses the card is conducting both the PIN update and the transaction.If you would like to enable this feature flag for your card program, contact your Marqeta representative.Copying a PIN to a reissued card
Platform release: V.2026.3.30.0Sandbox release date: April 23, 2026Production release date: April 27, 2026Marqeta now enables you to copy a PIN from a source card to a reissued card by setting the newcopy_pin_from_source_card field to true in the POST/cards endpoint. If the previous card has no PIN assigned, the reissued card is created without a PIN, and the pin_is_set field is set to false.This field can only be used with reissue_pan_from_card_token or new_pan_from_card_token, not with translate_pin_from_card_token.Marqeta also introduces a new error code, 400984, to indicate that copy_pin_from_source_card can only be used with reissue_pan_from_card_token or new_pan_from_card_token.For more information, see Create card and Errors.New transaction types and fields
Platform release: V.2026.3.30.0Sandbox release date: April 23, 2026Production release date: April 27, 2026Marqeta has added two feature-flag-enabled transaction types:fee.collection.debitfee.collection.credit
sub_type- Transaction subtypenetwork_metadata.message_reason_code- Message reason code, as provided by the card network
cardholder_impact payload field for all transactions, which indicates whether the transaction impacts the cardholder ledger.New fields in network reports
Platform release: V.2026.3.30.0Sandbox release date: April 23, 2026Production release date: April 27, 2026Marqeta adds the following new fields to the T112 network reports sent to customers:reconciliation_date- Represents the clearing system’s processing date based on the clearing center’s local time zone. The date is represented inYYMMDDformat.settlement_date- Represents the date when the settlement service initiates financial settlement for the transaction. The date is represented inYYMMDDformat.
New flag for card re-issuance
Platform release: V.2026.3.2.0Sandbox release date: April 2, 2026Production release date: April 8, 2026Marqeta now enables you to reissue a card with a new primary account number (PAN) and choose whether to retain or terminate the original source card after the new card is activated.Historically, Marqeta only supported issuing a new PAN in lost or stolen scenarios using thenew_pan_from_card_token field. In that flow, the source card is immediately terminated once the replacement card is issued. This process remains unchanged and continues to be the recommended approach for lost or stolen cases.Marqeta now enables you to generate a new PAN as part of the standard re-issuance flow using reissue_pan_from_card_token by setting generate_new_pan to true. In this setup, the original card does not have to be terminated immediately and can remain active based on your activation.actions configuration. This supports scenarios such as migrating a card from one bank identification number (BIN) to another while keeping the original card active during the transition period.For more information on creating and reissuing cards, see the Cards API reference.