Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2535

Add additional support for exchange rate processors

    Details

    • Type: Story
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.0-b1
    • Component/s: None
    • Labels:
      None

      Description

      The exchange rate processors that we have/had (Yahoo Finance, Google Finance, etc.) can be unreliable as they may scrape a website for the exchange rate (and the page can change, breaking the scrape), the accuracy may not be accurate, or in the case of Yahoo Finance, the service can be discontinued abruptly without notice.

      It would be better to also support a dedicated exchange rate processing service that provides an API and API key for fetching rates. These services can require a paid subscription, so they should be added in addition to the free (but potentially unreliable) ones that currently exist in Blesta. Because of the necessity to support an API key, exchange rate processors should be able to inject a set of fields to save as settings for the processor.

      Consider the following new exchange rate processors:

      1. Currency Layer
        • Free version supports up to 1000 API calls per month, updated hourly
      2. Open Exchange Rates
        • Free version supports up to 1000 API calls per month, updated hourly.
        • Free version is LIMITED TO USD AS BASE CURRENCY! We may be able to work-around this by converting the rate with respect to the base currency configured in Blesta.
      3. European Central Bank
      4. Fixer.io (CORE-2536)
      5. X-RATES (CORE-2534)

        Issue Links

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              tyson Tyson Phillips (Inactive)
              Reporter:
              tyson Tyson Phillips (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                5/Dec/17

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 11 minutes
                1d 11m

                  Agile