> ## 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.

# Risk, Fraud, & Disputes Release Notes

<Update label="July 2026">
  ### 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](/docs/developer-guides/about-disputes-portal).
</Update>

<Update label="June 2026">
  ### New features

  #### Real-time fraud decisioning on token provisioning

  The Marqeta Real-Time Decisioning (RTD) engine now integrates directly into the token provisioning flow, letting issuing programs detect and block fraud during token provisioning before a response is returned to the card network.

  If you choose to activate this feature for your program, every token provision request for Visa and Mastercard is evaluated by RTD's rule engine before the network response is issued, providing you with real-time fraud decisioning.

  RTD enables you to set transaction thresholds to detect systematic primary account number (PAN) enumeration from specific token requestors or devices. RTD then automatically blocks token requestors and devices after they exceed configurable thresholds. RTD also enables you to set rules on when you want to unblock requestors and devices after an attack occurs.

  When RTD declines a token provision request due to suspected fraud, the Token Provisioning service returns a standardized network response. This makes declined invalid PANs indistinguishable from fraud-triggered declines to prevent enumeration signal leakage.

  To activate this feature for your program, contact your Marqeta representative.

  ### Enhancements

  #### Enriched data in Real-Time Decisioning

  The Marqeta Real-Time Decisioning (RTD) platform now supports additional transaction and merchant data beyond standard authorization fields, giving programs more context to detect fraud as transactions happen.

  Requests can include order details, account metadata, device information, shipping and billing information, geolocation, and behavioral signals. By combining this additional context with the Marqeta fraud models, you can detect suspicious activity more accurately, reduce false positives, recognize trusted merchants, and improve approval rates for legitimate transactions.

  <Note>
    This data might not be available for all transactions. Enriched merchant data is sourced from third-party data partners and matched against transactions that flow through RTD. If there is no match to an existing transaction in RTD, the data will not be available.
  </Note>
</Update>

<Update label="March 2026">
  ### New features

  #### Fraud feedback via two-way SMS

  Marqeta now enables cardholders to provide feedback via two-way SMS for transactions that have been flagged as potentially fraudulent by the Marqeta Real-Time Decisioning (RTD) platform.

  Through the `GENERATE_SMS` supplementary action available in the RTD platform, you can now configure your RTD rules to send a cardholder an SMS to confirm whether a transaction was genuine or fraudulent. The Marqeta RTD system directly receives the cardholder's response.

  If the cardholder confirms that the transaction was genuine, the Marqeta system will automatically allow the cardholder to retry the transaction within a time window that you can configure in the RTD platform. If the cardholder confirms that the transaction was fraudulent, take appropriate action in accordance with your processes and policies.

  If you are a current RTD customer, you can contact your Marqeta account manager to enable two-way SMS for your program, starting 1 April 2026.

  ### Changed functionality

  #### Disputes processing for transaction below program's dispute threshold

  To ensure that all disputes are visible and meet regulatory compliance, Marqeta has made it mandatory for customers to raise disputes even if the amount of the transaction does not meet the program's dispute threshold.

  Previously, programs individually managed these disputes by providing a provisional credit and writing them off. Now, after you raise the dispute, Marqeta automatically issues a provisional credit and the disputes system applies a program write off without submitting the dispute to the card networks. Marqeta, or your program, sends a notification to cardholders that the case was won and closed, depending on who manages the cardholder communications.

  For customers whose cardholder notifications are not managed by Marqeta, you must implement additional logic to handle the provisional credit webhooks based on the dispute amount.

  For more information about webhook updates, reach out to your Marqeta representative. See also Marqeta's [Disputes under threshold](/docs/developer-guides/about-disputes/#_disputes_under_threshold) developer guide.

  #### Fraud reporting for account funding transactions

  Effective 18 April 2026, Marqeta will require customers to send the `fraud_type_classification` field in `POST /cases` payloads for fraudulent Visa account funding transactions (AFTs) if the `fraud_type` is `MANIPULATION_OF_ACCOUNT_HOLDER`.

  The `fraud_type_classification` field now accepts the following additional values:

  * `CHARITY_SCAM`
  * `HOLIDAY_AND_TICKET_SCAM`
  * `UTILITY_SCAM`
  * `LOAN_SCAM`
  * `PARENT_GRANDPARENT_RELATIVE_SCAM`
  * `JOB_SCAM`

  For more information, see [The fraud\_classification\_type\_dispute\_details object](/docs/core-api/disputes-visa/#_the_fraud_classification_type_dispute_details_object).
</Update>

<Update label="February 2026">
  ### New features

  #### Dispute case transition webhooks

  Marqeta has created webhook events for dispute case transitions, eliminating the need for continuous API polling and enabling real-time notifications for dispute case updates.

  You can now subscribe to `casetransition.*` events to receive instant notifications when dispute cases change status. The following event types are available under `casetransition.*` events:

  | Event type                  | Definition                             |
  | --------------------------- | -------------------------------------- |
  | `open`                      | Case created                           |
  | `open_with_action_required` | Action required                        |
  | `ready`                     | Ready for chargeback submission        |
  | `chargeback.initiated`      | Chargeback submitted                   |
  | `pending_close`             | Temporary state before the case closes |
  | `closed`                    | Case closed                            |
</Update>

<Update label="January 2026">
  ### New features

  #### Added support for Mastercard BIN attack flag in 3D Secure requests

  In compliance with Mastercard's updated requirements, Marqeta now enables card programs to reject 3D Secure (3DS) transactions that Mastercard has flagged as BIN attacks. When Mastercard flags a transaction as a suspected BIN attack, card programs will receive a 3DS completion webhook with `transaction_reason = NETWORK_SUSPECTED_BIN_ATTACK`.

  For more information on 3DS webhooks, see [3D Secure transition events](/docs/core-api/event-types/#_3d_secure_transition_events).

  ### Changed functionality

  #### New evidence collection requirements for disputes

  Marqeta is implementing new evidence collection requirements for dispute events under Regulation E. These requirements vary by program type and are only applicable to programs that are Managed by Marqeta or hybrid.

  | Program type                        | Program responsibility                                                           | Required evidence                                                                                                                          |
  | ----------------------------------- | -------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
  | Marqeta-managed JIT programs        | Program provides money movement evidence; Marqeta handles communications         | Documentation for provisional credit grant, reversal, and permanent credit submitted via API or the disputes portal within 3 business days |
  | Hybrid JIT programs                 | Program provides both money movement evidence and communication evidence         | Documentation for all credit events plus consumer communication records submitted via API or the disputes portal within 3 business days    |
  | Marqeta-managed pre-funded programs | Marqeta handles all evidence collection and communications                       | No evidence required — monitor dispute events through the disputes portal                                                                  |
  | Hybrid pre-funded programs          | Program provides communication evidence; Marqeta handles money movement evidence | Consumer communication dates and content for all credit events submitted via API or the disputes portal within 3 business days             |
</Update>


## Related topics

- [Release Notes](/docs/developer-guides/release-notes-2025.md)
- [2023 Release Notes](/docs/developer-guides/release-notes-2023.md)
- [2025](/docs/developer-guides/risk-fraud-disputes-release-notes/2025.md)
- [2022 Release Notes](/docs/developer-guides/release-notes-2022.md)
- [Card Issuing and Processing Release Notes](/docs/developer-guides/release-notes.md)