Software license protection and e-commerce integration are crucial components for software developers in today’s digital landscape. As the demand for software products continues to surge, integrating e-commerce solutions allows developers to efficiently sell their software online. This not only streamlines the purchasing process for customers but also ensures that products are protected and used only by authorized users. For developers, understanding the significance of these elements is essential in maximizing revenue and safeguarding their intellectual property.
There are various platforms that facilitate e-commerce integration, including Stripe, WooCommerce, and FastSpring. These platforms empower developers to create a professional online store with relative ease, allowing them to list their products attractively, manage inventory, and process payments securely. Moreover, many of these platforms come equipped with built-in tools for license key generation and validation, which are essential for protecting software from unauthorized use. By leveraging these capabilities, developers can focus more on creating quality software while leaving the complexities of e-commerce management to these platforms.
Upon purchasing a software product, the customer is provided with a unique license key or activation code. This key is vital as it enables the activation of the software and is usually tied to the customer’s email address or a specific hardware configuration. This practice not only ensures that the software is used legitimately but also allows developers to track software usage, which can be invaluable for future updates and customer support.
Typically, the license key or activation code is delivered to the user via email or displayed on the order confirmation page after the purchase is complete. This immediate delivery helps to enhance user experience, allowing customers to begin using the software as soon as they make a purchase. After receiving the key, the user is required to enter it into the software during the installation process to activate it. The software, upon receiving the key, will authenticate it by connecting to the developer’s license server. Once validated, the software becomes fully operational, providing the user with access to its features.
Implementing software license protection offers numerous benefits to software developers. One of the primary advantages is the prevention of software piracy, which is a significant concern in the digital marketplace. By ensuring that only authorized users have access to the software, developers can safeguard their investments and reduce revenue losses. Furthermore, license protection allows for effective tracking of the number of users who have activated the software. This data can be instrumental in shaping marketing strategies and understanding customer demographics. Another important aspect is the ability to revoke licenses if they are found to be in violation of usage terms, thus maintaining control over software distribution.
On the flip side, e-commerce integration brings a host of advantages for developers. It provides a platform to reach a global audience, allowing developers to sell their software products without geographical constraints. This broader reach can lead to increased sales and brand recognition. Additionally, e-commerce integration simplifies the purchasing process for customers. They can easily browse the software, read reviews, and make a purchase from the comfort of their homes, enhancing overall customer satisfaction. The automation of license key generation and validation not only saves time but also reduces the potential for human error, making the entire process smoother and more efficient for both developers and customers.
In conclusion, the interplay between software license protection and e-commerce integration is vital for the success of software developers. These elements combine to offer a secure, efficient, and user-friendly environment for selling and protecting software products. Developers who utilize e-commerce platforms with built-in license key management tools can effectively safeguard their creations while streamlining the purchasing process for their customers. As the digital landscape continues to evolve, adapting to these essentials will empower developers to thrive in a competitive marketplace.
Soraco’s Quick License Manager is integrated with several e-commerce platforms. For more information about Quick License Manager, visit our website at https://soraco.co.
Moreover, integrating customer relationship management (CRM) tools with e-commerce platforms can significantly enhance customer interaction. By tracking customer purchases and usage patterns, developers can tailor marketing efforts, offer personalized promotions, and ultimately build strong relationships with their user base. This approach not only fosters loyalty but also encourages repeat purchases and ongoing engagement with the software.
Lastly, it is essential for developers to stay informed about technological advancements and market trends. The integration of artificial intelligence (AI) into e-commerce solutions can further optimize the sales process, allowing for better customer personalization and improved fraud detection. By embracing these innovations, developers can position themselves at the forefront of the industry, ensuring their products remain competitive in an ever-evolving marketplace.
Another example can be seen in the gaming industry, where developers often implement strict license protection measures. By utilizing ecommerce platforms, game developers can sell their titles globally and ensure that each purchase comes with a valid license key. This not only curbs piracy but also helps in managing user access, allowing developers to provide updates and support based on the number of legitimate users.
For instance, consider a developer who creates a productivity app. By leveraging WooCommerce for e-commerce integration, they can set up a storefront where users can easily navigate and purchase the app. As soon as a user completes the transaction, they receive an email with their unique license key, enabling them to start using the app immediately. This streamlined process not only enhances user satisfaction but also encourages positive reviews and referrals.
Subscription licensing is a method used by software developers to provide access to their products on a recurring basis, typically on a monthly or annual basis. This type of licensing is becoming increasingly popular as it allows developers to generate recurring revenue and provide their customers with the flexibility to use the software as long as they are paying for it.
With subscription licensing, users can purchase access to the software for a specific period of time, such as a month or a year. Once the subscription period ends, the user will need to renew their subscription to continue using the software. The subscription can be renewed automatically, or the user will have to manually renew it.
One of the main benefits of subscription licensing for software developers is the ability to generate recurring revenue. Instead of one-time payments for software, developers can receive regular payments from customers who are continuously using their products. This can provide a more stable source of income for the developer, allowing them to invest in new features and updates for the software.
Another benefit is that subscription licensing can provide users with more flexibility in terms of how they use the software. Instead of committing to a long-term license, users can choose to subscribe to the software on a month-to-month or annual basis. This allows users to try the software before committing to a long-term license, or to cancel their subscription if they no longer need the software. Additionally, users can upgrade to the latest version of the products at no additional cost.
However, subscription licensing also has its drawbacks. For one, users may feel like they are being nickeled and dimed by having to pay for the software on a recurring basis. Additionally, if a user’s subscription lapses, they will lose access to the software and their work until they renew the subscription.
In conclusion, subscription licensing is a method that offers benefits for both software developers and users. It allows developers to generate recurring revenue and provides users with more flexibility in terms of how they use the software. However, it’s important for developers to communicate the terms of the subscription clearly to the users, and also to offer a clear path to cancel the subscription if they no longer need the software. Additionally, developers should ensure that the software still provides value to the users even if they are paying on a recurring basis.
Soraco’s Quick License Manager supports both subscription licenses. For more information about Quick License Manager, visit our website at https://soraco.co.
Cloud-based floating licenses are a method used by software developers to provide access to their products on a shared, pay-per-use basis. This type of licensing is becoming increasingly popular as it allows developers to provide their customers with the flexibility to use the software when and where they need it, while also reducing the cost of managing and distributing licenses.
In a cloud-based floating license model, a pool of licenses is maintained in the cloud and is shared among a group of users. Each time a user wants to use the software, they check out a license from the cloud-based license server. When the user is finished using the software, the license is returned to the pool for others to use.
One of the main benefits of cloud-based floating licenses is the flexibility they provide. Users can access the software from anywhere, as long as they have an internet connection. This eliminates the need for users to be physically present in a specific location to access the software, making it more convenient for users who travel or work remotely.
Another benefit is the cost-effectiveness of the model. With cloud-based floating licenses, developers only need to pay for the licenses that are in use, rather than purchasing a license for each user. This can help to reduce costs for both developers and users, especially in situations where the software is only needed occasionally.
However, cloud-based floating licenses also have their drawbacks. For one, the software may require an internet connection to access the license server, which can be a problem for users with poor internet connectivity or no internet access. Additionally, if the license server is down, users will not be able to access the software, which can be disruptive to their work.
In conclusion, cloud-based floating licenses are a flexible and cost-effective method for providing access to software products. They allow users to access the software from anywhere and provide the ability to pay-per-use. However, it’s important for developers to ensure that the license server is highly available and accessible, to minimize the disruption caused to users in case of an outage. Additionally, developers should also offer different pricing options, such as annual or perpetual licenses, to cater to users who prefer to have a permanent license rather than a subscription-based one.
Soraco’s Quick License Manager supports cloud-based floating licenses. For more information about Quick License Manager, visit our website at https://soraco.co.
Software activation by email address is a common method used by software developers and publishers to validate and authorize the use of their products. This process involves the user providing their email address during the installation of the software, and then receiving a unique activation code via email, which is used to activate and unlock the full functionality of the software.
One of the main advantages of software activation by email address is that it allows for easy and convenient activation for the user. Rather than having to enter a long and complex activation code, the user simply needs to provide their email address, which is something they already have on hand.
Another advantage of software activation by email address is that it allows for easy tracking and management of software licenses. By associating the software with a specific email address, developers and publishers can track and manage the use of the software, and can easily revoke or deactivate the software if necessary.
However, there are also some potential downsides to software activation by email address. One concern is that it may be less secure than other methods of software activation, as email addresses could be hacked by malicious actors. Additionally, if a user loses access to the email address associated with the software, they may be unable to reactivate or transfer the license to a new computer.
To mitigate these concerns, software developers and publishers can implement additional security measures, such as requiring the user to confirm the activation code via a second email or through a secure website. They can also provide clear instructions and support for users who have lost access to the email address associated with the software.
In conclusion, software activation by email address is a convenient and effective method for validating and authorizing the use of software. However, it is important for developers and publishers to consider the potential security risks and provide clear instructions and support for users. By implementing additional security measures and providing clear instructions, software activation by email address can be a reliable way to protect software licenses and ensure the integrity of the software.
Soraco’s Quick License Manager supports software activation by email. For more information about Quick License Manager, visit our website at https://soraco.co.
API keys are commonly used in software applications to authenticate and authorize access to external APIs. However, if an API key is embedded in the software application, it can potentially be discovered and misused by unauthorized parties. Here are a few methods for protecting an API key embedded in a software application:
Obfuscation: One way to protect an API key embedded in a software application is through obfuscation. This can include using code obfuscation techniques to make it difficult for unauthorized parties to reverse-engineer the software and discover the API key.
Encryption: Another way to protect an API key embedded in a software application is through encryption. This can include encrypting the API key and storing it in a secure location, and then decrypting it only when it is needed for use in the software application.
Key rotation: Regularly rotating the API key by generating new keys and phasing out old ones can limit the window of opportunity for an attacker to misuse a key if it is compromised.
Limit access: Limit the number of people who have access to the keys and the encryption software, and limit the number of systems that have access to the keys.
IP whitelisting: Limit the IP addresses that are allowed to make requests using the key, this way only authorized systems will be able to use the key.
Monitor usage: Monitor the usage of the key and set up alerts for unusual activity or usage patterns, this way you will be able to detect any misuse of the key.
Include a security layer: include a security layer in your application that verifies the authenticity of the key and the source of the request before allowing access to the API.
In conclusion, protecting an API key embedded in a software application requires a combination of technical and organizational measures. By using obfuscation, encryption, key rotation, limiting access, IP whitelisting, monitoring usage, and adding a security layer, software developers and organizations can help to protect the security of their API keys and the data accessed through the API.
For more information about Quick License Manager, visit our website at https://soraco.co.
Software license protection using online activation is a method used by software developers to ensure that their products are only used by authorized users. This method involves the use of an online activation process, in which a user must enter a unique activation code or license key to unlock and use the software.
The online activation process typically begins when a user purchases a software product. The user will receive an activation code or license key, which they must enter into the software to activate it. The activation code or license key is unique to the user and is generated using a combination of the user’s information and a secret algorithm.
Once the activation code or license key is entered, the software will connect to the developer’s activation server to verify the code. If the code is valid, the software will be unlocked and the user will be able to use it. If the code is not valid, the software will remain locked and the user will not be able to use it.
Online activation provides several benefits for software developers. First, it helps to prevent piracy by ensuring that only authorized users can use the software. Second, it allows developers to track the number of users who have activated the software, which can be useful for sales and marketing purposes. Third, it allows developers to revoke a license if it is being used on too many machines.
However, online activation also has its drawbacks. For one, it requires an internet connection to verify the activation code, which can be a problem for users who are not connected to the internet or who have a poor internet connection. Additionally, some users may find the activation process to be a nuisance, especially if they need to activate the software on multiple machines.
In conclusion, software license protection using online activation is an effective method for preventing piracy and tracking the use of software products. However, it does have some drawbacks, and developers must weigh the pros and cons before implementing this method.
Soraco’s Quick License Manager supports online and offline activation. For more information about Quick License Manager, visit our website at https://soraco.co.
Two common types of software licensing are subscription and perpetual. Each of these licensing models has its own set of benefits and drawbacks, and it is important for customers to understand the differences between the two in order to make an informed decision.
Perpetual licenses are the traditional model of software licensing, where customers purchase a license to use the software indefinitely. This means that once the customer has purchased the license, they have the right to use the software as long as they want, without the need to renew or pay additional fees. This model is best suited for customers who want to use the software for a long period of time and don’t want to worry about renewing their licenses.
Subscription licenses, on the other hand, are a newer model of software licensing, where customers pay a recurring fee (usually on a monthly or annual basis) in order to access and use the software. This means that customers must renew their licenses in order to continue using the software. This model is best suited for customers who want the flexibility of using the software for a shorter period of time or want access to the latest features and updates without making a large upfront investment.
One of the main benefits of subscription licenses is that customers have access to the latest features and updates without having to pay for a new version of the software. This is because the cost of the subscription fee includes access to all updates and new versions of the software. This can be a big advantage for customers who want to stay current with the latest technology and features.
Another benefit of subscription licenses is that they can be more cost-effective in the long run. This is because customers only pay for the software when they are using it, rather than having to pay a large upfront cost for a perpetual license. This can be especially beneficial for customers who may not need to use the software all the time, such as businesses that only need the software for specific projects or during specific periods.
However, perpetual licenses also have their own set of benefits. One of the main benefits is that customers own the license, which means they can use the software indefinitely without the need to pay recurring fees. This can be beneficial for customers who have a long-term need for the software, such as businesses that rely on the software for their daily operations.
Another benefit of perpetual licenses is that they can be less disruptive to customers’ workflows. Because customers own the license, they don’t have to worry about renewing their licenses or losing access to the software if they forget to pay their subscription fees.
In conclusion, both subscription and perpetual licenses have their own set of benefits and drawbacks. Customers should consider their specific needs and use case when choosing a licensing model, and weigh the benefits of each model before making a decision. Subscription licenses offer flexibility, access to latest features and updates, and can be more cost-effective in the long run while perpetual licenses offer the ownership of the license and less disruption to the customer’s workflow.
Soraco’s Quick License Manager supports both perpetual and subscription licenses. Additionally, QLM supports a perpetual license with a software maintenance plan that entitles customers to software upgrades and technical support. For more information about Quick License Manager, visit our website at https://soraco.co.
Yes, iterative releases, you read it right. We always hear of iterative development, agile process, etc. These methodologies describe processes for iterativedevelopment of a software. While these processes describe different approaches to developing software, they all typically assume that a software major release comes packed with new features that the team has worked on for an extended period of time.
Now consider the following typical release cycles: you released version 1.0 of your product; you then released version 1.1 with mainly bug fixes; you may also have released version 1.2 with some minor features.
While working on these minor releases, you have gathered your requirements for version 2.0 from different sources and are ready to start design and development for your next major release. Your initial estimate predicts a 6 to 9 months development cycle. Taking into account testing, beta cycles, etc., your next release should be ready in about a year.
Depending on the methodology you adopted, your requirements are broken down into stories, use cases or just milestones with several iterations that are typically 2 to 4 weeks long. For the purpose of this article, I will refer to these are feature sets.
Now consider this approach. You work on the first feature set, design it, develop it and test it. You then package it as version 2.0 and release it to customers. You continue through your development iterations and at each iteration, you release a minor version 2.x.
The main benefit of this approach is that you avoid the 1 year release cycle which is detrimental in many ways. Why you may ask?
1. First, your are forcing your customers to wait until all your features are developed to start benefiting from them. Some of the new features may be critical to retain customers and you run the risk of losing them.
2. For new customers, if you are lacking critical features that will only be available in a year, you have lost them.
3. A 1 year release cycle is quite long. The productivity of developers is usually at its peak when the feature they are developing is planned for immediate release to customers.
4. Because completed features will be available to customers at every iteration, issues will inevitably be reported soon after release forcing the developers to fix these issues promptly. This will ensure a continuous bug fixing process as opposed to leaving all bugs until the end which leads to a highly unstable product.
We believe this approach is ideal for small development teams (1-3 people) working on relatively small projects. For larger projects that involve larger teams, the logistics behind a release are too important and expensive to repeat at every iteration. Process automation is key in making this a success. For this approach to work effectively, you would ideally have a fully automated build process, automated unit tests and system tests.
As bugs are found, you may be forced to release many versions of your product and run the risk of having too many versions out there. This can become an issue when dealing with backward compatibility.
Finally, this approach will require customer education. Customers will get a shock when you release a new major version of your product with just a few features. They will ask questions. You need to be prepared to answer them and preferably, prepare them by explaining your process.
As you guessed, customer education is what this blog was intended for as we prepare for the next release of Quick License Manager!
When selling licenses to enterprise customers with potentially thousands of computers, having each user manually activate each license is not a viable solution.
There are several ways to ease the burden for large companies while at the same time providing an adequate level of protection for your application.
The first approach involves providing a special license key that does not require activation on every single node. At the time of purchase, the customer receives a special activation key. Typically, when an activation key is activated, a computer bound key is generated and returned to the client. In this case, instead of generating a computer bound key, a generic key is created that can be reused on other system. With this approach, the customer needs to activate the license on one computer and then reuse the generated key on all other computers. The generated key could be located in a central location that your application is aware of. The first time your application is launched, it would retrieve the generic key from the central location and validate it.
With this approach the generated license key can be used to install any number of systems so this is suited for unlimited licenses.
Another approach involves binding the license key to the company’s domain name. At the time of purchase, the customer receives a standard activation key. When the first system activates the license, a computer key bound the company’s domain name is generated. This computer key can then be used on any computer within that domain. As with the approach above, your application would need to pick up this computer key from a central location such as a share or a database and then validate it when the application starts up.
With this approach the generated license key can be used to install your application on any number of systems within the specified domain so this is suited for unlimited Site licenses.
Yet another approach involves a fully automated way of activating license keys and binding them to each specific computer. At the time of purchase, the customer receives a standard activation key with the number of seats embedded in the license key. The activation key would then be stored in a central location on the customer’s network such as on a share or a database. The first time your application is launched, it would retrieve the activation key from the central location and automatically activate it. The activation process generates a computer bound license key that would then be stored on the client system. Subsequently, whenever your application is launched, your retrieve the computer key from the client and validate it.
Customers are demanding. The ability for your software to automatically update itself when a new version is released is now a ubiquitous feature that is expected of professional software applications. Obviously, getting new versions of your application is tightly coupled with your software license model. Typically, not all users are allowed to upgrade for free! Therefore, integration of a “check for updates” feature with your licensing software is a must.
A license management solution must provide answers to the following two questions:
2. Is this customer allowed to upgrade to the latest version?
You sell a software product and you want to protect it against piracy by using license keys. You know you need to make sure users cannot reuse a license key on any computer. Now the tough decision: what unique identifier do you use to bind the license key to?
The answer to this question depends on several factors. Let’s review some alternatives (this is not an exhaustive list):
Given these choices, which option to pick depends on the following factors:
If your target market is the enterprise market, small, medium or large, we recommend binding the license to the Computer Name. In medium and large companies, software piracy is not prevalent. In addition, most companies run a Domain Controller that manages all computers in the organization. It is not possible in this context to have two computers with the same name. It may not be practical either for a company to keep computers outside of the domain infrastructure to bypass licensing. Finally, corporate customers can get quickly frustrated if they start experiencing licensing issues after hardware changes. You need to balance security with customer satisfaction.
If your target market is the consumer market, then the decision is based on these factors:
If you are a one man show or have a small support organization that is already busy on application related issues, once again, we recommend the Computer Name approach. Dealing with license key issues is not your primary business and you certainly do not want to spend a good portion of your time figuring out what hardware change broke the license.
If your software is a prime target for hackers, then consider the CPU ID or Hard Disk Serial Number with the possibility of reverting to a Computer Name if these identifiers cannot be retrieved.
If your software is affordable, then it may be less of a target for hackers. Consumers do not mind paying a low price for a product that meets their needs. Piracy is most common with highly priced products.
Whichever solution you end up picking, keep in mind that someone, somewhere will always try to hack your software and get a free copy. Is it worth your while? Is it worth implementing a very strict license policy and potentially alienate paying customers to protect against a few hackers? It’s a decision you need to think about seriously as it that has a direct impact on your bottom line, one way or another.
One of the main factors of a company’s success is revenue. Some would argue that it is the only factor but that’s another debate. When you sell software applications, as with any other business, ensuring steady revenue is a key factor to growth and stability. Learn how you can avoid fluctuating revenue by implementing a Maintenance Plan for your software application.
When you manage to sell your software to a customer, you have succeeded, but only partially. A customer, if happy with your product, will be interested in continuing to use your product for several years. If like most software companies, you continuously improve the product and release new minor and major upgrades, you have the potential to turn your current customers into buyers again by offering a Yearly Maintenance Plan option.
If you ever heard the term online activation, software activation or product activation and wondered what it meant, read the rest of this blog.
Most of us have already been exposed to online activation, most likely when you installed a Microsoft Office product. Microsoft was one of the early adopters of online activation. Due to online activation, Microsoft was able to effectively stop the piracy of its Office product line in the consumer market (it’s a different story for the Enterprise market).
In the early days of licensing, when you purchased a product, you received a license key that enabled you to run the software. The license key was generic, i.e. not tied to a specific computer. This meant that users were able to install your application on any number of computers and reuse the same license key over and over. With the advent of the internet, generic license keys were published on the internet therefore allowing anyone to install your application.
With software activation, when a customer purchases a software product, they receive an activation key. The activation key does not enable the application to run. When the user enters an activation key in the application, the application connects to a license server and sends the activation key along with one or several unique computer identifiers. The license server validates the key and generates a new ID, sometimes called Product ID or Computer Key and sends it back to the application. This Computer Key is used subsequently as the license key that will be validated at application start-up. The Computer Key is bound to the computer identifiers that were sent to the license server. If a user tries to use this Computer Key on another computer, it will fail.
When users have an internet connection, the activation process can be fully automated thus making the user experience seamless and friendly. In some instances, users may not have an internet connection so access to the license server is not possible. In these cases, offline activation is possible. Offline activation is typically done by asking the user to send his activation key along with the computer identifiers (the application should display to the user the computer identifiers) by fax, phone or email. Upon receipt of this information, the vendor generates a Computer Key on the customer’s behalf and sends it back to him. The customer then enters the Computer Key and enables the software to run.
Another aspect to consider when implementing software activation is license transfers. It is quite common that companies will need to uninstall an application from one computer and reinstall it on another. There are 2 general cases to consider:
(a) the original computer is still operational or
(b) the original computer is not operational.
When the computer where the software was initially installed is still functional, the recommended approach is to automatically de-activate (release) the activated license when the software is uninstalled. Therefore, the setup program that uninstalls the application should automatically connect to the license server and release the license that was activated. This allows the user to simply install the application on another system and activate it. If the original system where the software was installed is not functional, then there are two choices: either the vendor allows the customer to de-activate the original license by providing them with such an option in the application or the customer will need to contact the vendor to request a license transfer. The choice here clearly depends on the type of customer and the type of product you are selling.
Product activation is an effective way to prevent software piracy. It is used by many software companies today and has become the standard way for protecting the intellectual property of the vendor.
We decided to write this blog following some requests we received to provide full source of our software. It appears that some companies offer this option to provide the security that should the vendor go out of business, then they can always carry on using the software.
While this may sound great, we believe that in most cases, it is a myth and a venue that is rarely beneficial to the customer and here are some reasons why:
Most enterprise software products have been developed over years by multiple developers, have hundreds of thousands of lines of code and are typically not well documented. Getting your hands on a huge amount of code without any guidance is certainly not going to be the most productive use of your time. It will drag your developer resources into an area you really did not have time for, nor allocated a budget for.
The main reason you decided to purchase a product in the first place was to save time and focus on your core business. That premise does not change if a vendor has ended its support for a product. You still want to focus on your core business.
In the specific case of license management and security, providing source code to customers also means providing source code to potential hackers who could use the source code to find ways to hack it.
In most cases, even if the vendor has disappeared, you can still use their software for a fair period of time. This is a transition time to plan your next move.
Providing full source code may sound appealing and does give a false sense of security. In reality, if a product you purchased is no longer supported, your best bet is to find a similar product and integrate with it. After all, do you ask for the design specs of your TV when you buy one and then try to fix it yourself when it breaks? You just go and buy a new one. It’s unfortunate for sure but you need to move on as quickly as possible.
Integration of your licensing component with your eCommerce provider is essential to achieving a fully automated sales process. This article describes how integration with FastSpring ensures a seamless purchasing experience for the purchaser as well as the vendor.
As a vendor, you obviously want to protect your software against piracy. You figured out how to generate license keys and validate them in your application with Quick License Manager or any other vendor. This is half of the story. You now need to get the license key to your customer when they purchase the software. You also want to track their order information and tie it to the license key so that you can manage this customer effectively. If you are running a business, small, medium or large, you really want this process to be fully automated so that you focus your time on running your business and not performing manual steps to track and manage your licenses.
Quick License Manager resolves this problem with seamless integration with several leading commerce providers such as Plimus, Regnow, Share-it, Google checkout, Paypal, UltraCart, etc.
Our latest addition to this growling list is FastSpring.
When a customer places an order via FastSpring, the order information filled by the customer during the ordering process is automatically and securely sent to Quick License Manager. Quick License Manager generates a license key and sends it back to FastSpring. The order information along with customer data and license information are automatically stored in the Quick License Manager database. FastSpring then sends a confirmation email to the customer with the license key generated by Quick License manager.
As a vendor, this integration provides an optimal, unified approach to selling your software online. All the relevant information collected during the ordering process is readily available in Quick License Manager. Management of the customer information and license keys can be easily performed using the Quick License Manager Console.