DOCS

New!

/

5 minute read

May 4, 2020

Release Notes

May 2020

Changed functionality

For the accepted_countries endpoint, POST and PUT are newly restricted to Admin users only

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.

Webhooks provide spend control details for declined transactions

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.

Last four digits of PAN displayed in digital wallets during PAN swap functions

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.

Improved support for long business names

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

April 2020

New features

Visa and Mastercard have added new token requestor names

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 events include amount to be released

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 supported for dual-message withdrawal transactions

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.

Changed functionality

State of digital wallet tokens reflected in wallets

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.

Notable documentation changes

New ledger management developer guide

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.

Newly documented fields in transaction response model

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

Name Description

amount_to_be_released

Amount to release following a financial advice.

preceding_transaction

Object containing the amount and token of the preceding authorization transaction.

See the Transactions API reference.

Conditionally returned fields explained

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

Have any feedback on this page?

If you feel we can do anything better, please let our team know.

We strive for the best possible developer experience.