Update on force_daf Behavior

Previously, merchants had the option to set the force_daf flag within their 3DS2 integrations. Going forward, Spreedly will begin ignoring this flag starting November 2, 2025.

No integration changes required: Customers do not need to modify their current integration in order to accommodate this change.

Impact: While your requests may still include the force_daf flag, Spreedly will no longer honor it.

Reason: This ensures consistency across integrations and removes reliance on DAF behavior in the future.

Action for Merchants:

At this stage, no action is required from your engineering teams. However, be aware that the force_daf flag will be ignored in upcoming releases, and you should plan for this in any future integration updates.

The Spreedly factsheets now indicate gateway support for Partial Capture and Partial Refund within the "Supported Operations" section.

The following gateways now have visibility:

• Checkout
• Cybersource
• dLocal
• Credorax
• Forte
• Paysafe
• Ebanx
• NMI
• Nuvei
• CommerceHub
• Adyen
• Authorize.net
• PayU Latam
• Vantiv eCommerce
• Cybersource REST
• Decidir
• JP Morgan Chase(Orbital)
• PayPal Commerce Platform
• Worldpay
• Airwallex
• HPS
• Bluepay
• Pin Payments
• Global Collect (World line)
• Elavon
• WePay
• Eway Rapid
• Conekta

Spreedly now only supports single IP addresses with a valid format in transaction.ip. Please see the previous changelog notification.

In cases where an IP address is entered incorrectly or with multiple IPs, the following errors may occur:

• multiple_addresses_not_allowed: "Multiple IP addresses are not allowed. Please provide only one valid IP address."
• invalid_format: "Invalid IP address format. Please provide a valid IPv4 or IPv6 address."

Spreedly will be modifying the From address for AU email notifications to [email protected]. Emails are currently sent from [email protected]. Email recipients, subject and content will be unchanged. Customers should update their allow lists if necessary to ensure these notifications continue to be received, however failing to do so will not impact the sending, receiving and processing of the updates themselves in the Account Updater service.

Spreedly now supports the automatic_payment_methods_enabled and automatic_payment_methods_allow_redirects gateway specific fields for the Stripe Payment Intents gateway. For more information, please see the gateway guide.

Spreedly now supports the Shift4 (formerly Credorax), Forte and Heartland Payment Systems gateway types via Composer. See our Composer documentation for more details.

Spreedly has added additional reporting in our application for Protect with new Fraud Management coverage. Updated information can be found in our Reporting documentation. Log in and check it out!

Spreedly now returns the SchemeTransactionId value returned from the IPG gateway in our transaction response as response.network_transaction_id

Spreedly now supports Apple pay on dLocal gateway . For more information, please see the gateway guide.

Guides on https://developer.spreedly.com are now grouped by product area of the Open Payments Platform, simplifying navigation and accessibility of related functionality. Gateway guides and API reference are unchanged.