Spreedly now supports Apple Pay and Google Pay payment methods for NMI gateway.

Spreedly now supports the merchant_descriptor_city, merchant_descriptor_state, merchant_descriptor_country, and submerchant_id gateway specific fields for the CyberSource gateway. For more information, please see the gateway guide.

Spreedly now supports the store_id gateway specific field on the MerchantWarrior gateway. For more information, please see the gateway guide .

Spreedly now supports billapay, frontier_airlines, and verifone as payment method receivers. See our list of supported receiver types for more information.

Spreedly has made some Stored Credential updates to the CyberSource Gateway. The stored credential field reason_type will be sent for all stored credential transactions in the commerceIndicator CyberSource field. If the reason_type is ‘unscheduled’ we will set the commerceIndicator as ‘internet’. ’. If an initial transaction is Customer Initiated (CIT), then we will pass subsequentAuthFirst as ‘true’.

Spreedly now supports the issuer_country gateway specific response field for the Checkout.com gateway. For more information, please see the gateway guide.

This change ensures that all fields passed in during the creation of ThirdPartyGooglePay and ThirdPartyApplePay are saved. Therefore, fields such as those corresponding to billing or shipping address will now be saved.

Spreedly now supports the risk gateway specific field on the Checkout V2 gateway. For more information, please see the gateway guide.

Spreedly will now set retry_logic as true and generate an idempotency_key for customers if the idempotency_key is not valid or one is not provided and if retry_logic is true or not provided. These two Orbital gateway specific fields will enable Orbital Retry Logic, which is a function available for Orbital Gateway to reprocess transactions when there is an unknown result on a transaction request.

Spreedly has standardized the error responses returned due to invalid Accept or Content-Type headers. Users will now receive a 406 Not acceptable for an invalid or unsupported Accept header, and a 415 Unsupported media type for a POST, PUT, or PATCH with a missing, unsupported, or invalid Content-Type header.