Many people have commented how fast and easy they’ve found the checkout process on the Stacks4Stacks and ThemeFlood websites; and wanted to know what we use and where they can get it! Since January 2015 we’ve used Paddle to securely handle all checkout purchases of RapidWeaver addons.
The free PaddleBoard stack makes it simple to display purchasing terms and conditions within a modal window, which customers can agree to and then begin the checkout process via Paddle. Any button or link that lets you add custom classes can be used to trigger the checkout process:
Additionally the PaddleBoard stack also provides a simple admin interface. Store owners can use this to login to their Paddle account, or for generating a tracking cookie (which enables display of the PaddleBoard Dashboard):
Once a tracking cookie is setup in the PaddleBoard Admin, extra dashboard buttons are displayed at the top left of a page, therefore giving quick access to edit the product information on Paddle:
Whether you’re managing one or one thousand digital downloads for sale on your website, PaddleBoard will give your purchasing customers a really intuitive buying experience and give you a quick admin interface to manage the store with.
You can add custom properties to the checkout button, supported by the latest Paddle overlay checkout. And of course the major advantage of using Paddle is that it takes care of all the terribly complicated EU VAT regulations, surrounding digital downloads!
But, you are not able to “reinforce contractural agreements with a customer”, as the buyer is not your customer, but the one from Paddle. You have no legal contract with the customer when the customer is using Paddle.
A product (like software) may have a specific set of system requirements that the customer must understand they need, before said product will function. It’s your responsibility to tell the customer what they need and their responsibly to check they meet the minimum system requirements.
It’s not safe to offer refunds on digital downloads - otherwise you just open yourself up to loads of people buying stuff, getting refunds, and continuing to use the product or giving it away to others. Therefore the terms and conditions modal provides the opportunity to state this clearly and divert people towards using free demo’s first.
A customer needs to know who they are buying from and where they can get support from. Otherwise you’re no better than an internet scammer taking the money and running away! It’s good to put this information in the terms and conditions and make it printable.
How do you stop someone simply buying a product and listing it for sale on their website? This is where you need to present your license information clearly, and explain this sort of misuse might not be acceptable.
Digital products you upload to sell through Paddle are not owned by Paddle. Paddle don’t do all the customer support and updates for you, do they? The role of Paddle is as a sales merchant. Therefore it’s perfectly reasonable and justified to have customers agree to a set of terms and conditions, before letting them purchase a digital download from your own website. It’s completely within the rights of the seller to determine how their product is licensed and used. I see dozens of Paddle users do the same and the API even supports the ability for you to add special instructions.
Unfortunately few people ever click the ‘legal’ or ‘terms and conditions’ link in a website footer. So displaying much of this same information at the payment gateway is far more intuitive and avoids many expensive misunderstandings later on. It elevates the overall professionalism of the checkout and significantly improves transparency.
I don’t know if you have downloaded this stack yet, but you will find the terms and conditions modal is very easily turned off in the stack settings, with a simple checkbox toggle (if you do not need it). If you have further questions about the stack or you require modification of it, you can purchase a support ticket here.
I do no currently have a Paddle account, so this question is somewhat academic.
The code, Will, that you have posted in the Setup section on this particular stack page…where does it go?
Create a link or button in your webpage. This link or button can be created using almost any method and can be any style you prefer. Give the button a class attribute and a value that corresponds to the value shown in edit mode. In HTML code, an example button might look something like this:
I am presuming that you have a button that leads to a modal page, and that is where the Paddle stack goes. Is that correct?
Also, the code above indicates the word “pay” and a product number. The image of the stack on an actual page uses the word “buy” and a product number. Are we talking about the same thing?
