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

What does the future hold for blockchain and insurance?

Daily FintechbyDaily Fintech
January 14, 2016
in Archive
Reading Time: 7 mins read
0
Share on Facebook

Blockchain, Blockchain, Blockchain! What does it all mean for Insurance? No one knows yet, but that doesn’t stop blockchain being one of the hottest topics for the Insurance industry right now. This week, I take a look at the direction this puck is heading.

blockchain-1200x651

(photo source: followmyvote.com/the-proof-is-in-the-blockchain)

Hype or reality?

Last September, the World Economic Forum published a report entitled, “Deep Shift – Technology Tipping Points and Societal Impact”. The report is based on surveys with over 800 executives and experts about new technologies and innovations. The point of the report is to identify deep shifts in society that result from new technologies. These include areas such as 3D printing, driverless cars, wearables and artificial intelligence.

I was drawn to shift number 16, simply called “Bitcoin and the blockchain”. By 2025, 58% of these experts and executives believed we would hit the tipping point for Bitcoin and blockchain. This was defined as;

“10% of global gross domestic product will be stored on blockchain technology”

To put that into context, the total worth of Bitcoin today in the blockchain is circa 0.025% of today’s $80trillion global GDP.

Also of interest, especially given that it looks like Tunisia will be the first country to issue a digital currency on a blockchain, shift number 18 was called “Governments and the blockchain”. Here, almost 3 out of 4 of the survey group expected that “Governments would collect tax via a blockchain by 2023”.

It’s a reality then!

It’s certainly looks that way. And $500m of VC money in 2015 can’t be wrong, can it?

The prospect of a seismic shift on a par with the impact of the Internet is massively compelling. Which explains all the attention, predictions and excitement about blockchain. But, if we use the evolution of the Internet as a benchmark, the development of blockchain today for commercial use is equivalent to the Internet in, say, the mid 1990s’ at best.

The debates on with or without Bitcoin, private or public blockchains, Sybase vs Oracle (oops, wrong century) are yet to play out. The ability of the Bitcoin blockchain to scale to handle massive volumes at lightening speed remains unproven.

Now, just as it was in 1995, blockchain technology is at an embryonic stage. Still finding its way; yet to prove it is a viable, industrial strength, large-scale technology capable of solving world hunger.

Which is why I am going to focus on the use case for insurance, rather than the technology itself. (For one explanation of how Blockchain works, go to Wired, here.)

The Smart Insurance Contract

This is getting most attention right now. The notion of automating the insurance policy once it is written into a smart contract is compelling. The idea that it will pay out against the insurable event without the policyholder having to a make a claim or the insurer having to administer the claim has significant attractions.

First, the cost of claims processing simply goes away. Second, the opportunity for fraud largely goes away too. (I hesitate on this one simply because it is theoretical and not yet proven). Third, customer satisfaction must go up!

One example being used to illustrate how these might work came from the London Fintech Week Blockchain Hackathon last September. Here a team called InsurETH built a flight insurance product over a weekend on the Ethereum platform.

The use case is simple. In the twelve months to May 2015, there were 558,000 passengers who did not claim for delayed or cancelled flights in and out of the UK. In fact, less that 40% of passengers claimed money back from their insurance policy.

They built a smart contract where the policy conditions were held on blockchain. Using the Oraclize service to connect the blockchain with the Internet, publicly available data is used to trigger the insurance policy.

In this case, a delayed flight is a matter of fact and public record. It does not rely on anyone’s judgement or individual assessment. It is what it is. If the event occurs, the smart contract gets triggered and the pay out is made. Automatic and immediate, with no claims processing costs for the insurer and satisfaction for the customer.

Building on this example and applying it to motor, smart contracts offer a solution for insurers to control claims costs after an accident. The trigger that there has been an accident would come from a smartphone app or the connected car via the Internet to the blockchain. Insurers are always frustrated when customers go a more expensive route for repairs, recovery and car hire. So, with a smart contract, insurers could code the policy conditions to only pay- out to the designated third parties (see related article by Sia Partners).

So long as the policy conditions are clear and unambiguous, and the conditions for paying out are objective, the insurance can be written in a smart contract. When the conditions are undeniably reached, the smart contract pays out. As blockchain startup SmartContract put it, “Any data feed trusted by a counterparty to release payment or simply complete an agreement, can power a smart contract.”

To understand this better, I asked Joshua Davis, the technical architect and co-founder at blockchain p2p InsurTech Dynamis to explain it to me, “you need well qualified oracle(s) to establish what “conditions” exist in the real world and when they have been “undeniably reached”.  An oracle is a bridge between the blockchain and the current state of places, people and things in the real world.  Without qualified oracles there can be no insurance that has any relation to the world that we live in.   

“As far as oracles go you can use either a single trusted oracle, who puts up a large escrow that is lost if they feed you misinformation, or many different oracles who don’t rely on the same POV or data sources to verify that events occurred.

“In the future social networks will be the cheapest and most used decentralized data feeds for various different insurance applications.  Our social networks will validate and verify our statements as lies or facts.  We need to be able to reliably contact a large enough segment of a claimant’s social network to obtain the truth.  If the insurance policy can monitor the publishing or notification of our current status to these participants and their responses accurately confirm it, then social networks will make for the cheapest most reliable oracles for all types of future claims validation efforts.”

Is this simply too good to be true?

Personally, I don’t think it is. Of course, a smart contract doesn’t have to be on the blockchain to deliver this use case.

However, what the blockchain offers is trust. And it offers provenance. The blockchain provides an immutable record and audit trail of an agreement. The policyholder does not have to rely on the insurer’s decision to pay them damages because they’ve broken their promise to keep them safe from harm. As the WEF report states, this is an “unbreakable escrow”. The insurer will pay out before they even know about it.

There’s another reason for going with the blockchain – cybersecurity!

With the blockchain sitting outside the corporate firewall and managed by many different and unconnected parties, the cyber criminal no longer has a single target to attack. As far as I’m aware, blockchain is immune to all of the conventional cyber threats that corporations are scared about.

What happens when you put blockchain and P2P Insurance together?

In December, I published a 2-part article on Peer 2 Peer Insurance (here are the links to Part 1 and Part 2). When you bring the P2P model together with the blockchain, this creates the potential for a near-autonomous self-regulated insurance business model for managing policy and claims.

Last year, Joshua Davis wrote an interesting white paper called “Peer to Peer Insurance on the Ethereum Blockchain”. In the paper, he presents the theory behind blockchain and the creation of Decentralized Autonomous Organizations (“DAO”). These are corporate entities with no human employees.

The DAOs would be created for groups of policyholders, in a similar way to the P2P group model of the likes of Guevara and Friendsurance. No single body or organization would control the DAO; it would be equally “controlled” by its policyholders within each group. All premiums paid in would create a pool of capital to pay claims.

And because this is a self-governing group with little or no overheads, any float at the end of the year would be redistributed back amongst the policyholders. Arguably, this makes the DAO a non-profit making organization and materially increases the capital reserve for claims costs.

The big question mark for this model is regulation. Who will maintain the blockchain code with in each DAO when regulations change does not yet have an answer. But, what does seem a dead cert is that someone, somewhere is figuring out how to solve this.

Blockchain offers the potential for new products and services that have never existed before in a P2P insurance model. It should also open up insurance to whole new markets, especially those on or near the poverty line.

For now, we watch to see what comes from the likes of Dynamis who are using smart contracts to provide supplementary employment insurance cover on Ethereum.

Innovation will come from new players

It has been my belief for some time that, in the main, incumbent insurance firms will not be able to materially innovate from within. Like Fintech, the innovation that will radically change this industry will come from new entrants and start-up players, such as;

Dynamis

SmartContract

Rootstock

Everledger (see previous article on Daily Fintech here)

Tradle

Ethereum Frontier

Codius (Ripple Labs) (update: Codius discontinued)

This is particularly true with blockchain in insurance. These new age pioneers are unencumbered by corporate process, finance committees, bureaucracy and organisational resistance to change.

Besides, the incumbent insurance CIOs have heard this all before. For decades, software vendors have promised nirvana with new policy admin, claims and product engines. So why should they listen to the claims that blockchain is the panacea for their legacy IT issues. Which is a subject for another post… watch this space!

By Rick Huckstep

Tags: Bitcoin & BlockchainBlockchainInsurTechP2P Insurance
Previous Post

Here Are the New Apple Pay Processors

Next Post

Two Digital Banks Launch in a Single Day

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

Two Digital Banks Launch in a Single Day

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