Community
Participate
Working Groups
We would like to propose an open, light-weight API to integrate payment services with the Marketplace Client, enabling shop or payment service providers to add purchasing options and users to purchase tools directly from within the MPC. The idea is to extend the Marketplace Client (MPC) to be able to show a Buy button and basic pricing information. An open payment API would act as a bridge between the Marketplace Client and 3rd-party payment implementations. We chose a client-side solution instead of proposing to extend the (closed-source) Marketplace server, because the Eclipse Foundation itself does not have the resources for and can’t take the legal and financial risks of operating an international "Eclipse shop" for all Eclipse vendors and users. The API we propose is kept purposefully leight-weight and simple. An MPC payment service manages a list of payment modules capable of integrating open or proprietary payment solutions provided by plug-ins. Implementation effort for adopters is kept down to one simple interface offering the basic interaction methods with a shopping cart/payment system: public interface PaymentModule { PaymentItem offer(String nodeId, IProgressMonitor monitor); IStatus purchase(PaymentItem item, IProgressMonitor monitor, IAdaptable context); IStatus remove(PaymentItem item, IProgressMonitor monitor, IAdaptable context); IStatus checkout(IProgressMonitor monitor, IAdaptable context); IStatus cancel(IProgressMonitor monitor, IAdaptable context); PaymentTransaction getSession(); List<PaymentTransaction> getPurchases(); } New payment modules can be discovered by the payment service on-demand for catalog entries that no installed module is found for. This could be based on P2 discovery using an URL-based discovery scheme with a list of discovery locations rolled out with the MPC. At a later time, we also plan to include an open license configuration interface that can be implemented by commercial tools to integrate their license management system with the payment API to support zero-configuration license setup. For more details about the proposed payment API implementation check out our preliminary codebase at GitHub: https://github.com/YattaSolutions/epp.mpc I've written more extensively about user and ecosystem benefits and our Marketplace vision here: http://www.yatta.de/news/eclipse-marketplace-payment/ We are planning to make our own payment options available to all Eclipse vendors. We have talked with many different Eclipse Members and with the Foundation itself in order to cover all requirements and will try to meet all your requirements, too.
+1 I consider this a very helpful addition to the Eclipse eco system. This will allow a lot of companies/people to offer plug-ins with a reasonable cost overhead.
To get started with the contribution and start the ddiscussion on the contribution process as discussed with Ian on the phone, I've put up the code on Gerrit here: https://git.eclipse.org/r/#/c/15696/
Carsten, There are a number of things I would like to see happen before we accept the code: 1) We need to have test code available and a test service provider 2) I would prefer to see the service provider discovery controlled by the server as opposed to the current client side discovery, so I think we need to have this discussion on the pros and cons. 3) Can you please document the security model you have implemented to ensure things like man in the middle attacks can't happen. 4) I'd like to see documentation on how to setup a service provider. I'd also like to get some people reviewing the code. Thank you very much for pushing this forward. I think it will be a great addition to MPC.
+1 for a payment service in the Marketplace client.
+1 I think it would be great to have something like this in place. And I share Ian's concerns.
I've taken the opportunity to update our code on GitHub[1] to the latest version from our running pilot projects. I'll update the Gerrit contribution as soon as we have finished moving to the latest Mars version of MPC. The current version is still based on Luna. [1] https://github.com/YattaSolutions/epp.mpc
+1 Awesome feature!
+1 yes, this would be great!
+1 for this feature
+1 Great idea! Would love to see something like that.
