Quantum Art Releases QP7.Payment

This is a reprint of a post from the other blog:

Who said content management is not about revenue generation? QP7.Payment is a transaction capture solution designed to help governments and corporation centralize disparate electronic revenue management functions. For example, say you are a government with 60 different departments. Each of the departments has a specific business process and product categories for generating revenue (Treasurer collects property taxes; Clerk's office sells records, both certified and not; Planning and Zoning issues permits; Parks allows you to reserve facilities; etc.).

Now, integrating all of these items into a single catalog is a major undertaking. Plus, the checkout process will be different for every department. In this situation, does it make any sense to do the integration on the product or the content level? We didn't think so either and architected QP7.Payment to be a web-services solution that integrates these disparate revenue generation sources on the transaction level, thus becoming a transaction capture solution.

The government process I described is just an example. It's actually based on Bernalillo County (NM) that already implemented QP7.Payment. But same applies to sales of, say, digital assets, or an actual product inventory.

QP7.Payment is, of course, based on QP7. All the nice things about the platform still apply.

END REPRINT