> ## 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. # July 2026 Card Issuing and Processing Release Notes > Release notes for the Card Issuing and Processing platform in July 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. **New features** ## Disputes portal available in early access The new Disputes portal is now available in early access. The portal will eventually replace the Disputes section of the Marqeta Dashboard with a unified platform that features guided agent workflows, enhanced investigation tools, embedded communications, and actionable reporting and insights. The Disputes portal reaches general availability on 15 August 2026. At that point, it will be backed by the standard Marqeta service level agreement (SLA) and support commitments. To begin early access onboarding, contact your Marqeta representative. Once enrolled, access the portal at [disputes.marqeta.com](https://disputes.marqeta.com). For a full overview of the Disputes portal, see [About the Disputes Portal](https://www.marqeta.com/docs/developer-guides/about-disputes-portal). ## New active filter for velocity control and authorization control APIs Marqeta now supports an `active` query parameter on the following list endpoints, giving you visibility into inactive controls without retrieving each one individually. * `GET /v3/velocitycontrols` * `GET /v3/authcontrols` * `GET /v3/authcontrols/exemptmids` Earlier, Marqeta only enabled you to retrieve active controls. If all controls were inactive, the endpoints retrieved an empty list. The `active` parameter accepts the following values. | Value | Returns | | - | - | | `true` | Only active controls. By default, `active` is set to `true`. | | `false` | Only inactive controls. | | `all` | Both active and inactive controls. | For more information, see [Velocity Controls](https://www.marqeta.com/docs/core-api/velocity-controls) and [Authorization Controls](https://www.marqeta.com/docs/core-api/authorization-controls). ## Stop orders now match on original transaction amount **Platform release:** V.2026.7.6.0 **Sandbox release date:** July 20, 2026 **Production release date:** July 23, 2026 Stop order placement and enforcement now include the original transaction amount as part of the matching key, in addition to the card and merchant ID. This resolves the following issues: * **Shared-MID merchants:** For merchants that use a single merchant ID (MID) across multiple recurring subscriptions, such as marketplace subscription billing, a stop order on one subscription no longer blocks authorizations for other subscriptions with a different transaction amount at the same merchant. * **Cross-cycle duplicates:** Placing a stop order for one billing cycle of a recurring charge now conflicts with (returns `409`) an existing stop order for the same card, merchant, and amount, instead of creating a redundant, disconnected stop order per cycle. The stop order response now includes a new field, `original_amount`, which Marqeta derives automatically from the underlying transaction. This field is not a required request parameter. Marqeta also returns a new error code, `403041` (`STOP_ORDER_TRANSACTION_AMOUNT_NOT_AVAILABLE`), when the original transaction amount cannot be determined. For more information, see [Subscription Management](https://www.marqeta.com/docs/core-api/subscription-management/) and [Errors](https://www.marqeta.com/docs/core-api/errors.md). ## New transaction type for processing CHAPS credit payments **Platform release:** V.2026.7.6.0 **Sandbox release date:** July 20, 2026 **Production release date:** July 23, 2026 Marqeta now supports `CHAPS_CREDIT`, a new transaction type for processing Clearing House Automated Payment System (CHAPS) credit payments. This transaction type is available for UK transactions only. UK banks use CHAPS to send same-day payments in British pounds, often for high-value transactions such as property purchases. ## Real-Time Decisioning now allows decisioning on card and address verification transactions **Platform release:** V.2026.7.6.0 **Sandbox release date:** July 20, 2026 **Production release date:** July 23, 2026 Real-Time Decisioning (RTD) now evaluates zero-dollar authorizations, such as card account verification and address verification requests, at the time of the request rather than after the fact. This gives the programs consistent, real-time risk coverage across all authorization types, not just standard purchase authorizations. No action is required from you. This is an automatic enhancement to authorization coverage for existing RTD-enabled programs. ## New decline scenario for partially funded cashback transactions **Platform release:** V.2026.7.6.0 **Sandbox release date:** July 20, 2026 **Production release date:** July 23, 2026 This change applies only to Just-in-Time (JIT) Funding gateway programs. Marqeta now declines the transaction with response code `1875` instead of approving it without the cashback when a JIT Funding gateway partially funds a cashback transaction, such as `authorization.cashback` or `pindebit.cashback`, with an amount that covers the purchase but not the full cashback amount. Cashback cannot be partially approved — it must be fully funded or not included at all. Previously, due to an error in Marqeta processing, Marqeta silently dropped the cashback amount and approved only the purchase portion, which could create a funding discrepancy between the amount funded by the gateway and the amount settled by the network. Response code `1875` declines now include additional context in the `response.additional_information` field, to distinguish between the following decline reasons. | Scenario | Provided context | | - | - | | Terminal or card product does not allow partial approval. This is the existing behavior. | "Gateway approved for partial amount but terminal/card product does not allow partial amount" | | Cashback cannot be partially approved according to the card network rules. This is the new behavior. | "Gateway approved for partial amount but cashback cannot be partially approved per network rules" | For example, for a \$100.00 request consisting of an \$80.00 purchase and a \$20.00 cashback amount: | Amount funded by the gateway | Result | | - | - | | \$0.01 to \$80.00 | Partial approval for the purchase portion only. Existing behavior, no change. | | \$80.01 to \$99.99 | **New:** Declined with response code `1875`, because the funded amount is more than the purchase amount but less than the full requested amount. | | \$100.00 | Full approval, including cashback. No change. | This change does not affect the existing decline scenario where response code `1875` fires when a JIT Funding gateway partially funds a transaction and the terminal or the card product does not support partial approvals. If the JIT Funding gateway funds the full requested amount of purchase plus cashback, the transaction is approved as before. For more information, see [Transaction Response Codes](https://www.marqeta.com/docs/developer-guides/about-transactions.md#_transaction_response_codes) and [Gateway JIT Funding Messages](https://www.marqeta.com/docs/core-api/gateway-jit-funding-messages.md). ## Related topics - [July 2026 UX Toolkit Release Notes](https://www.marqeta.com/docs/developer-guides/ux-toolkit-release-notes/2026-07.md) - [July 2026 Risk, Fraud, and Disputes Release Notes](https://www.marqeta.com/docs/developer-guides/risk-fraud-disputes-release-notes/2026-07.md) - [August 2026 Card Issuing and Processing Release Notes](https://www.marqeta.com/docs/developer-guides/card-issuing-processing-release-notes/2026-08.md) - [April 2026 Card Issuing and Processing Release Notes](https://www.marqeta.com/docs/developer-guides/card-issuing-processing-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)