Release Notes

We’ve updated Dashboard navigation to make managing your program easier:

If you’re not ready for these changes, you can select the Revert to old button in the Welcome banner at the top of the Dashboard to temporarily revert to the old navigation. Revert is available until June 12, 2023.

Beginning June 2, 2023, when a user submits a fraud dispute on a 3DS transaction, the case management system creates a webhook when it smart-rejects the dispute. See Smart rejects for 3DS case events.

Would you like to keep on top of the latest Marqeta deployments and be notified whenever new release notes are published? Get our new biweekly newsletter conveniently delivered to your inbox by subscribing in the release notes section of the homepage.

You do not need to be a Marqeta customer to sign up, and you can unsubscribe hassle-free at any time.

You can simulate direct deposit event types in both the public and private sandbox environments. For more information, see Simulations 2.0 (Beta) — Direct Deposits.

You can use Postman to run requests for card transaction and direct deposit simulations endpoints. This collection of requests has been saved as a YAML file for your convenience. To access the YAML file, see Postman Collection for Simulations 2.0 (Beta).

There are four new languages available for cardholder notifications such as 3D Secure one-time passcode (OTP) notifications and digital wallet token notifications. You now have the option to send notifications in Dutch, Greek, Portuguese, and Romanian in addition to Czech, French, German, Italian, Polish, Spanish, and Swedish. The default language for notifications is still English. For more information, see Configuring Notification Languages.

The API reference page previously called Simulations 2.0 (Beta) is now specific to the Simulations 2.0 API for card transactions. See Simulations 2.0 (Beta) — Card Transactions.

We are pleased to announce the launch of the Marqeta Status Page. This new, publicly available page is simple to navigate and displays real-time health information for Marqeta’s products and services. Use the status page to stay informed about the critical operational and incident updates happening at Marqeta. It is also a great place to check for the latest announcements and planned maintenance schedules.

To get started, access the status page and subscribe to your preferred notification method. We support email, text messages, webhooks, atom feeds, and RSS feeds. Reach out to your Marqeta representative if you have any questions.

Marqeta currently provides support for Direct Deposit API version 2.0. Version 3.0 is in development and will replace v2 upon release. As this could require changes to your workflows, we are providing notice well in advance so you can plan to update your processes accordingly.

We plan to start migrating programs to the new version in Q3 of 2023. More specific timing and details about the changes required will be available as development progresses. Contact your Marqeta representative for more information.

Beginning 15 April 2023, Visa will implement Compelling Evidence 3.0 changes for Card Not Present (10.4) Visa disputes. Effective on that date, a 10.4 dispute raised against a merchant who has signed up for Compelling Evidence 3.0 can be rejected by Visa, provided there are at least two historic transactions that meet the Remedy Prior undisputed transactions criteria. For details, see the "Rejection from the Visa network for Compelling Evidence 3.0-enabled merchants" section in Managing Visa Disputes and Disputes in the Dashboard.

The text of the following two reason codes has changed in the Visa questionnaire.

The Visa network now requires issuers and programs to report fraud to the card network, regardless of the amount. Whenever a cardholder reports fraud, a fraud report must be created with the card network. Noncompliance with network rules results in fines and suspension of the ability to process chargebacks. For details, see Reporting Fraud in Disputes in the Dashboard and Reporting Fraud in Managing Visa Disputes.

The Transaction Details page of the Marqeta Dashboard has been enhanced to include additional information about transactions, such as transaction and merchant summaries, related transactions, and point-of-sale details. For a detailed guide on how to use the page to investigate commonly occurring issues, see Investigating Transactions in the Dashboard.

Global search, available at the top of the Marqeta Dashboard, has been enhanced to search by transaction token.

The prearbitration.responded event has been added; the scope of this chargeback transition event is limited to Fraud and Authorization reason codes. See Chargeback transition events.

Marqeta now supports sharing Level 2 (L2) and Level 3 (L3) data for card programs by webhook. Enhanced transaction data provide you with detailed information, including important non-financial details about purchases, to help inform your program. For more information, see Level 2 and Level 3 card data events. Contact your Marqeta representative to learn more and get access.

Use the new endpoints to simulate the following transaction types:

Note that these endpoints are currently in beta and subject to change. For more information, see Simulations 2.0 (Beta) — Card Transactions.

The Marqeta credit platform supports PIN-debit credit transactions, force-capture PIN-debit credit authorizations, and PIN-debit credit refunds. For more information, see the related pindebit, pindebit.authorization.clearing, and pindebit.refund event types in the Credit journal entry events reference and the About Credit Account Journal Entries guide.

Use the new endpoints to simulate the following transaction types:

Note that these endpoints are currently in beta and subject to change. For more information, see Simulations 2.0 (Beta) — Card Transactions.

You can simulate various transaction event types in both the public and private sandbox environments. For more information about how to simulate these transaction events, see Simulations 2.0 (Beta) — Card Transactions.

Two new RiskControl Real-Time Decisioning reports have been added to the Marqeta Dashboard:

Learn how to use these reports in the Marqeta Dashboard by reading Reports in the Dashboard. Additional details about these reports are provided in Reports In-depth.

To retrieve the transaction count by rules using the DiVA API GET /views/cptrxn/rule/detail endpoint, see Real-Time Decisioning Transaction Count by Rules. For details on using the DiVA API GET /views/cpauth/detail endpoint to retrieve the authorizations data, see Real-Time Decisioning Authorizations.

The Delinquency feature is now available. Delinquency is a part of the Marqeta credit platform’s Credit Account Servicing offerings.

Use the new Delinquency endpoints to view details on a credit account’s delinquency state and delinquency state transitions. An account is considered delinquent if it is past due on its payments.

For the complete endpoint reference, see Delinquency.

Marqeta sends webhook notifications when an account’s delinquency state transitions between delinquent and current. For more, see Credit account delinquency transition events in Event Types.

Marqeta’s Interactive Voice Response (IVR) is a program-specific, white-label product used by your cardholders to interact with the Marqeta platform. With IVR, your cardholders use their landline or mobile telephone to perform basic functions such as activating a card, checking an account balance, reporting a card as lost/stolen, and speaking with a customer support representative. You can also use the IVR product to comply with Payment Card Industry Data Security Standard (PCI DSS) requirements for your program.

The IVR product has recently been migrated to a newer high-performance platform that shortens the time required to launch your program by up to 75%. Built on a modern, elastic stack, this new platform provides greater availability and heightened visibility, enabling Marqeta to monitor IVR health more proactively and react even faster in the event of an issue.

To learn more about IVR and activating it for your program, contact your Marqeta representative.

The allowable values for the encrypted_pass_data and ephemeral_public_key fields on the Digital Wallets Management page of the Core API collection have been corrected from 255 char max to Any value.

The Card Transitions page of the Core API collection now correctly describes that setting the sync_state_with_dwts field to true synchronizes the state of the card’s associated tokens with the card’s new state.

The Credit Programs and Accounts section of Platform Overview has been expanded to include information about credit programs, credit account management, rewards and redemptions, and more.

The About Credit Account Journal Entries page now has a section, Time fields, that explains how the meanings of the created_time, request_time, and impact_time journal entry fields change for different transaction types and status field values.

The About Credit Account Journal Entries page now includes a section that describes the differences between the state and status fields, fields of journal entries.

Marqeta’s customizable widgets enable your cardholders to securely interact with your customer applications in compliance with the Payment Card Industry Data Security Standard (PCI DSS). Beginning in January 2023, the widgets offer support for an additional language: Portuguese (Brazil), which complements the existing language set of English (US), Czech, French (Canada), French (France), German, Italian, Polish, Spanish, and Swedish.

This release of the Marqeta platform includes two new fields in the ThreeDSAuthenticationRequest object: three_ds_requestor_url and three_ds_requestor_app_url. These fields provide more information about merchants requesting 3D Secure authentication.

For more information about these new fields, see The ThreeDSAuthenticationRequest object.

An issue that set the value of the pin_present field to false for all offline PIN transactions has been resolved in this release for both the Visa and Mastercard networks.

This release of the Marqeta platform fixes an issue that prevented filtering results from the GET /digitalwallettokens endpoint by the token field.

An issue that caused pre-authorization transactions to be incorrectly identified, thus creating duplicate transactions, has been resolved in this release.