Spreedly will begin enforcing a 180 day implicit filter on all endpoints that list transactional data on June 1st, 2026. For more details about this change please read our guide.

Spreedly now supports credit_card_full_name as a payment method receiver variable. See our list of supported receiver variables for more information.

Spreedly now supports the merchant_capture_code and processing_type gateway specific fields for Ebanx gateway. For more information on the usage of the fields, please see the Ebanx gateway guide.

Spreedly now supports 3D Secure Global on Ebanx gateway. For more information, please see the Ebanx Gateway Guide.

Spreedly now supports the bank_id gateway specific field for the DLocal gateway. For more information, please see the gateway guide.

Spreedly now provides a last_successfully_used property on all payment method objects which returns the time (in UTC) of when that payment was last used in a successful Authorization, Purchase, Verification, GeneralCredit, OffsiteVerification, or OffsitePurchase transaction. For more details please see our API reference.

Spreedly now supports level II and level III gateway specific fields for the NMI gateway. For more information, please see the gateway guide.

Spreedly has upgraded the Braintree integration to 4.34.0. This update is backward compatible. Merchants can now leverage support for metadata field like payment_account_reference, and Improved library compatibility and XML parsing for more robust transaction processing.

No code changes are required for existing integrations. For more information on using Braintree with Spreedly, please see the Braintree gateway guide.

Spreedly now supports the qr_code_emv and qr_code_image_base64 gateway specific response fields for the PayU Latam gateway. For more information, please see the gateway guide.

Spreedly now supports ACH Store/Third Party Vaulting on the Authorize.net gateway. For more information, please see the gateway guide.