Spreedly now supports the merchant_descriptor_name, merchant_descriptor_address1, and merchant_descriptor_locality gateway specific fields for the CyberSource REST gateway. For more information, please see the gateway guide.
Spreedly is upgrading our Stripe integration to align with the latest Stripe API versions. This ensures continued compatibility and improved handling of Transactions with Stripe.
Timeline
A 60-day transition period begins from this announcement. Effective date as 7th July 2026.
During this time, the existing integrations will continue to work as-is. You must test and implement changes to your Spreedly integration if you use certain features.
What’s Changing The default integration by Spreedly is moving to version 2025-10-29.clover
- Balance Transactions & Fees: Transaction amounts and fees will now reflect the captured amount rather than the authorized amount
- Refund Handling: For partial captures or cancellations Stripe will not create a Refund object
- Level 3 fields will be deprecated If you send Level 3 or line item data, you must:
a. Use new field names (e.g., order_reference, shipping_to_postal_code)
b. Provide structured line items, including product_name and Tax details.
What You Need to Do:
See our bulletin Stripe Payment Intent in our Major Changes guide for more detail on the updated you have to make.
Spreedly has added support for the new ConnexPay gateway. For more details, please refer to the gateway guide.
Spreedly now supports Google Pay for transactions on dLocal gateway.
For more information, please refer the gateway guide.
Spreedly now supports Store functionality for transactions on Nuvei (formerly SafeCharge) gateway.
For more information, please refer the gateway fact sheet.
Spreedly now supports Partial Capture and Unstore functionalities for transactions on Worldpay gateway. For more information, please refer the gateway fact sheet.
Spreedly has added support for the new Bambora North America REST gateway. For more details, please refer the gateway guide. Please note that the existing Bambora North America gateway (Soap) is currently in maintenance mode. While existing features remain supported, all new enhancements are being developed exclusively for the Bambora North America REST gateway. We recommend migrating to the REST guide to access the latest capabilities.
Spreedly supports idempotent requests via the idempotency_key field to prevent duplicate processing of the same transaction on the Vantiv Express (formerly Element) gateway.
For more details, please refer the gateway guide.
Spreedly now supports the wallet_id, wallet_transaction_id, and wallet_transaction_type gateway specific fields for the IPG gateway. For more information, please see the gateway guide.
Spreedly now supports the sender_postal_code gateway specific field for the Shift4 (formerly Credorax) gateway. For more information, please see the gateway guide.