Hi Shammi,
How we are going to handle failure cases with this plan.
To handle the failures internally inside APIM , we must configure a webhook
endpoint at the APIM side and must listen to the relevant events which are
triggered from Stripe at the occurrence of such an event. But in this
feature we
Hi,
How we are going to handle failure cases with this plan.
eg:
- for the monthly plan, If the subscriber has not paid or can not be
charged from the CC, Is stripe will send back the call to API M to block
that subscription?
- If the subscriber paid later, how we are going to re-activate
- When
Would a discount pricing model make sense? E.g. after x requests you get a
discount of y%?
And what about adding a QoS aspect: if x requests failed within y duration,
you get a discount of z% for D duration?
Best regards,
Frank
Am Mi., 15. Mai 2019 um 08:21 Uhr schrieb Chamin Dias :
> Hi all
Hi all,
Based on the recent discussions we had, we will be going to implement the
following features from the products POV. Intention of this email is to
give an update on some of the important points.
*A) Model : Charge a fixed price for a given time*
*1. What we need in the product : *
Ability
Hi Cyril,
As for the initial implementation, we plan to provide this integration with
stripe but eventually we hope to provide necessary interfaces to extend.
For now, we focus on delivering a workable solution (APIM + Stripe) for a
normal usage based billing scenario.
Thanks.
On Fri, Apr 5, 201
Hi Rukshan,
Please my answer to your concern below
*I think we can reuse the existing data. Even though we define recording
policy, all the possible data is stored in the analytics DBs regardless of
the recording policy. So we should be able to correlate this recording
policy with stat data and f
On Fri, Apr 5, 2019 at 2:46 PM Silmy Hasan wrote:
> Hi Bhathiya,
>
> Please find my answers for your concerns,
>
> *I think we can do this check at the time they enable monetization for an
> API*.
> +1
>
> *Why do we need separate tables here? Can't we use the existing stats data
> here?*
> We ne
Hi Bhathiya,
Please find my answers for your concerns,
*I think we can do this check at the time they enable monetization for an
API*.
+1
*Why do we need separate tables here? Can't we use the existing stats data
here?*
We need a separate table here because we check whether the response for a
pa
Hi Chamin
it is a great idea to level up monetization support for APIM. +1 !
There are some building blocks already in place and the sample billing
engine for 2.6.0 is in alpha state :
https://github.com/ruks/wso2-am-billing-engine/releases/tag/v2.6.0-alpha
question 1 : I understand that you are
Hi all,
We are in the process of providing support for monetization in APIM. We
have performed a pre-analysis of $subject and came up with the initial
design.
For the initial implementation, we plan to use Stripe and implement the
necessary functions to support monetization flow in the product.
10 matches
Mail list logo
