Paddle changelog vendors.paddle.com

Our new .NET (C#) Windows SDK lets you handle in-app payments, and manage licensing and trials with your users.

It’s the perfect way to provide a great checkout experience and optimize your desktop app for conversion.

To find out more check out our announcement or get set up with the SDK here.

We’ve started to rollout our new checkout today! The new checkout will allow us to provide you with new ways to increase conversions and average order value.

We're making the new checkout available to our sellers gradually via an A/B test with the old one, so you may see it appear on your website.

You don’t need to do anything and your buyer experience will not be affected: the new checkout supports the same implementation and looks and behaves the same way as the old one.

Find out about our plans for the new checkout here. Any questions at all, please get in touch.

We've made it easier for you to give buyers the option to update or cancel a particular subscription.

Simply retrieve update_url or cancel_url using the List API. To find out more, check out the updated doc to see a sample response object.

We're stopping a long-running A/B test of our checkout to start our biggest A/B test yet, focusing on gradually introducing the new checkout we've building from the ground up.

Aside from a few UX improvements along the way, the main objective is to use more modern technologies, making it quicker and easier to add new features in the future.

Over the next few months, we’ll be starting a gradual rollout of an experiment which tests our new checkout against the existing one to ensure a smooth transition.

We'll then begin focusing on improving it, primarily looking at improving conversion rate and average order value to grow your revenue!

To learn more about this change and our plans for the checkout, read our announcement.

We have resolved the order processing slowdown that started earlier today.

New orders are processed straight away as usual. The queue of orders that were slowed down has now been cleared up.

Thank you for your patience!

We are currently experiencing issues with order processing which affect a large number of sellers.

Orders are correctly created and payments are collected, which means this does not impact your revenue.

However the processing of these orders, which include creating licenses and sending confirmation emails to buyers is greatly slowed down. Our post-checkout API, which can be used to display order confirmation details open your website, will not be able to return processed order information in a timely manner. None of the subscription webhooks will be fired.

We are actively working with absolute priority on solving the issue and clearing the queue of orders to process, so that your buyers receive their license or purchase as soon as possible. We will update you as soon as this is resolved.

Our Mac SDK makes it incredibly easy to take payments in-app, use licensing for access control and / or offer trials to your users.

Introducing our new Mac SDK, v4. It's more flexible and customizable, works well with more complex billing or product models, increases anti-piracy protection… And is fully Mojave-compatible (including dark mode)!

To learn more, read our announcement and get started from scratch or migrate from v3.

As of September 3, 2018, we will no longer charge B2B taxes to buyers in South Korea.

These changes will automatically apply in your account for any new transaction with a South Korean company. If they enter a VAT number they will automatically see the price reduced to exclude taxes.

We’ve just released a new support role that is perfect if you want more control over what information your support team can see - for example if you outsource your support function.

The new role (available through the team page) only allows users to see specific transactions by order ID or customer email address, rather than all of them. These users cannot download transaction reports either.

Interested in using restricted support roles for your team? This feature is currently in beta, contact our success team to get access.

We run lots of A/B testing experiments on our Checkout, including recently testing the best way to display the GDPR statements.

Our latest test focused on PayPal. We wanted to figure out how each version of their brand colors performed in terms of both conversion (actual purchases of the software) and engagement (choice made by the buyer to use PayPal).

We didn't see any change in overall conversion, which means both versions of the checkout generated the same overall number of purchases.

Buyers were however 9% less likely to click on the yellow PayPal button (a statistically significant result) - choosing to pay by card instead.

The yellow button is, relatively ironically 🤔, the new branding for PayPal - as a consequence we will keep using the previous blue design as it works better in the context of our checkout.