Details
Improvement
Major
Description
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ (PHP API Library here also)
In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)".
The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use.
Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not.
MaxMind is planning to deactivate their legacy APIs at the end of May 2022.
Development API Credentials available in Feng.
Activity
Paul Phillips
created issue -
Paul Phillips
made changes -
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
Paul Phillips
made changes -
| Rank | Ranked lower |
Paul Phillips
made changes -
| Description |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. |
Paul Phillips
made changes -
| Description |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. Development API Credentials available in Feng. |
Paul Phillips
made changes -
| Description |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. Development API Credentials available in Feng. |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ (PHP API Library here also) In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. Development API Credentials available in Feng. |
Paul Phillips
made changes -
| Rank | Ranked higher |
Paul Phillips
made changes -
| Rank | Ranked higher |
| Description |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ (PHP API Library here also) In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. Development API Credentials available in Feng. |
When a user signs up with Maxmind's minfraud service, they have to ask Maxmind to enable the "legacy API" for it to work with Blesta. We need to switch Maxmind over to using the new API. Perhaps there should be an option as to which API (defaulting to the latest) when configuring Maxmind within the Order Settings for backwards compatibility.
See https://dev.maxmind.com/minfraud/ (PHP API Library here also) In implementing this, maybe we should add it as a new type since we want to maintain backwards compatibility. Maybe just rename the old one "Maxmind (Legacy)". The old API had 2 tiers: Standard and Premium. The new API has two tiers also, called Insights and Factors. One providers more information than the other and has a higher query cost. We should allow in the Settings for staff to select which tier they prefer to use. Maxmind also has a static Javascript embed code that can be added to order forms and providers additional tracking data for determining risk. There should be an option in the settings on whether to embed this in the order pages or not. *MaxMind is planning to deactivate their legacy APIs at the end of May 2022.* Development API Credentials available in Feng. |
| Rank | Ranked higher |
| Fix Version/s | 4.12.0-b1 [ 11502 ] | |
| Fix Version/s | Short Term [ 10800 ] |
| Sprint | 4.12.0 Sprint 1 [ 113 ] |
| Rank | Ranked lower |
| Assignee | Abdy Franco [ abdy ] |
Automated transition triggered when Abdy Franco created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 35 minutes [ 2100 ] | |
| Worklog Id | 13880 [ 13880 ] |
| Time Spent | 35 minutes [ 2100 ] | 1 day, 30 minutes [ 30600 ] |
| Worklog Id | 13883 [ 13883 ] |
Automated transition triggered when Abdy Franco created pull request #188 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Time Spent | 1 day, 30 minutes [ 30600 ] | 1 day, 5 hours, 3 minutes [ 46980 ] |
| Worklog Id | 13892 [ 13892 ] |
| Time Spent | 1 day, 5 hours, 3 minutes [ 46980 ] | 1 day, 5 hours, 47 minutes [ 49620 ] |
| Worklog Id | 13900 [ 13900 ] |
| Sprint | 4.12.0 Sprint 1 [ 113 ] | 4.12.0 Sprint 2 [ 114 ] |
| Rank | Ranked lower |
| Time Spent | 1 day, 5 hours, 47 minutes [ 49620 ] | 1 day, 7 hours, 9 minutes [ 54540 ] |
| Worklog Id | 13922 [ 13922 ] |
Automated transition triggered when Jonathan Reissmueller merged pull request #188 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
