Spreedly now supports Third-Party 3DS2 Authentication for Verify Transactions on Stripe Payment Intents.
For more information on Third-Party 3DS2, please see the Third Party 3DS2 Guide.
Spreedly now supports Third-Party 3DS2 Authentication for Verify Transactions on Stripe Payment Intents.
For more information on Third-Party 3DS2, please see the Third Party 3DS2 Guide.
Spreedly now supports SPEI, Boleto Bancario, Matrix, Khipu as a payment method option on the PayU Latam gateway.
For more information on using the new payment method, review the documentation.
Spreedly now supports SPEI, Boleto Bancario, Nequi, Khipu, Yape as a payment method option on the dLocal gateway.
For more information on using the new payment method, review the documentation.
Spreedly now supports the shopper_interaction gateway specific response field for the Adyen gateway. For more information, please see the gateway guide.
Spreedly has expanded viewing capabilities in app.spreedly.com to support listing payment methods within an environment, listing payment method events within an environment, and global search for a payment method token.
Spreedly now provides the following values in transaction responses utilizing Network Tokens under the network_tokenization or network_token fields :
token_reference,
token_first_six_digits, token_last_four_digits, token_created_at, token_updated_at.
For more information on Network Tokens please view the NT guide.
Spreedly has updated the public PGP key used for payment method migrations. For more information, please see the guide to Importing Payment Methods
Spreedly now supports the user_value_1, user_value_2, user_value_3, user_value_4, and user_value_5 gateway specific fields for the Ebanx gateway. For more information, please see the gateway guide.
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.