Uploaded image for project: 'Help-Desk'
  1. Help-Desk
  2. HELP-4526

FIWARE.Request.Tech.Apps.Store.WStore create offering with yearly recurring payment and monthly pay per use billing

    Details

    • Type: extRequest
    • Status: Closed
    • Priority: Major
    • Resolution: Done
    • Fix Version/s: 2021
    • Component/s: FIWARE-TECH-HELP
    • Labels:
      None
    • HD-Chapter:
      Apps
    • HD-Enabler:
      WStore

      Description

      Dear FIWARE coach,
      we forward you a support request received from a CreatiFI applicant we are not able to solve.
      Please let us know if you need direct contact with the submitter.
      Thanks.

      *************************************************
      One of our pricing models is the following:

      A yearly license fee is purchased, which allows for a fixed number of usages of our product, for example 1,000,000 uses.
      When the allowed usages are depleted, the client will be charged each month for the additional usage of our product (which is a fixed amount for each usage).

      According to the pricing basis document (http://edu.fiware.org/mod/resource/view.php?id=531), we will have to create a custom USDL, which contains multiple pricing plans:

      • A subscription pricing plan with a yearly interval
      • A pay-per-use plan (component based as we have only one parameter and a very easy pricing function usage*FIXED_AMOUNT)

      However, this document states the following:

      It is important to note that
      the aggregation of accounting information and charging to the customer is made monthly by
      default, being the first charge a month after the purchase. This default timing only applies when
      the price models only contains pay-per-use and single payments; however, if the price model
      includes subscriptions, the pay-per-use is resolved every time a subscription is renovated.

      We however require a monthly charge of additional usage

      How can this payment profile be included in WStore? Currently the only alternative we see is to set up two separate pricing plans and request our user to make two purchases. This is not acceptable as it severely impacts client experience.

        Issue Links

          Activity

          Hide
          backlogmanager Backlog Manager added a comment -

          Assignee before migration = Francisco de la Vega

          Show
          backlogmanager Backlog Manager added a comment - Assignee before migration = Francisco de la Vega
          Hide
          backlogmanager Backlog Manager added a comment -

          Original time span = 66 days, 22:13:12

          Show
          backlogmanager Backlog Manager added a comment - Original time span = 66 days, 22:13:12

            People

            • Assignee:
              fdelavega Francisco de la Vega
              Reporter:
              silviocretti Silvio Cretti
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: