Spreedly now supports the add_subscription, source_transaction_id, plan_id, and start_date gateway specific fields for the NMI gateway. For more information, please see the gateway guide.

Spreedly has introduced a maximum limit of 200 inquiry request per transaction. This change ensures platform stability and prevents excessive updates on a single transaction.

Spreedly now supports Mercado Pago as a payment method option on the MercadoPago gateway.

For information on how to utilize the new payment method, review the documentation.

Spreedly added support for additional PayWay error codes, including capturing and returning processorResultCode and processorErrorMessage for improved decline diagnostics. Mapped paywayMessage to the generic Message field to provide clearer, customer-facing error details.

Spreedly now supports PIX, PagoFacil,RapiPago, CobroExpress, Efecty, WebPay, PSE, PagoEfectivo, Oxxo, SevenEleven & PagosFarmacias as a payment method options on the PayU Latam gateway.

For information on how to utilize the new payment method, review the documentation.

Spreedly now supports Efecty,** PSE**, WebPay, PagoEfectivo, RapiPago, Mercado Pago, PagoFacil, Oxxo & Pix Automatico as a payment method options on the dLocal gateway.

For information on how to utilize the new payment method, review the documentation.

Spreedly now supports the promotion_id gateway specific field for the Payu Latam  gateway. For more information, please see the gateway guide.

Spreedly now supports NuPay and NuPay Recurrent as a payment method options on the Ebanx gateway. Spreedly provides the option for separate and combined enrollments and payments.

For information on how to utilize the new payment method, review the documentation.

Spreedly now supports the tax_exempt, number_of_payments, line_item_total_with_tax, and line_item_detail_indicator level 3 gateway specific fields for the Vantiv eCommerce gateway. For more information, please see the gateway guide.

Please refer to our prior notifications via email and details provided in our migration guide. Certain non-gateway transaction types (such as payment method lifecycle updates, fraud checks, and SCA-related actions) are now returned as events instead of transactions. These records will begin no longer appearing in the /transactions or /payment_methods/{token}/transactions endpoints.