Spreedly nows supports two additional API endpoints to query and view administrative events related to creating or updating configuration objects. See our API reference for more information on how to integrate and our guide on how to use them.

Spreedly has changed the response body for the redact gateway, retain gateway, redact payment method receiver, and update payment method receiver API calls as noted in our March Newsletter. See our API reference for more information.

Date of Deprecation: JUL 28, 2025
Details: Spreedly will deprecate VR Payment gateway.
Impact: The VR Payment gateway will be redacted and all support for this gateway will be removed from Spreedly.
Questions or Concerns: If you need assistance or have any questions about this change, please contact Spreedly Support.

Added support for Apple Pay and Google Pay to the Pin Payments gateway.

Spreedly now supports transaction sync for StripePaymentIntents. For more information, please see the Syncing gateway transaction gateway guide.

Spreedly now supports stax_payments as a payment method receiver. See our list of supported receiver types for more information.

Spreedly now supports the custom_api_url gateway field for Cardstream. For more information, please see the gateway guide

Spreedly now supports the sender_birth_date gateway specific field for Credorax. Starting June 1, 2025, all AFT transactions must include the sender’s date of birth alongside the existing sender and recipient information. For more information, please see the gateway guide

Spreedly now supports the statement_descriptor_suffix_kanji and statement_descriptor_suffix_kana gateway specific fields on the Stripe Payment Intents gateway. For more information, please see the gateway guide.

Spreedly now supports the MercadoPago and PayU Latam gateway types via Composer. See our Composer documentation for more details.