> ## 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.
# 2023 Release Notes
> Release notes are a convenient, central location to learn about the new features, improvements, and documentation changes in each of Marqeta's products. Updated 2-4 times a month.
The end-of-year holiday season represents a peak traffic period for many of Marqeta’s card programs and customers. In addition, we are expecting increased transaction volume during this time, based on initial feedback we received.
In order to ensure an optimal cardholder experience during the 2023 holiday season, we are instituting a code freeze for the Marqeta platform over the holiday period. Biweekly platform updates will not be deployed from 10 November 2023 until the second week of January 2024. For more information, contact your Marqeta representative.
Notable documentation changes
Marqeta Dashboard documentation rearchitecture
The [Marqeta Dashboard](https://app.marqeta.com/) documentation pages have been consolidated into one location under **Marqeta Dashboard** in the left-side navigation panel. Several pages have been reorganized for improved usability. See [Marqeta Dashboard and Quick Start](/developer-guides/dashboard-overview-and-quick-start/).
Changed functionality
Fixed: card\_acceptor object not inheriting values from the parent transaction
An issue whereby default values were erroneously being populated in the fields of the `card_acceptor` object has been fixed in this release. Impact was limited to the responses returned by the following Simulations 2.0 endpoints:
* `authorization.reversal`
* `authorization.advice`
* `authorization.incremental`
The `card_acceptor` object now correctly inherits the values from the parent transaction for all affected transaction types.
For more information, see [Simulations 2.0 — Card Transactions](/core-api/simulations-card-transactions/).
General availability (GA) release of our chatbot, Docs AI
We are excited to announce the general availability (GA) release of our documentation chatbot, Docs AI. With Docs AI, you have a real-time companion offering you easy-to-understand answers to your product-related questions. Faster than searching the documentation directly, this is a new, intuitive, and engaging way to discover the Marqeta platform. Our chatbot incorporates OpenAI’s natural language technology and responds to questions with a human-like question/answer format that summarizes the most relevant excerpts from the Marqeta Docs site. Spend less time searching for information and more time writing code.
To access Docs AI, visit [Marqeta Docs](/developer-guides/), then click the **✧ Ask Docs AI** button in the upper-right corner of the screen. For more information, see our [blog](https://www.marqeta.com/blog/elevate-your-experience-introducing-marqeta-docs-ai) or the [AI Assistant](/developer-guides/assistant-help/) help page.
Processing changes for Visa disputes
The following changes apply to the Visa disputes consumer processing questionnaire and to the processing rules, effective 14 October 2023.
Consumer processing questionnaire changes
The following changes apply to the Visa consumer processing questionnaire:
* **12.5, Incorrect Transaction Amount Disputes:** A copy of the transaction receipt or other record with the correct transaction amount is required when attempting to submit to the card network. Using the [Marqeta Dashboard](https://app.marqeta.com/), this information must be provided in order to proceed with the dispute. If you initiate a dispute with the card network using the `/cases` endpoint without a copy of the transaction receipt or other record with the correct transaction amount, the dispute will be smart-rejected and then moved to **Open with Action Required**.
* **13.1, Merchandise/Services Not Received:** There are now two additional questions included in the consumer processing questionnaire. For details, see [Consumer disputes](/developer-guides/managing-visa-disputes/#_consumer_disputes) in Managing Visa Disputes and [The service\_not\_provided\_merchandise\_not\_received\_details object](/core-api/disputes-visa/#_the_service_not_provided_merchandise_not_received_details_object) in the Visa Disputes API Reference.
Processing rule changes
The following changes apply to the Visa dispute processing rules:
* **10.3, Other Fraud for Card-Present Environment:** Now valid only for key-entered transactions. Unattended transactions are not valid after 14 October 2023.
* **12.6, Duplicate Processing or Paid by Other Means:** Now requires that the duplicate take place on the same transaction date and for the same transaction amount.
For a description of the Visa processing rules, see [Dispute reasons](/core-api/disputes-visa/#_the_dispute_details_dispute_reason_field).
A new home for Marqeta’s sub-processor list
Marqeta can engage sub-processors to assist with the provisioning of the card program management and processing services offered to our customers. We maintain a [list of all our sub-processors](https://www.marqeta.com/sub-processors), which you can now access at any time on the main Marqeta website.
Whenever this list is updated, we will provide notice here in the Release Notes. The notification updates formerly delivered via email have been discontinued.
New features
New Data Products and Insights report
A new Data Products and Insights report, Authorization and Clearing Comparison Detail, is available. This report links authorizations to clearing details, significantly reducing the time required to identify the clearing differences per transaction. For more information, see [Authorization and Clearing Comparison Detail](/developer-guides/data-products-and-insights/#_authorization_and_clearing_comparison_detail).
Gateway JIT Funding implementation sample code now in GitHub
You can now download the JIT Funding implementation sample code from the [Marqeta GitHub repository](https://github.com/marqeta/reference-app).
For more information about the Gateway JIT Funding implementation sample code, see [Gateway JIT Funding implementation sample code](/developer-guides/gateway-jit-funding-implementation-sample-code/).
Support for fleet card use cases on both the Mastercard and Visa card networks
Marqeta now offers support for fleet card use cases on both the Mastercard and Visa card networks, providing fleet managers with greater control and security over fleet expenditures. Both Managed By and Processed By card programs can take advantage of this offering.
The fleet card is a commercial, driver-assigned credit card used by managers of vehicle fleets to pay for expenses incurred by their drivers, such as fuel and refreshments. With this unsecured, non-revolving card, you can set spending limits, transaction categories, and usage restrictions on fleet cards to manage expenses effectively. By spending with a card instead of cash or checks, your program can capture critical L2/L3 data points and manage your vehicles in a cost-efficient and convenient manner.
For more information, contact your Marqeta representative.
Simulations 2.0 general availability (GA) release
We are excited to announce the general availability (GA) release of the Simulations 2.0 service. Simulations allow you to test functionality — that would normally be triggered by an external event in a live environment — in a sandbox environment. For example, you can simulate when a customer uses a payment card at a point of sale.
Simulations 2.0 introduces scalable, extensible support for a wide range of event types. It follows an API-driven approach, where the structure of the service is defined by its API specification. With Simulations 2.0, you can replicate all supported transactions from the [existing Simulations service](/core-api/simulating-transactions/), as well as a wide range of new endpoints. The new endpoints include, but are not limited to, refunds, incremental authorizations, account funding transactions (AFTs), original credit transactions (OCTs), PIN-debit transactions, and multi-currency international transactions.
Simulations 2.0 provides an OpenAPI YAML file that can be imported in Postman. The OpenAPI file can also be used to generate a client to enable seamless interaction with the Simulations 2.0 RESTful APIs.
##### Simulations 2.0 (GA) — card transactions
Use the `/simulations/cardtransactions/*` endpoints to simulate transactions involving a card, such as a purchase or a refund back to the card. You can simulate card transaction events in both the public and private sandbox environments. For more information, see [Simulations 2.0 — Card Transactions](/core-api/simulations-card-transactions/).
##### Simulations 2.0 (GA) — direct deposits
Use the `/simulations/directdeposits/*` endpoints to simulate event types related to deposit accounts. You can simulate direct deposit event types in both the public and private sandbox environments. For more information, see [Simulations 2.0 — Direct Deposits](/core-api/simulations-direct-deposits/).
##### Postman collection for Simulations 2.0 (GA)
With [Postman](https://www.postman.com/), you can run requests for [card transactions](/core-api/simulating-transactions/) and [direct deposit](/core-api/simulating-transactions/) simulations endpoints. The Simulations 2.0 Postman collection has been saved as a [downloadable YAML file](/core-api/postman-collection-simulations#_simulations_2_0_postman_collection_file) for your convenience. For more information, see [Postman Collection for Simulations 2.0](/core-api/postman-collection-simulations/).
Notable documentation changes
Developer deep-dive: Simulations 2.0 (GA) webinar
On 17 October 2023, members of Marqeta’s Developer Experience (DX) team hosted a live webinar called *Testing Transactions with Simulations 2.0*, followed by a Q\&A session.
In this webinar, we explore using our sandbox environment, how to get started with simulating transaction event types, and how to leverage the Simulations 2.0 Postman collection. We also highlight what’s new in Simulations 2.0 compared to the existing simulations service and why you should switch to Simulations 2.0 if you are using existing simulations.
A [recording of the webinar](https://event.on24.com/wcc/r/4365668/A6F9D89949274C5083C91B5DD067C3B2/) is available for viewing (registration is not required).
Developer deep-dive: Hands-on walkthrough on using Simulations 2.0 (GA) in the sandbox
Are you ready to try the Simulations 2.0 service out yourself? Follow our step-by-step process to use Simulations 2.0 to test E2E network transaction flows in the sandbox environment: [Developer Community Post - Introducing Simulations 2.0](https://community.marqeta.com/t5/developer-blogs/introducing-simulations-2-0/ba-p/1024/).
Deprecated features
Deprecation of Marqeta.js v1.1.0
A coordinated upgrade from Marqeta.js v1.1.0 to v2.0.0 will be required by 31 October 2023. If your program is already on Marqeta.js v2.0.0, this change does not apply to you.
* If your program only uses the [Activate Card and Set PIN widgets](/developer-guides/using-activate-card-and-set-pin-widgets/), you can ignore the update.
* If you want to use the `ShowPan`, `CopyCVV`, or `RevealPIN` functionality of Marqeta.js in the near future, you should enable Marqeta.js v2.0.0 and avoid this upgrade.
These changes require your program to [migrate to Marqeta.js v2.0.0](/developer-guides/using-marqeta-js/) and update the library’s [configuration object](/developer-guides/using-marqeta-js/#_the_configuration_object) by 31 October 2023 at the very latest. For your convenience, Marqeta has made Marqeta.js v2.0.0 backward compatible with v1.1.0 of the library until v2.0.0 is adopted.
Please notify [support@marqeta.com](mailto:support@marqeta.com) of the date and time when you plan to upgrade to Marqeta.js v2.0.0 and update the library’s configuration object. Marqeta will then update your program’s internal client tokens shortly thereafter.
For more information, contact your Marqeta representative.
Changed functionality
##### Validation enhancements for Visa CAVV
The `cardholder_authentication_data` object now includes two new fields to enhance cardholder authentication verification value (CAVV) validation on the Visa card network. You can find the new `cavv_validation_amount` and `raw_cavv_data` fields in the transaction payloads of Gateway JIT Funding requests, webhooks, and `GET /transactions` requests.
To enable these fields, contact your Marqeta representative.
For detailed information about these fields, see the [Transactions](/core-api/transactions/#get_transactions_token) API reference.
##### Updated User KYC verification fields
Some banks require a cardholder’s `phone` and `email` information to perform KYC verification. The descriptions for the `phone` and `email` fields in the `user` resource have been updated to reflect this conditional requirement. You can see these updated descriptions in [Create user](/core-api/users/#post_users).
To support this requirement, Marqeta now includes two new [User KYC failure codes](/core-api/kyc-verification/#_user_kyc_failure_codes): `EmailIssue` and `PhoneIssue`.
To determine if you need to include these fields to perform KYC verification for your cardholders, contact your Marqeta representative.
Changed functionality
##### Fixed: Incorrect transaction type in JIT Funding clearing payload after stand-in processing event
An issue that caused JIT Funding notifications to categorize clearing events after stand-in processing events as `pgfs.force_post` transaction types has been fixed in this release.
For more information about JIT Funding notifications, see [JIT Funding notifications](/core-api/gateway-jit-funding-messages/#_jit_funding_notifications).
##### Fixed: Missing field in swagger.json
Marqeta’s `swagger.json` file now includes the `acquirer_reference_data` field. This 23-digit string appears in the payload of certain webhooks, and contains data about clearing events that can be used to tie a clearing event back to the card network.
The 2023.10.2.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.
New features
Use Marqeta’s new chatbot, Docs AI, to find the answers you need
Marqeta is on a mission to provide developers and potential customers with a new, intuitive, and engaging way to discover the Marqeta platform. Our Docs site now features a chatbot that you can use to quickly find answers to your questions instead of searching the documentation directly. The chatbot incorporates OpenAI’s natural language technology and responds to questions with a human-like question/answer format that summarizes the most relevant excerpts from the Marqeta Docs site. Spend less time searching for information and more time writing code.
Our chatbot is currently available in open beta. To access it, visit [Marqeta Docs](/developer-guides/), then click the **✧ Ask Docs AI** button in the upper-right corner of the screen. For more information, see our [blog](https://www.marqeta.com/blog/elevate-your-experience-introducing-marqeta-docs-ai) or the [AI Assistant](/developer-guides/assistant-help/) help page.
Data Products and Insights
The new Data Products and Insights feature provides reports and insights to help you improve your card program and performance. For more information, see [Data Products and Insights](/developer-guides/data-products-and-insights/).
Notable documentation changes
New credit reward programs guide
Learn how to use Reward Programs to track reward accruals and manage reward redemptions on a credit account in this new guide: [About Reward Programs](/developer-guides/about-credit-reward-programs/).
New credit account origination tutorial
Learn how to originate a credit account in this new tutorial: [Originate a credit account](/developer-guides/about-credit-accounts/#_tutorial_originate_a_credit_account).
Changed functionality
##### Digital wallet token transaction payloads now include cardholder authentication data
Digital wallet token transaction payloads now include the `cardholder_authentication_data.electronic_commerce_indicator` and `cardholder_authentication_data.verification_result` fields.
For more information about the `cardholder_authentication_data` object, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
##### Three-character country code now included in clearing transactions
Marqeta now includes an [alpha-3 ISO 3166 country code](https://www.iso.org/iso-3166-country-codes.html) in clearing transaction payloads, rather than the previous two-character country code.
The name of the field containing this code depends on which version of the Marqeta Core API Transaction Model you are using:
* In Transaction Model v2, the field is called `card_acceptor.country_code` (used by most programs)
* In Transaction Model v1, the field is called `card_acceptor.country`
For more information about the `card_acceptor` object, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
Changed functionality
##### Transaction payloads now include the local transaction time
Transaction payloads in Gateway JIT messages, webhooks, and `GET /transactions` now include a field to display the local date and time of a transaction at the card acceptor’s location: `local_transaction_date`. You can use this field to determine the correct time of the transaction when filing a dispute.
##### Programmatically decline cryptocurrency transactions on the Mastercard network
You can now configure your card program to automatically decline incoming cryptocurrency transactions on the Mastercard network, based on the `CRYPTOCURRENCY_PURCHASE` value of the `special_condition_indicator` field in the `card_acceptor` object.
To enable this feature, contact your Marqeta representative.
For more information about the `special_condition_indicator` field, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
##### Fixed: Incorrect name on funding sources for business account holders
An issue that caused an incorrect name on funding accounts for business account holders has been fixed in this release.
New features
Redigitization now available for Mastercard
Mastercard customers can now swap digital wallet tokens to different Bank Identification Number (BIN) ranges. This minimizes disruptions and makes it so cardholders do not need to reprovision their new replacement cards to their digital wallets. For more information, contact your Marqeta representative.
Notable documentation changes
New credit program gateway documentation
Learn how to use Credit Program Gateways to exchange messages with Marqeta’s credit platform regarding decisions on transaction authorizations in these new docs:
* Developer guide: [About Credit Program Gateways](/developer-guides/about-credit-program-gateways/)
* API reference: [Program Gateways](/core-api/credit-program-gateways/)
Changed functionality
##### Fixed: Enumerated values in jit\_funding.method field
The enumerated value `pgfs.original.credit.authorization.clearing` has been added to the `method` field of the `jit_funding` object.
A typo in the list of enumerated values for the `method` field of the `jit_funding` object was also fixed in this release.
##### Fixed: Contactless limits not applied to all valid transaction types
An issue that prevented contactless transaction limits from being applied to all valid transaction types has been fixed in this release.
##### Know Your Customer (KYC) verification status changes
The [KYC verification](/core-api/kyc-verification/) endpoints no longer return the `PENDING` KYC status for user account holders. The only values that can be returned now are `SUCCESS` and `FAILURE`.
The 2023.8.7.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.
New features
Get started quickly with our Just-in-Time Funding reference application
Marqeta now offers a reference application to demonstrate how to implement [Just-in-Time (JIT) Funding](/developer-guides/about-jit-funding/). The reference application is a sample web server that demonstrates the implementation of the `/gateway` and `/webhook` endpoints required for integrating with Marqeta’s Gateway JIT Funding feature. You can also use the reference application for Managed JIT Funding, which does not require the `/gateway` endpoint.
The reference application creates a user, card product, card, webhook endpoint, and JIT gateway endpoint for you to use in your sandbox environment. You can then run the scripts included in the reference application to simulate several common transaction flows and view their results to better understand how each component works during a JIT Funding transaction.
The reference application is currently in beta and subject to change. If you are interested in using the JIT Funding reference application, contact your Marqeta representative for more information.
Notable documentation changes
New credit program implementation guide
Learn how to implement your credit program using the Marqeta Dashboard and Marqeta’s credit platform’s RESTful API features in this new guide:
* [Implementing Your Credit Program](/developer-guides/implementing-your-credit-program/)
The 2023.7.24.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.
New features
##### Visa Fast Funds indicator for dual-message original credit transactions
Marqeta now indicates when a dual-message original credit transaction (OCT) has Visa Fast Funds enabled. If a dual-message OCT has Visa Fast Funds enabled, you will see a value of `true` in the `fast_funds_enabled` field of the `original_credit` object in the transaction payloads of Gateway JIT Funding requests, webhooks, and `GET /transactions` requests.
When you receive a dual-message OCT authorization with Visa Fast Funds enabled, you should make funds available to your user within 30 minutes, which may require a change to your business logic. If an authorization would normally move money to a pending layer, you should move it to a final layer or equivalent for Fast Funds OCTs.
This transaction flow differs from many clearings, in which funds move from a pending layer to a final layer. It is critical that you implement validation to ensure that you do not double-post funds. When you receive a clearing record for a Fast Funds OCT, it includes the `preceding_related_transaction_token` to link the clearing to the authorization. Your business logic should validate the layer of funds for that authorization: if the clearing is in a final layer as expected, do not take action upon clearing.
When you are ready to implement dual-message Fast Funds OCTs in production, you can pursue enablement of the feature with Visa, as it requires BIN configuration. You must also inform your Marqeta representative so they can update your program’s configuration. Once this configuration change is complete, you can test any ledger changes in sandbox and deploy them to production.
Dual-message OCTs with Visa Fast Funds enabled are considered "good funds" by the Visa network, meaning they will not allow reversals or refunds for any reason other than timeouts. Reversals for Fast Funds OCT timeouts should be handled the same way as any other reversal events, where money moves back to its starting point.
For more information about the `fast_funds_enabled` field, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
##### Programmatically decline cryptocurrency transactions on the Visa network
You can now configure your card program to automatically decline incoming cryptocurrency transactions on the Visa network, based on the `CRYPTOCURRENCY_PURCHASE` value of the `special_condition_indicator` field in the `card_acceptor` object.
To enable this feature, contact your Marqeta representative.
For more information about the `special_condition_indicator` field, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
##### New field in the card product provisioning controls object
You can configure your card product to use the status of a card during digital wallet token authorization transactions using the new `dwt_use_card_status_during_auth` field of the `provisioning_controls` object of your `/cardproducts` endpoint.
If the value for this field is `true`, then digital wallet transactions are declined if the card associated with the digital wallet token is in either the `SUSPENDED` or `TERMINATED` state. The default value for this field is `false`.
For more information about the `/cardproducts` endpoint and the `provisioning_controls` object, see [Card Products](/core-api/card-products/).
New features
New Dashboard navigation
We’ve updated navigating the Marqeta Dashboard to make managing your program easier:
* **New content navigation** – The content switcher lets you move between workspaces to quickly access the information relevant to you.
* **Program Controls workspace** – Manage your program, users, and audit logs via the Program Controls workspace.
* **Data & Insights workspace** – Access all of your Reports from the Data & Insights workspace with dynamic filtering, sorting, and interactive visualizations.
* **Collapsible sidebar** – Use the collapsible sidebar to open up the dashboard for easier viewing and smoother workflows.
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 12 June 2023.
New webhook for 3DS smart rejects
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](/core-api/event-types/#_smart_reject_for_3ds_case_events).
Automated state transitions for Visa disputes
The following enhancements have been added for Visa disputes:
* Automatically transition a dispute case state from `initiated` to `representment`.
* Download documents associated with representment and make them available for users to review in the Marqeta Dashboard.
* Submit a prearbitration to Visa in the Marqeta Dashboard.
* Automatically transition a case to `case.won` when the timeframe expires on the prearbitration request with comments in the transition history.
When creating a dispute case in the Marqeta Dashboard, use the new **Comments** text box to send a comment to Visa. This eliminates the requirement that comments be attached as a PDF file.
Changed functionality
Updated 3DS Automated Decisioning Reporting endpoint
The 3DS Automated Decisioning Reporting endpoint has been updated. After June 30, 2023 the Davinci endpoint will no longer be accessible to retrieve 3DS Automated Decisioning Reports. For information, see [3DS Automated Decision Service Reporting](/developer-guides/3ds-automated-decision-service-reporting/).
Notable documentation changes
New credit program management guide
Learn about key differences between Marqeta’s two models of credit program management in this new guide:
* [Understanding Credit Program Management Differences](/developer-guides/understanding-credit-program-management-differences/)
Changed functionality
##### Fixed: ATM fees for international transactions settle in USD
An issue that caused ATM fees for non-US transactions to be settled in USD has been fixed in this release.
New features
##### Support for the Federal Reserve Regulation II clarification
Marqeta supports the Federal Reserve Regulation II ("Durbin Amendment") requirements for card-not-present (CNP) transactions.
Because domestic debit networks are more readily able to support CNP transaction processing, the Federal Reserve issued its "Regulation II Clarification" in October 2022. Effective 1 July 2023, issuers must enable an additional "unaffiliated" network on debit and general-use prepaid cards to allow the merchant a routing choice for CNP transactions.
"Unaffiliated" means that the two card networks selected by the issuer cannot be owned and operated by the same network. For example, Pulse is unaffiliated with Visa and Mastercard because it is owned by the Discover network.
By enabling the PULSE PINless CNP network on our Visa- and Mastercard-branded US debit card programs, Marqeta complies with the requirement to support two unaffiliated routing options.
Changed functionality
##### Visa Risk Manager response code included in transaction payloads
Marqeta now passes the Visa Risk Manager response code 59 (suspected fraud) in the new `incoming_response_code` field of the `network_metadata` object in the transaction payloads of Gateway JIT Funding requests, webhooks, and `GET /transactions` requests.
##### Fixed: Incorrect decimal calculations for some merchant category code (MCC) groups
An issue that caused incorrect decimal amount calculations for some MCC group configurations has been fixed in this release.
New features
Subscribe to the Release Notes Newsletter
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](/developer-guides/) 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.
Simulations 2.0 (Beta) — Direct Deposits
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](/core-api/simulations-direct-deposits/).
Postman collection for Simulations 2.0 (Beta)
You can use [Postman](https://www.postman.com) to run requests for [card transaction](/core-api/simulations-card-transactions/) and [direct deposit](/core-api/simulations-direct-deposits/) 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)](/core-api/postman-collection-simulations/).
Four new cardholder notification languages
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](/developer-guides/configuring-notification-languages/).
The 2023.5.29.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.
Changed functionality
##### Special condition indicator now included in transaction payloads
The `special_condition_indicator` field is now included in the transaction payloads of JIT gateway requests, webhooks, and `GET /transactions` API requests for transactions on the Visa card network. When a payload includes the `special_condition_indicator` field, it means that the transaction involves quasi-cash (i.e., traveler’s checks, money orders, foreign currency, gaming chips), a cryptocurrency purchase (including transactions that load or unload cryptocurrency wallets), or debt repayment.
For more information about the `special_condition_indicator` field, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
Changed functionality
##### Network metadata now included in Transaction Model v1 payloads
The `network_metadata` object is now included in the transaction payloads of JIT gateway requests, webhooks, and `GET /transactions` API requests using Transaction Model v1 of the Marqeta Core API.
For more information about the `network_metadata` object, see the [Transactions API reference](/core-api/transactions/#get_transactions_token).
##### New transaction response code
This release of the Marqeta platform includes a new transaction response code: `1927: Account transfer not allowed`. The Marqeta platform returns this response code to decline account transfer transactions, which Marqeta does not support.
For more information about the codes that are returned by the Marqeta platform to help you understand the response to a transaction, see [Transaction response codes](/developer-guides/about-transactions/#_transaction_response_codes).
##### Fixed: Mismatch between GPA load and clearing amounts
An issue that caused a mismatch between GPA loads and clearing transactions has been resolved in this release.
##### Fixed: Refund clearing transactions associated with incorrect authorizations
An issue that caused `refund.authorization.clearing` transactions to be associated with the incorrect `refund.authorization` transaction has been resolved in this release.
Notable documentation changes
Simulations 2.0 (Beta) reference renamed and updated
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](/core-api/simulations-card-transactions/).
New features
We are pleased to announce the launch of the [Marqeta Status Page](https://status.marqeta.com/). 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](https://status.marqeta.com/). We support email, text messages, webhooks, atom feeds, and RSS feeds. Reach out to your Marqeta representative if you have any questions.
Upcoming Direct Deposit API version update
Marqeta currently provides support for [Direct Deposit API version 2.0](/core-api/direct-deposits/). 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.
Compelling Evidence 3.0 for disputes in the Visa network
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](/developer-guides/managing-visa-disputes/#_rejection_from_the_visa_network_for_compelling_evidence_3_0_enabled_merchants) and [Disputes in the Dashboard](/developer-guides/disputes-dashboard/#_rejection_from_the_visa_network_for_compelling_evidence_3_0_enabled_merchants).
Dispute reason code changes for Visa
The text of the following two reason codes has changed in the Visa questionnaire.
##### Cancelled Recurring Transaction Details, 13.2
The `Cancellation date` text has changed to `Date cardholder withdrew permission to charge the Payment Credential`. If a value is entered for this field, contact method details with the merchant are required. For details, see [Dispute questionnaires](/developer-guides/managing-visa-disputes/#_dispute_questionnaires) in Managing Visa Disputes and the [cancelled\_recurring\_transaction\_details object](/core-api/disputes-visa/#_the_cancelled_recurring_transaction_details_object) in the Disputes (Visa) API Reference.
##### Cancelled Merchandise or Services, 13.7
Visa now requires that two additional questions be answered for cancelled services:
* Did the cardholder attempt to resolve the dispute with the merchant?
* If No to the above, is the attempt prohibited by regulation?
For details, see [Dispute questionnaires](/developer-guides/managing-visa-disputes/#_dispute_questionnaires) in Managing Visa Disputes and the [cancelled\_merchandise\_or\_services\_details object](/core-api/disputes-visa/#_the_cancelled_merchandise_or_services_details_object) in the Disputes (Visa) API Reference.
Reporting fraud from the Disputes dashboard or Cases endpoint
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](/developer-guides/disputes-dashboard/#_reporting_fraud) in Disputes in the Dashboard and [Reporting Fraud](/developer-guides/managing-visa-disputes/#_reporting_fraud) in Managing Visa Disputes.
Enhanced transaction details
The [Transaction Details](/developer-guides/customers-dashboard/#_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](/developer-guides/transaction-details-dashboard/).
Search by transaction token
Global search, available at the top of the Marqeta Dashboard, has been enhanced to search by transaction token.
New chargeback transition event
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](/core-api/event-types/#_chargeback_transition_events).
Level 2 and Level 3 webhooks
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](/core-api/event-types/#_level_2_and_level_3_card_data_events). Contact your Marqeta representative to learn more and get access.
The 2023.4.17.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.
The 2023.4.3.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.
Notable documentation changes
New endpoints added to Simulations 2.0 API (Beta)
Use the new endpoints to simulate the following transaction types:
* `account.funding.auth_plus_capture`
* `account.funding.auth_plus_capture.reversal`
* `authorization.atm.withdrawal`
* `authorization.cashback`
* `authorization.clearing.atm.withdrawal`
* `authorization.clearing.quasi.cash`
* `authorization.quasi.cash`
* `original.credit.authorization`
* `original.credit.authorization.clearing`
* `original.credit.auth_plus_capture`
* `original.credit.auth_plus_capture.reversal`
* `pindebit.quasi.cash`
Note that these endpoints are currently in beta and subject to change. For more information, see [Simulations 2.0 (Beta) — Card Transactions](/core-api/simulations-card-transactions/).
The 2023.3.20.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.
New features
##### State code conversion for Visa transactions
For Visa transactions in the United States and Canada, the Marqeta platform now converts the two-digit ANSI state or provincial code received from the card network to an [alpha-2 state or provincial code](/core-api/kyc-verification/#_valid_state_provincial_territorial_and_federal_abbreviations) in the `card_acceptor.state` field.
Changed functionality
##### Fixed: Inconsistent value for payment\_channel field between authorization and clearing
An issue that caused inconsistent `payment_channel` values between a transaction’s authorization and its clearing has been resolved in this release.
##### Fixed: Corrected gpa.impacted\_amount field in Mastercard clearing transactions
An issue that caused the `gpa.impacted_amount` field to show a different value than the `settlement_data.amount` field has been resolved in this release. The `gpa.impacted_amount` field now includes both the billing amount and any applicable currency conversion fees. You can now use the `gpa.impacted_amount` field to update your cardholder’s ledger without performing any additional adjustments or calculations.
##### Fixed: Cards blocked when merchant entered incorrect expiration date
An issue that caused the Marqeta platform to reject transactions and block cards if merchants entered the card expiration date incorrectly has been resolved in this release.
##### Fixed: Incremental transactions not handled correctly
An issue that caused some incremental transactions to be treated as initial transactions has been resolved in this release.
##### Fixed: Incorrect impacted amount in some ATM partial reversals
In some partial reversal transactions completed at an automated teller machine (ATM), the `impacted_amount` field incorrectly included the card network fee in cases where that fee should also have been reversed. This issue has been resolved in this release.
Notable documentation changes
New pindebit event types added for journal entries
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](/core-api/event-types/#_credit_journal_entry_events) reference and the [About Credit Account Journal Entries](/developer-guides/about-credit-account-journal-entries/) guide.
New endpoints added to Simulations 2.0 API (Beta)
Use the new endpoints to simulate the following transaction types:
* `authorization.advice`
* `authorization.incremental`
* `pindebit`
* `pindebit.authorization`
* `pindebit.authorization.clearing`
* `pindebit.authorization.reversal`
* `pindebit.cashback`
* `pindebit.refund`
* `pindebit.atm.withdrawal`
* `pindebit.balanceinquiry`
* `refund`
* `refund.authorization`
* `refund.authorization.clearing`
* `refund.authorization.reversal`
Note that these endpoints are currently in beta and subject to change. For more information, see [Simulations 2.0 (Beta) — Card Transactions](/core-api/simulations-card-transactions/).
New features
Simulations 2.0 (Beta)
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](/core-api/simulations-card-transactions/).
New RiskControl Real-Time Decisioning reports
Two new RiskControl Real-Time Decisioning reports have been added to the Marqeta Dashboard:
* The **RiskControl Real-Time Decisioning—Authorizations** report provides information on all the transaction authorizations processed by Real-Time Decisioning.
* The **RiskControl Real-Time Decisioning—Transaction Count by Rules** report provides the count of transactions per triggered rule for a program.
Learn how to use these reports in the Marqeta Dashboard by reading [Reports in the Dashboard](/developer-guides/reports-dashboard/#_riskcontrol_real_time_decisioning). Additional details about these reports are provided in [Reports In-depth](/developer-guides/reports-in-depth/#_riskcontrol_real_time_decisioning).
To retrieve the transaction count by rules using the DiVA API `GET /views/cptrxn/rule/detail` endpoint, see [RTD Transaction Count by Rules](/diva-api/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](/diva-api/real-time-decisioning-authorizations/).
New Delinquency endpoints added to Credit Account Servicing
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](/core-api/credit-account-delinquency/).
Marqeta sends webhook notifications when an account’s delinquency state transitions between delinquent and current. For more, see [Credit account delinquency transition events](/core-api/event-types/#_credit_account_delinquency_state_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.
Marqeta platform releases now occur biweekly until further notice. The next release of the Marqeta platform will be on 7 March 2023.
Changed functionality
##### Multi-currency transaction settlement data included in Pulse card network transaction payloads
You can now view multi-currency transaction settlement data for Pulse card network transactions in Gateway JIT messages, transaction webhooks, and in the response to a call made to `GET /transactions`. See the `currency_conversion.network.settlement_data` object documentation in the [Transactions](/core-api/transactions/) page for more information.
##### Gateway JIT Funding requests for international address verification system transactions
The Marqeta platform now sends Gateway JIT Funding requests for all international address verification system (AVS) transactions.
##### Fixed: Contactless ATM transactions excluded from strong customer authentication rules
An issue that caused transactions at contactless ATMs to be excluded from strong customer authentication (SCA) rules has been resolved in this release of the Marqeta platform.
##### Fixed: Race condition for cards activated upon issuance
An issue that caused a race condition for card programs configured to activate cards upon issuance has been resolved in this release.
Marqeta platform release 2023.2.13.0 was rolled back on 21 February 2023.
Changed functionality
##### Changed reporting expected afternoon refresh times
Expected refresh times for the afternoon data run have been changed to 3:45 AM UTC (start time) and 7:45 AM UTC (completion time). See [Expected refresh and settlement timelines](/developer-guides/reports-in-depth/#_expected_refresh_and_settlement_timelines).
##### Fixed: Incorrect value for offline PIN transactions on Visa network
An ongoing issue that set the `pin_present` field value to `false` for all offline PIN transactions on the Visa network has been resolved in this release.
##### Fixed: Pre-authorization indicator not included in Pulse transactions
An issue that caused the pre-authorization indicator to be excluded from `pindebit.authorization` transactions on the Pulse card network has been resolved in this release.
Notable documentation changes
Updated allowable values on Digital Wallets Management page
The allowable values for the `encrypted_pass_data` and `ephemeral_public_key` fields on the [Digital Wallets Management](/core-api/digital-wallets-management/) page of the Core API collection have been corrected from `255 char max` to `Any value`.
Corrected field description on Card Transitions page
The [Card Transitions](/core-api/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.
Expanded credit section on Platform Overview page
The [Credit Programs and Accounts](/developer-guides/platform-overview/#_credit_programs_and_accounts) section of [Platform Overview](/developer-guides/platform-overview/) has been expanded to include information about credit programs, credit account management, rewards and redemptions, and more.
Added explanation of time fields for journal entries
The [About Credit Account Journal Entries](/developer-guides/about-credit-account-journal-entries/) page now has a section, [Time fields](/developer-guides/about-credit-account-journal-entries/#_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.
Added explanation of the difference between the `status` and `state` fields
The [About Credit Account Journal Entries](/developer-guides/about-credit-account-journal-entries/) page now includes a section that describes the [differences between the `state` and `status` fields](/developer-guides/about-credit-account-journal-entries/#_differences_between_the_state_and_status_fields), fields of journal entries.
New features
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.
The 2023.1.30.0 release of the Marqeta platform was rolled back on 2 February 2023.
The 2023.1.23.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.
New features
##### Application Transaction Counter enabled for all programs
The Marqeta platform now returns the Application Transaction Counter (ATC) for Mastercard transactions that include this data element.
##### New decline reasons for Gateway Just-in-Time Funding transactions
This release adds two new values to the Gateway Just-in-Time (JIT) Funding object’s `decline_reason` field: `CARD_NOT_ACTIVE` and `CARDHOLDER_NOT_ACTIVE`.
Changed functionality
Changes to 3D Secure authentication requests
This release of the Marqeta platform includes two new fields in the `ThreeDSAuthenticationRequest` object: `three_ds_requester_url` and `three_ds_requester_app_url`. These fields provide more information about merchants requesting 3D Secure authentication.
* The `three_ds_requester_url` field shows the fully qualified URL of the merchant’s website or customer care site. This data element provides additional information to help troubleshoot any problems that arise, along with the merchant’s contact information.
* The `three_ds_requester_app_url` field shows the fully qualified URL of the merchant application that initiated the 3D Secure authentication request. For app e-commerce transactions, you can use the `three_ds_requester_app_url` field to redirect your cardholders back to the merchant application after they have completed 3D Secure authentication in their mobile banking application. Redirecting cardholders in this way makes their payment experience smoother and more seamless, thereby reducing cardholder abandonment.
For more information about these new fields, see [The ThreeDSAuthenticationRequest object](/core-api/3ds/#_the_threedsauthenticationrequest_object).
Fixed: Incorrect value for offline PIN transactions
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.
Fixed: Filtering GET /digitalwallettokens results
This release of the Marqeta platform fixes an issue that prevented filtering results from the `GET /digitalwallettokens` endpoint by the `token` field.
Fixed: Duplicate transactions from misidentified pre-authorizations
An issue that caused pre-authorization transactions to be incorrectly identified, thus creating duplicate transactions, has been resolved in this release.