Spreedly has fixed the error pattern for failed attempts to create a Sca Provider or Protection Provider. Please see our API reference for details on the error response syntax for failures to create a SCA Provider or Protection Provider.
Spreedly now supports the return_url gateway specific field for the SumUp gateway. For more information, please see the gateway guide.
Spreedly has fixed the error pattern for attempted updates on redacted gateways; previously, the gateway update request would process but the gateway would remain redacted and unusable. Now, Spreedly will return a 422 when an update request is made for a gateway that has been redacted.
Spreedly now supports the recurring_adv_code gateway specific field for the Orbital gateway. For more information, please see the gateway guide.
Spreedly will map the PaywayMessage field from Payway to the Message field in Spreedly. Additionally, for the specific Paywayresultcode 5012, Spreedly APIs will reference the ProcessorResultCode field in the response to provide more detailed error information.
Spreedly has added support for the following 15 new card types to our platform: Tarjeta Única (50478089), Consumax (603416), Tarjeta Fértil (50478050), Favacard (504408), Elebar (504777), Tarjeta Axis (639281), Tarjeta Plan Platino (603702), Tarjeta Fiel (504906), Copeplus (627620), Tarjeta Credimas (504520), Tarjeta Local (605827), Tarjeta Sucredito (621978), Sidecreer (504962), Cliper (589955), Centrocard (627697).
These new card types (and BINs) will now be accepted for tokenization and passing our validation checks for use in your Spreedly vault. However, not all gateways will accept these new card types and you could experience rejections from the processors. Please contact your gateway for information regarding their support and contact Spreedly Support for any questions regarding our update.
You will find these added to our supported payment methods guide.
Spreedly no longer supports the JSONP media type across any endpoints in the Core Transactional API. Requests attempting to use JSONP will return an error. Please see our response codes for more details.
Spreedly now uses the latest Airwallex gateway version dated 2025-09-30. This version will be visible in transaction transcripts via the X-Api-Version header.
Spreedly now supports the reference_transaction_id gateway specific field for the Merchant Warrior gateway. For more information, please see the gateway guide.
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.