@Sanjeewa, In the free and paid API concept, we need credit card details, cvc numbers, expiry dates and billing address etc.. for the paid APIs. Before subscribing it checks for those information. Actually we do not collect additional data but the 3rd party webapp does the data collection part and it redirects back to complete the subscription process. We are just enabling the capability to extend the workflow process to handle this.
@Roshan, There will be three categories for the APIs as *'Free'*, *'Freemium*' and ' *Commercial'*. If all the tiers are free, it is a 'Free' API If some of the tiers are free and some are paid then it is 'Freemium' If all tiers are paid, then it is a 'Commercial' API No we are not going to deal with payment gateways. It is a customisation part need to be handled by the user. Thanks, Madusanka On Mon, Sep 14, 2015 at 11:46 AM, Sanjeewa Malalgoda <[email protected]> wrote: > @Madusanka, > What does it meant by collect user data. When subscribers signup or > register by admin they are suppose to provide information. > And we may have user data in our side. What do we additionally collect > here? > > Are we calling external billing system to create account there? I think we > can use user provisioning concept here rather collecting information from > user. > We can provision user available in our side to 3rd party using > provisioning APIs available(like JIT). > WDYT? > > Thanks, > sanjeewa > > On Mon, Sep 14, 2015 at 9:48 AM, Madusanka Premaratne <[email protected] > > wrote: > >> Hi All, >> I am going to implement the $subject for WSO2 API manager to enable the >> capability of handling paid APIs. The data flow diagram can be seen as >> follows. >> >> >> >> >> >> As described in the figure above if there are no payment plans set for >> the subscriber the workflow will redirect to third party/inbuilt web page >> to collect those information. If those are already defined it will just >> continue the subscription process. >> >> To fulfil the above task, I am going to change the existing *execute* >> method of *WorkflowExecutor* to handle the redirection process and to >> receive the feedback. After the operation from the webpage/ the required >> details are already collected the webpage will send a response back to >> workflow executer to complete the execution and complete the subscription. >> >> Suggestions and feedbacks are welcome. >> >> Thanks, >> Madusanka >> >> -- >> *Madusanka Premaratne* | Associate Software Engineer >> WSO2, Inc | lean. enterprise. middleware. >> #20, Palm Grove, Colombo 03, Sri Lanka >> Mobile: +94 71 835 70 73| Work: +94 112 145 345 >> Email: [email protected] | Web: www.wso2.com >> >> [image: Facebook] <https://www.facebook.com/maduzanka> [image: Twitter] >> <https://twitter.com/rmmpremaratne> [image: Google Plus] >> <https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub> [image: >> Linkedin] <http://lk.linkedin.com/in/madusanka/> [image: Instagram] >> <http://instagram.com/madusankapremaratne> [image: Skype] >> <http://@rmmpremaratne> >> >> > > > -- > > *Sanjeewa Malalgoda* > WSO2 Inc. > Mobile : +94713068779 > > <http://sanjeewamalalgoda.blogspot.com/>blog > :http://sanjeewamalalgoda.blogspot.com/ > <http://sanjeewamalalgoda.blogspot.com/> > > > -- *Madusanka Premaratne* | Associate Software Engineer WSO2, Inc | lean. enterprise. middleware. #20, Palm Grove, Colombo 03, Sri Lanka Mobile: +94 71 835 70 73| Work: +94 112 145 345 Email: [email protected] | Web: www.wso2.com [image: Facebook] <https://www.facebook.com/maduzanka> [image: Twitter] <https://twitter.com/rmmpremaratne> [image: Google Plus] <https://plus.google.com/u/0/+MadusankaPremaratnemaduz/about/p/pub> [image: Linkedin] <http://lk.linkedin.com/in/madusanka/> [image: Instagram] <http://instagram.com/madusankapremaratne> [image: Skype] <http://@rmmpremaratne>
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
