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.For a full overview of the Disputes portal, see About the Disputes Portal.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.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.
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 theGENERATE_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 developer guide.Fraud reporting for account funding transactions
Effective 18 April 2026, Marqeta will require customers to send thefraud_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_SCAMHOLIDAY_AND_TICKET_SCAMUTILITY_SCAMLOAN_SCAMPARENT_GRANDPARENT_RELATIVE_SCAMJOB_SCAM
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 tocasetransition.* events to receive instant notifications when dispute cases change status. The following event types are available under casetransition.* events: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 withtransaction_reason = NETWORK_SUSPECTED_BIN_ATTACK.For more information on 3DS webhooks, see 3D Secure transition events.