Bank Automation News

No products in the cart.

Subscribe
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
Log In
No Result
View All Result
  • AI
  • Business Banking
  • Core
  • Cloud
  • Payments
  • Retail Banking
  • Risk & Security
Bank Automation News
  • News
  • Data
  • Transactions
  • Events
    • Bank Automation Summit
    • Apply to Speak
    • Apply to Demo
  • Podcast
  • WEBINARS
    • On-Demand Webinar: Emerging fintechs: New technologies you need to know now
    • Webinar Library
BAN PLUS
Log In
No Result
View All Result
Bank Automation News
No Result
View All Result

Blockchain in Insurance #insurtech

Daily FintechbyDaily Fintech
May 13, 2016
in Archive
Reading Time: 6 mins read
0
Share on Facebook
LifeInsurance_shutterstock_154854575-260x140
Image from actuaries.digital

Early stage investors and entrepreneurs make their money when something moves from bleeding edge (lots of technical risk) to leading edge (market and team risk).  Blockchain in Insurance  is currently at this intersection, which is why we see so much interest in the subject. The technical risk is lessening every day (there is always some technical risk) but there is still a lot of market risk. We are seeing a lot of Proof Of Concept (POC) projects and lots of Minimum Viable Products (MVP), but as yet very little Product Market Fit (PMF). There is lots of good theory on why these MVPs should get to PMF, but there is as yet very little actual proof from the market.

Auto Payout Based on a Trustless Smart Contract

This holds out a win/win promise. Customers know that payout is automatic and immediate (no more hassling for payout during the most stressful times when the bad event has actually happened). Insurance companies get two benefits:

  • Elimination of fraud. The Insurance company does not rely on the customer’s version of truth. There is independently verified data.
  • Elimination of claims processing cost. This is a consequence of elimination of fraud.

For this to work, it has to be binary simplicity. An algo has to make a yes/no decision instantly. Something with complexity (such as who is at fault in an accident or whether a medical procedure is covered) needs human intervention.

One example of where we see that binary result is flight insurance. The flight was either cancelled or it was not. Blockchain systems use external data sources (e.g via the Oraclize service ) to get this proof of what happened. A Proof Of Concept for this flight insurance use case was coded during a weekend at a hackathon using Ethereum – proving that technical risk is not the prime concern.

We expect to see lots of use cases where this binary rule applies where really low cost insurance can be offered (thanks to elimination of fraud and claims processing). This is classic disruption at the edge – where disruption usually gets traction. For example, there are lots of use cases within the sharing economy. These are on demand or just-in-time insurance use cases.

One mainstream use case is Life Insurance. Life or death is pretty binary. Smart Contracts can look at online death registers and make payout to the designated account. Given the stress that grieving relatives are under, this would score high on Net Promoter Scores.

Enforced rules for where to spend the money

In more complex claims processes it is more about enforcing rules on where a customer spends the money. For example, in an auto accident, only go to these garages or in a ski accident, only go to these doctors. This is a win/win as the customer has confidence of getting reimbursement and the insurer gets lower and more predictable claims. Using geo location and smart phones it is pretty simple for the customer to make a decision where to go even in stressful situations and will take this action if there is 100% confidence in auto payout via a Blockchain resident smart contract. Ideally the vendor (garage, doctor etc) gets notification on their phone of incoming customer and notification from the smart contract of what they can charge, so the customer does not have to pay and reclaim later.

The Provenance use case for Blockchain

The use case for Insurance that has been understood for some time is Provenance. This affects assets such as jewelry, art and antiques where it is critical to know that the “asset is what the customer claims it is”. If I am insuring a 1964 Chateau Petrus (currently valued in US$ millions), the Insurance carrier needs 100% confidence that it really is a 1964 Chateau Petrus and not cheap wine with a 1964 Chateau Petrus forged label.

An immutable blockchain database is the obvious solution. You can see all transactions on that 1964 Chateau Petrous dating back to when the farmer sold the grapes in 1964. Ok, that only works for transactions starting now unless there is a conversion of historical data – nobody said this was easy!

An early pioneer in this use case is Everledger (our note on Everledger from July 2015 is here). They focus on jewellery, which is a big niche market.

This is a niche within Property Insurance and one can envisage lower cost insurance offered at the point of sale because a smart contract tied to proven provenance means that many more products can be covered. So this can grow the market.

Blockchain + P2P Insurance = Disruption

P2P Insurance has been suggested by many as the disruptive model for Insurance and we have covered this many times on Daily Fintech. It maybe that P2P is only viable with Blockchain resident smart contracts that can guarantee the payout. For the fundamental theory behind this, read a white paper from Joshua Davis entitled “Peer to Peer Insurance on the Ethereum Blockchain”. The Distributed Autonomous Corporation (DAO) that takes in premiums and makes payouts would be owned and controlled by policyholders who have an affinity (ie part of a cohort with a shared risk profile).

Joshua Davis, who wrote that seminal white paper went on to turn theory into practice by creating Dynamis.  They are not trying to boil the ocean; their niche is supplemental unemployment insurance.

Unbreakable Escrow and Solvency 2 on the Blockchain 

As the WEF report states, Blockhain based smart contract Insurance works through an “unbreakable escrow”. The insurer will pay out before they even know about it. This has dramatic and complex implications on solvency regulation that will take time to play out.

Solvency 2 regulation is designed to ensure that insurance companies have enough capital to pay claims.

The issue is how much capital the investor has to put at risk to enable “unbreakable escrow”. Will it be back to the future where the equivalent of Lloyds Names agree to unlimited liability? Or will Insurance companies have to deposit a far higher % of reserves to guarantee the payout. A P2P DAO owned by the policy holders can afford to do this. A traditional insurance company cannot afford to do this. This is classic disruption.

A Digital Lloyds of London

One of the best visions of what a Blockchain based Insurance marketplace connecting brokers, carriers and reinsurance is from a Blockchain foundry called Chain That. Their video explainer sounds like a back to the future version of the original Lloyds of London – replacing human runners carrying paper between the parties with a shared ledger and smart contracts.
Chain That shows how important existing data standards are. They use Accord data -which serves a similar role to the FIX standard in capital markets.

MicroInsurance for the Underbanked using Blockchain

Consuelo (Spanish word for consolation) from a Mexican company called Saldo.mx offers microinsurance for health and life insurance. This is like microfinance – doing something in really small bites at very low cost. Saldo prefer the term non-adjustable insurance, which means replacing the claims process and the claims adjuster.

This fits the Daily Fintech thesis of “first the rest then the west” (that innovation will come from billions emerging into a global middle class because they have greater need and a technological clean slate). What Saldo is referring to is the same Blockchain based smart contracts based on verifiable data from oracles that we described earlier. What is interesting is that this innovation may first get traction among the Underbanked.

Daily Fintech recently described why China and India may define the future of Insurance and InsurTech. At the time we speculated that this innovation could also come from Latin America. It is interesting to see this happening now.

What makes Consuelo particularly interesting is their focus on one of the most critical global networks – diaspora networks. They are focussed on the huge market of Mexican Americans. They call this   “community without borders” in this interview in CoinTelegraph.

Daily Fintech Advisers provide strategic consulting to organizations with business and investment interests in Fintech. Bernard Lunn is a Fintech thought-leader.

Tags: Bitcoin & BlockchainBlockchainInsurTechP2P Insurancesmart contracts
Previous Post

Innovation Comes to Employee Benefits via PayActiv, Student Loan Genius

Next Post

Breaking Banks: Fintech Inside Banks (Warning: May Include Bitcoin)

Related Posts

Image by CanStock
Archive

Blend Labs integrates acquisition’s mortgage automation process

August 20, 2021
Photo by CanStock
Archive

Chilean fintech looks for slice of giant money transfers market

August 5, 2021
Image by CanStock
Risk & Security

Listen: How banks can protect themselves against cybersecurity risks

August 3, 2021
Next Post

Breaking Banks: Fintech Inside Banks (Warning: May Include Bitcoin)

Please login to join discussion

Stay Informed with Our Newsletters

EMERGING FINTECH DIRECTORY

Emerging Fintech Directory

The Buzz Podcast

RETAIL BANKING

Huntington Bank’s new branch in Spartanburg

Huntington Bank resolves outage

May 7, 2025
bank

Barclays, Banco Santander, Lloyds plan product expansion

May 5, 2025
satisfactiin

Online banks lead FIs in customer satisfaction

May 2, 2025

SPONSORED

Just Released! 2025 Strategy Benchmark

May 1, 2025

Leverage Treasury Management to Turn Fraud Prevention Into a Strategic, Revenue-Generating Opportunity

April 1, 2025

A growth mindset in banking requires AI

March 27, 2025
  • About Us
  • Help Center
  • Contact Us
  • Privacy Terms
  • ADA Compliance
  • Advertise

 Manage Cookie Consent

Connect

twitter linkedin podcast podcast podcast
© 2025 Royal Media
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

Welcome Back!

Login to your account below

Forgotten Password?

Retrieve your password

Please enter your username or email address to reset your password.

Log In
No Result
View All Result
  • NEWS
    • All News
    • AI
    • Business Banking
    • Core
    • Cloud
    • Payments
    • Retail Banking
    • Risk & Security
  • DATA
  • TRANSACTIONS
  • EVENTS
    • Bank Automation Summit
  • PODCAST
  • WEBINARS
    • Upcoming Webinar
    • Webinar Library
  • SUBSCRIBE
  • Log In / Account

THIS WEBSITE USES COOKIES

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “I CONSENT”, you consent to the use of ALL the cookies.

Cookie settingsI CONSENT

Review our Cookie Policies
.
Manage Cookie Consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
__cfruidsessionCloudflare sets this cookie to identify trusted web traffic.
__RequestVerificationTokensessionThis cookie is set by web application built in ASP.NET MVC Technologies. This is an anti-forgery cookie used for preventing cross site request forgery attacks.
_abck1 yearThis cookie is used to detect and defend when a client attempt to replay a cookie.This cookie manages the interaction with online bots and takes the appropriate actions.
34f6831605sessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
a64cedc0bfsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ak_bmsc2 hoursThis cookie is used by Akamai to optimize site security by distinguishing between humans and bots
ARRAffinitysessionARRAffinity cookie is set by Azure app service, and allows the service to choose the right instance established by a user to deliver subsequent requests made by that user.
ARRAffinitySameSitesessionThis cookie is set by Windows Azure cloud, and is used for load balancing to make sure the visitor page requests are routed to the same server in any browsing session.
AWSELBsessionAssociated with Amazon Web Services and created by Elastic Load Balancing, AWSELB cookie is used to manage sticky sessions across production servers.
bm_sz4 hoursThis cookie is set by the provider Akamai Bot Manager. This cookie is used to manage the interaction with the online bots. It also helps in fraud preventions
cf_ob_infopastThe cf_ob_info cookie is set by Cloudflare to provide information on HTTP Status Code returned by the origin web server, the Ray ID of the original failed request and the data center serving the traffic.
cf_use_obpastCloudflare sets this cookie to improve page load times and to disallow any security restrictions based on the visitor's IP address.
CONCRETE5sessionThis cookie is set by the provider Concrete5 web content management system. This is a necessary cookie used for maintaining the user session between pages.
connect.sid1 monthThis cookie is used for authentication and for secure log-in. It registers the log-in information.
cookielawinfo-checkbox-advertisement1 yearSet by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category .
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
cookiesession11 yearThis cookie is set by the Fortinet firewall. This cookie is used for protecting the website from abuse.
crmcsrsessionGeneral purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server.
ep20130 minutesThis cookie is set by Wufoo for load balancing, site traffic and preventing site abuse.
JSESSIONIDsessionThe JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application.
LS_CSRF_TOKENsessionCloudflare sets this cookie to track users’ activities across multiple websites. It expires once the browser is closed.
PHPSESSIDsessionThis cookie is native to PHP applications. The cookie is used to store and identify a users' unique session ID for the purpose of managing user session on the website. The cookie is a session cookies and is deleted when all the browser windows are closed.
sxa_sitesessionThis cookie is used to identify the webiste visitor's session state across page requests on server.
ts3 yearsPayPal sets this cookie to enable secure transactions through PayPal.
ts_c3 yearsPayPal sets this cookie to make safe payments through PayPal.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
wordpress_test_cookiesessionThis cookie is used to check if the cookies are enabled on the users' browser.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
__cf_bm30 minutesThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management.
_zcsr_tmpsessionZoho sets this cookie for the login function on the website.
663a60c55dsessionThis cookie is related to Zoho (Customer Service) Chatbox
bcookie2 yearsLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID.
bscookie2 yearsLinkedIn sets this cookie to store performed actions on the website.
e188bc05fesessionThis cookie is set in relation to Zoho Campaigns
geosessionThis cookie is used for identifying the geographical location by country of the user.
iamcsrsessionZoho (Customer Support) sets this cookie and is used for tracking visitors (for performance purposes)
langsessionLinkedIn sets this cookie to remember a user's language setting.
languagesessionThis cookie is used to store the language preference of the user.
lidc1 dayLinkedIn sets the lidc cookie to facilitate data center selection.
optimizelyEndUserId1 yearOptimizely uses this cookie to store a visitor's unique identifier which is a combination of a timestamp and a random number. Different variations of web parts are shown to users that optimizes the website's user experience.
tableau_localesessionTableau uses this cookie to determine the preferred language and country-setting of the visitor - This allows the website to show content most relevant to that region and language.
UserMatchHistory1 monthLinkedIn sets this cookie for LinkedIn Ads ID syncing.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
AWSELBCORS20 minutesThis cookie is used by Elastic Load Balancing from Amazon Web Services to effectively balance load on the servers.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThe __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites.
_ga2 yearsThe _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors.
_gcl_au3 monthsProvided by Google Tag Manager to experiment advertisement efficiency of websites using their services.
_gid1 dayInstalled by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously.
ajs_anonymous_idneverThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.
ajs_group_idneverThis cookie is set by Segment to track visitor usage and events within the website.
ajs_user_idneverThis cookie is set by Segment to help track visitor usage, events, target marketing, and also measure application performance and stability.
browser_id5 yearsThis cookie is used for identifying the visitor browser on re-visit to the website.
CONSENT2 yearsYouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data.
sid1 yearThe sid cookie contains digitally signed and encrypted records of a user’s Google account ID and most recent sign-in time.
uid1 yearThis is a Google UserID cookie that tracks users across various website segments.
vuid2 yearsVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website.
WMF-Last-Access1 month 21 hours 5 minutesThis cookie is used to calculate unique devices accessing the website.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
_dc_gtm_UA-1038974-41 minuteUsed to help identify the visitors by either age, gender, or interests by DoubleClick - Google Tag Manager.
_fbp3 monthsThis cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website.
_pxhdpastUsed by Zoominfo to enhance customer data.
fr3 monthsFacebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin.
IDE1 year 24 daysGoogle DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile.
test_cookie15 minutesThe test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies.
VISITOR_INFO1_LIVE5 months 27 daysA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.
YSCsessionYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.
yt-remote-connected-devicesneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt-remote-device-idneverYouTube sets this cookie to store the video preferences of the user using embedded YouTube video.
yt.innertube::nextIdneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
yt.innertube::requestsneverThis cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
049fc2ef5beb27056b07d9e4c4d13fd3sessionNo description
akaalb_http_misc_subssessionNo description
AnalyticsSyncHistory1 monthNo description
BIGipServermsocu-web-2-rr.webfarm.ms.com.10882sessionNo description
bm_misessionNo description available.
CX_4061522881 yearNo description
DCID20 minutesNo description
debugneverNo description available.
DrupalVisitorMobilesessionNo description available.
ep2033 monthsNo description available.
frbatlanta#langsessionNo description
geo_info1 yearNo description available.
GoogleAdServingTestsessionNo description
li_gc2 yearsNo description
loglevelneverNo description available.
loom_anon_commentsessionNo description available.
loom_referral_videosessionNo description
mkjs_group_idneverNo description available.
mkjs_user_idneverNo description available.
MorganStanley.ClientServ.Common.IPZipAccess.IPZipCookie.DEFAULT_COOKIE_NAMEpastNo description
NSC_us_nbsl-83+63+21+25-91sessionNo description
nyt-a1 yearThis cookie is set by the provider New York Times. This cookie is used for saving the user preferences. It is used in context with video and audio content.
nyt-gdpr6 hoursNo description available.
nyt-purr1 yearNo description available.
OCC_Encrypted_CookiesessionNo description
polleverywhere_session_id14 daysNo description
ppnet_2020sessionNo description available.
ppnet_2777sessionNo description available.
reuters-geosessionNo description
shell#langsessionNo description
smcx_0_last_shown_atsessionNo description available.
tableau_public_negotiated_localesessionNo description available.
vary1 monthNo description
www#langsessionNo description
X-Vive-CountrysessionNo description
xn_uuid1 monthNo description
Save & Accept
Powered by CookieYes Logo