> ## Documentation Index > Fetch the complete documentation index at: https://www.marqeta.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # April 2026 Card Issuing and Processing Release Notes > Release notes for the Card Issuing and Processing platform in April 2026: new features, enhancements, fixed issues, deprecations, and notable documentation changes. To follow new Card Issuing and Processing release notes with RSS, subscribe to the current release notes feed: `https://www.marqeta.com/docs/developer-guides/release-notes/rss.xml` > [!NOTE] > > 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. **Breaking changes** ## Changes to network report field names Action required Breaking change Marqeta is standardizing network report field names to follow lowercase `snake_case` format consistently. Effective 27 April 2026, Marqeta will update the field names of the following network reports: | Network | Report name | | - | - | | Visa | VSS Detail SMS Raw | | Mastercard | T112 T464 | | Pulse | EDF | 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`. > [!NOTE] > > **Note** > > This 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. If your integration relies on header names, you will have to update your header names to match the new standardized format when this change is released to existing Marqeta customers. If your integration relies on column positions, no action will be required. For more details about field mapping for T112 reports, see the T112 file specification. **New features** ## PIN validation fraud check feature flag implementation **Platform release:** V.2026.3.30.0 **Sandbox release date:** April 23, 2026 **Production release date:** April 27, 2026 Marqeta 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 field `52` 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.0 **Sandbox release date:** April 23, 2026 **Production release date:** April 27, 2026 Marqeta now enables you to copy a PIN from a source card to a reissued card by setting the new `copy_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](https://www.marqeta.com/docs/core-api/cards/#post_cards) and [Errors](https://www.marqeta.com/docs/core-api/errors.md#400900-400999-error-codes). ## New transaction types and fields **Platform release:** V.2026.3.30.0 **Sandbox release date:** April 23, 2026 **Production release date:** April 27, 2026 Marqeta has added 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 provides a new `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.0 **Sandbox release date:** April 23, 2026 **Production release date:** April 27, 2026 Marqeta 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 in `YYMMDD` format. * `settlement_date` - Represents the date when the settlement service initiates financial settlement for the transaction. The date is represented in `YYMMDD` format. The reconciliation date and settlement date may sometimes differ. For example, for a transaction processed during a weekend, the reconciliation date will fall on the weekend date, but if the settlement bank is closed during the weekend, the settlement date will fall on the following business day. These fields can help you to better understand the clearing and settlement timelines for Mastercard transactions. ## New flag for card re-issuance **Platform release:** V.2026.3.2.0 **Sandbox release date:** April 2, 2026 **Production release date:** April 8, 2026 Marqeta 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 the `new_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](https://www.marqeta.com/docs/core-api/cards/) API reference. **Documentation changes** ## New documentation pages **Platform release:** V.2026.3.2.0 **Sandbox release date:** April 2, 2026 **Production release date:** April 8, 2026 Marqeta has added the following pages to our documentation: | Topic | Description | | - | - | | [Rate Limiting](https://www.marqeta.com/docs/core-api/rate-limiting.md) | Describes the upcoming implementation of rate limits for Core API requests at Marqeta | | [Disputes Evidence Collection](https://www.marqeta.com/docs/core-api/disputes-evidence-collection/) | Describes Regulation E evidence collection requirements for Managed by Marqeta (MxM) customers and hybrid card programs and how to submit evidence using the `/cases` endpoint | | [Subscription Management](https://www.marqeta.com/docs/core-api/subscription-management/) | Describes the new Subscription Management feature and associated API | **No customer-facing changes** ## Platform release V.2026.3.16.0 **Sandbox release date:** April 14, 2026 **Production release date:** April 15, 2026 The V.2026.3.16.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. ## Related topics - [March 2026 Card Issuing and Processing Release Notes](https://www.marqeta.com/docs/developer-guides/card-issuing-processing-release-notes/2026-03.md) - [April 2026 UX Toolkit Release Notes](https://www.marqeta.com/docs/developer-guides/ux-toolkit-release-notes/2026-04.md) - [May 2026 Card Issuing and Processing Release Notes](https://www.marqeta.com/docs/developer-guides/card-issuing-processing-release-notes/2026-05.md) - [June 2026 Card Issuing and Processing Release Notes](https://www.marqeta.com/docs/developer-guides/card-issuing-processing-release-notes/2026-06.md) - [July 2026 Card Issuing and Processing Release Notes](https://www.marqeta.com/docs/developer-guides/card-issuing-processing-release-notes/2026-07.md)