Picture
Automotive Solution Developer Portal

My Premium

Introduction

Our “My Premium” feature/service enables your customers to have visibility of their premium price within the app to support scenarios where it can fluctuate based on driving distances (Pay As You Drive) and/or driving behaviours (Pay How You Drive) such as distraction events, speeding, manoeuvres and contextual factors.

The implementation behind “My Premium” allows for full flexibility to support premium calculations based on selected driving factors (e.g. from distance driven to speeding). The “My Premium” API is used to enable premium price/discounts to be displayed to customers based on the calculations made/factors considered by yourselves.

Use-Cases

Below are some illustrative examples to show how “My Premium” looks from a customers perspective in the mobile app.

“My Premium” is visible on the home page of the app and can also be accessed from the settings menu, enabling customers to gain further insights regarding their premium price.

Mobile App Behaviour

  1. Bar chart highlights the current month when displayed as an increment (e.g. June is highlighted if current month is June).

  2. For months prior to the current month, bar chart will be populated based on the data provided (e.g. monthly, quarterly - depends on the cadence submitted by yourselves).

  3. The bar chart always consists of 5 increments along the bottom (e.g. months/year) and the three price increments on the side are; base premium, half the base premium and 0.

  4. If a discount is submitted for a future month/date, it will not be displayed until the corresponding date has occurred (based on "startingDate" value submitted via the "My Premium" API).

  5. Any discount items with a "startingDate" before the current contract start date will not be displayed to the customer.

  6. In instances where there are less than 5 discount submissions, any future increments of the bar chart are always month by month from the current month (e.g. Oct, Nov, Dec). Other time spans are not currently supported.

  7. The "Total savings" cell on the home page displays the premium savings from the start of the contract.

  8. The premium amount/discount shown on the dashboard is the most recent submission (e.g. if the last discount that was given was June, then this is what is displayed on the dashboard).

  9. "minimumPremium", "days" and "months" attributes from the "My Premium" API are not used by the mobile app.

  10. If no premium data has been submitted, the "My Premium" cell is still shown on the home page but is unpopulated. The "My Premium" screen itself is just blank when accessing this either via the menu or by tapping the "My Premium" cell.

Integration Flow

The below diagram depicts the end to end flow to support the “My Premium”:

1. Obtain the desired telematics data (e.g. trip information, distraction events, scoring etc.) to support premium/discount calculations.

Data can be obtained via the following methods:

1a. Domain Event Service

  • Data can be received real time through using webhooks, supporting use cases where it is desired for data to be obtained in a timely manner.

1b. Data Delivery Service

  • Data can be received in bulk through the Data Delivery Service, supporting use cases where it is more desirable to obtain consolidated data.

2. Perform premium calculations

  • Through using the desired data which has been obtained (either via the webhook approach or Data Delivery Service) you can then perform the appropriate calculations against the customers premium.

  • This approach enables full flexibility as the calculation made are up to you and are performed by yourselves based on the data obtained.

3. Submits premium/discount information to Swiss Re

  • Once completing the premium calculations, the Swiss Re “My Premium” API should then be invoked with the premium information to be displayed to the customer in the mobile app. The “My Premium” API supports a number of attributes such as; base premium, calculated premium, currency etc.

4. App shows pricing/discount data

  • Once you have submitted information to the “My Premium” API, it is then subsequently shown to the customer in the mobile app through the “My Premium” feature.

End to End Steps

Aligned with the integration flow, the below table provides the segregation of responsibilities between Swiss Re vs yourselves ("Client").

Sample Payload Request

Below is a sample payload request for a customer, aligned with the following scenario:

  • Customer has driven 2000 km in the course of a month.

  • Their monthly base premium is 300 €.

  • The premium cannot go below 200 €.

  • The premium has been calculated as 280 € for the month, meaning the customer has achieved a 20 € saving.

  • The discount commences on 11th October 2022 and applies for 1 month (aligned with the premium payments)

{
    "discountID": "80bf896a-e1b8-469c-8546-4861b27d1aab",
    "drivenKm": 2000.0,
    "basePremium": 300.00,
    "calculatedPremium": 280.00,
    "minimumPremium": 200.00,
    "currencyDecimalPlaces": 2,
    "currencySymbol": "€",
    "currencyCode": "EUR",
    "contractId": "97e9da42-92f1-4c06-10e2-08da9190b1b4",
    "tenantID": "fbfa0214-5105-4393-9008-32fb66c89414",
    "startingDate": "2022-10-11T00:00:00",
    "days": 0,
    "months": 1
}

Methods and Dictionary

Further information regarding the methods availability and the data dictionary can be be found here (can we insert hyperlink?).