Nov. 25 - Dec. 6 Updates
- Apple Pay on Braintree: Now available when a store doesn't have a custom checkout domain
- PayPal: Ability to set translation on checkout for "Click here"
- Apple Pay: Ability to set translation on checkout for "Payment Options"
- Apple Pay on Stripe: Fixed a bug when using Apple Pay during checkout
Products API
- New create (POST) product endpoint
- New update (PUT) product endpoint
- New delete (DELETE) product endpoint
Fixed bug that the
order_interval_unit
was being retrieved from the ruleset instead of the product. It is now fixed to retrieve theorder_interval_unit
from the product record.
Checkout API
- Fixed bug that the discount code was not being displayed on the Checkout UI when the checkout was created using the Checkout API and then the customer redirected to the Checkout UI to complete the checkout. Now the discount code is displayed when applied via the Checkout API.
Subscriptions API
Fixed bug that caused charge regeneration to be delayed when cancelling subscriptions via the
POST /subscriptions/
endpoint. Now charge regeneration is triggered immediately when cancelling a subscription unless the/cancel commit_update
is set to false.
- Updated
shipping_countries
response to return all countries instead of being defaulted to a limit of 50 countries and paginated Fixed a bug that was setting the
expire_after_specific_number_of_charges
field to null on new subscriptions that were added through the Theme Engine customer portal when the default value for the product was an integer (e.g. 6, 12). Now new subscriptions will inherit the default value from the product record. To implement this functionality you'll need to generate a new theme or update your existingsubscription_new.html
file (see image below for updates).{% if subscription_defaults.expire_after_specific_number_of_charges %}
{% endif %}
Added ability to delay a subscription as a retention strategy when a customer is cancelling their subscription. To implement this functionality you'll need to generate a new theme or update your existing
subscription_retention_strategy.html
file (see image below for updates).