Release Notes

You can configure 3DS OTP messages for your cardholders in French, Italian, Spanish, Polish, and Czech. The localized language for these messages can be configured at the card product or user level.

To learn more, see the config transaction controls object and the metadata object.

Gateway JIT and Authorization webhooks now include additional 3DS parameters to help you make better decisions during authorization based on 3DS authentication details:

Reason code R17 is an optional new code available to RDFIs. Use this code when an ACH entry may have been initiated under questionable circumstances. When you return an entry using R17, you must add “QUESTIONABLE” to the return’s Addenda Information field. Learn more here: Direct Deposits (Beta).

For card fulfillment, you now set expedited shipping and expedited processing time separately. To specify expedited processing time, which shortens the time it takes for a card provider to process, pull, personalize, and pack cards into envelopes, set the expedite field in the /bulkissuance and /card endpoints to true. This expedited service is available only for cards fulfilled by Perfect Plastic Printing and IDEMIA.

To specify expedited shipping for card orders, use the fulfillment.shipping.method field when creating card products in the /cardproducts endpoint, when creating cards in the /cards endpoint, and when creating bulk orders in the /bulkissuance endpoint.

When ordering cards from providers Perfect Plastic Printing and IDEMIA, you can now select from the following generic shipping options:

These options specify shipping companies and services available from the card provider.

For details on specific mapping of shipping companies and services and card providers, contact your Marqeta representative.

The API Keys page has been redesigned to help new developers know what to do with their API keys once they receive them. Improvements include field-level descriptions, a link to the documentation on authentication, and a “Hello, World!” cURL that provides a personalized example of how credentials are used in the console.

The interactive elements that enable you to make calls to our API directly from the website have been redesigned with an overall cleaner design and heightened usability. These elements are available in the Core API Quick Start, all API references pages, and the API Explorer.

The Marqeta platform now includes separate card transition reason codes for lost and stolen cards. The existing reason code 10 now applies only to lost cards, and the new reason code 23 applies to stolen cards. See Create card transition

Authorization, clearing, and Gateway JIT request webhooks now include the transaction_metadata.moto_indicator field to indicate MOTO transactions. Possible values for this field are MANUAL, RECURRING, INSTALLMENT, and OTHERS. This change applies to version two of the transaction model.

Authorization, clearing, and Gateway JIT request webhooks now include the pos.is_installment field to indicate installment transactions.

You can now ignore the suspended state of a card for credit voucher and online refund transactions. Be aware that allowing suspended cards to receive funds entails the associated risk of causing additional issues.

For Visa transactions, the acquiring_reference_id field now uses the six-digit acquirer reference identifier in clearing webhooks.

For Mastercard transactions, some merchants send incremental authorizations after the original authorization was cleared or reversed. These incremental authorizations could not be cleared or expired, which negatively impacted cardholders. The Marqeta platform now processes such transactions as standard authorizations that are cleared or expired based on the actions of the merchant.

An issue occasionally caused an incorrect reset of the offline PIN script flag, which then forced cardholders to reset their PIN multiple times. This issue is fixed in this release.

Some zero-amount authorizations with cashback amounts did not work correctly, impacting the cardholders balance but not allowing them to get cash. This issue is fixed in this release.

USPS_Regular is no longer available for bulk card orders. In the past, you could select USPS_Regular, and this selection would automatically convert to FedEx_Expedited to support tracking information for bulk orders.

Transactions for identical amounts at the same merchant occasionally are mismatched with their reference identifiers. This enhancement provides additional data to help you determine the correct authorization for a given transaction.

The pin_present is now included in Swagger with this release.

Clearing webhooks for Visa transactions now include the correct data in the original_amount field of the currency_conversion object.

Clearing webhooks for Visa transactions now include the correct data for the CROSS_BORDER_ISSUER_FEE.

This change is implemented throughout Marqeta documentation.

The decline_reason field lets you specify the reason why a Gateway JIT Funding transaction was rejected. This field is optional. If you do not include this field in your Gateway JIT Funding response, the transaction is declined with the reason "insufficient funds." The new decline reasons are mapped to the relevant card network response codes. See Gateway JIT Funding Messages.

Several new JIT Funding codes, available as transaction response codes, provide more clarity about JIT Funding decisions for transactions. See Transaction response codes.

Compressed AVS data is commonly used by United Kingdom and European Union merchants during tokenization.

This field indicates whether a PIN was entered during a transaction, and appears in Gateway JIT calls, transaction webhooks, and GET /transactions.

This email address can receive one-time passwords for 3DS authentication. It is useful when the user.email field is null or not set. Send a PUT or POST to /users to set this metadata.

Visa chargeback representment webhooks no longer include incorrect original amounts in the currency_conversion object.

The cardholder_authentication_data object in Gateway JIT and transaction webhooks was being sent unnecessarily for tokenized transactions. This object will now be sent only for transactions where 3DS authentication is attempted.

This new guide covers resetting the PIN retry counter and modifying a program’s PIN retry limit value. It also includes a PIN retry flow that explains how to intervene when a cardholder’s card has been locked out after reaching the maximum number of unsuccessful PIN retries. For details, see About Personal Identification Numbers.

See Accepted Countries.

Other roles can retrieve the list of accepted countries, but cannot change its contents. With this change, the API Explorer will no longer show POST and PUT calls for this endpoint.

You can configure the Marqeta platform to send a webhook whenever a transaction is declined. If a spend control is responsible for declining the transaction, the webhook sent now includes the additional_information field. This field contains the name of the spend control responsible for the transaction being declined. To learn more, read Controlling Spending.

The Mobile Wallet UI now displays the last four digits of the card PAN during PAN swap functions for Mastercard. Previously, the PAN swap was occurring successfully, but was not reflected in the Mobile Wallet UI.

Long business names (up to 255 characters) are now supported when creating or updating a business' payment card information. To learn more, read Businesses.

Visa and Mastercard have added a number of new token requestors as a response to increased tokenization by e-commerce merchants. These token requestors have unique token requestor IDs and use unknown as the token requestor name.

We are currently creating specific, more accurate names for approximately 200 new token requestors on the Marqeta platform. For details, see the token_service_provider object of GET /digitalwallettokens/{token}.

Because the list of token requestor names may change, we recommend not hardcoding against specific values for token requestor names.

Financial advice authorization.clearing transaction events include a new field, amount_to_be_released. This field is useful for automated fuel dispenser (AFD) transactions, where the authorization may be for a fixed amount higher than the actual amount cleared.

You can use this field to update your ledgers to reflect the actual amount more quickly, then release the excess funds back to your customer. For details, see Transaction Events.

Velocity controls that apply to cash withdrawals now support dual-message withdrawal transactions, which are common in the European Union.

Previously, any velocity controls that excluded purchases from consideration also did not limit cash withdrawals. For details, see Controlling Spending.

Digital wallets now update to reflect the status of their digital wallet tokens when a token is suspended or resumed. Previously, suspended tokens appeared active, but their transactions would decline.

Suspended tokens now appear as unavailable for payment in their digital wallets.

The Ledger Management for JIT Funding guide describes how to use information contained in JIT messages to help manage your account ledgers, which transaction events impact the ledger, and best practices for ledger management.

Transaction type authorization.clearing, following a financial advice, returns these fields:

See the Transactions API reference.

Core and DiVA API reference pages now describe the conditions under which the API returns all fields documented as "Conditionally returned."