Recherche avancée

Sur d’autres sites (10332)

• Four Trends Shaping the Future of Analytics in Banking

  27 novembre 2024, par Daniel Crough — Banking and Financial Services

  While retail banking revenues have been growing in recent years, trends like rising financial crimes and capital required for generative AI and ML tech pose significant risks and increase operating costs across the financial industry, according to McKinsey’s State of Retail Banking report.

   

  Today’s financial institutions are focused on harnessing AI and advanced analytics to make their data work for them. To be up to the task, analytics solutions must allow banks to give consumers the convenient, personalised experiences they want while respecting their privacy.

   

  In this article, we’ll explore some of the big trends shaping the future of analytics in banking and finance. We’ll also look at how banks use data and technology to cut costs and personalise customer experiences.
  
  So, let’s get into it.

  

  This doesn’t just represent a security risk, it also impacts the usability for both customers and employees. Does any of the following sound familiar ?

  • Only specific senior employees know how to navigate the software to generate custom reports or use its more advanced features.
  • Customer complaints about your site’s usability or online banking experience are routine.
  • Onboarding employees takes much longer than necessary because of convoluted systems.
  • Teams and departments experience ‘data siloing,’ meaning that not everyone can access the data they need.

  These are warning signs that IT systems are ready for a review. Anyone thinking, “If it’s not broken, why fix it ?” should consider that legacy systems can also present data security risks. As more countries introduce regulations to protect customer privacy, staying ahead of the curve is increasingly important to avoid penalties and litigation.

  And regulations aren’t the only trends impacting the future of financial institutions’ IT and analytics.

  4 trends shaping the future of analytics in banking

  New regulations and new technology have changed the landscape of analytics in banking.

  New privacy regulations impact banks globally

  The first major international example was the advent of GDPR, which went into effect in the EU in 2018. But a lot has happened since. New privacy regulations and restrictions around AI continue to roll out.

  • The European Artificial Intelligence Act (EU AI Act), which was held up as the world’s first comprehensive legislation on AI, took effect on 31 July 2024.
  • In Europe’s federated data initiative, Gaia-X’s planned cloud infrastructure will provide for more secure, transparent, and trustworthy data storage and processing.
  • The revised Payment Services Directive (PSD2) makes payments more secure and strengthens protections for European businesses and consumers, aiming to create a more integrated and efficient payments market.

  But even businesses that don’t have customers in Europe aren’t safe. Consumer privacy is a hot-button issue globally.

  For example, the California Consumer Privacy Act (CCPA), which took effect in January, impacts the financial services industry more than any other. Case in point, 34% of CCPA-related cases filed in 2022 were related to the financial sector.

  California’s privacy regulations were the first in the US, but other states are following closely behind. On 1 July 2024, new privacy laws went into effect in Florida, Oregon, and Texas, giving people more control over their data.

  

  One typical issue for companies in the banking industry is that their privacy measures regarding user data collected from their website are much less lax than those in their online banking system.

  It’s better to proactively invest in a privacy-centric analytics platform before you get tangled up in a lawsuit and have to pay a fine (and are forced to change your system anyway). 

  And regulatory compliance isn’t the only bonus of an ethical analytics solution. The right alternative can unlock key customer insights that can help you improve the user experience.

  The demand for personalised banking services

  At the same time, consumers are expecting a more and more streamlined personal experience from financial institutions. 86% of bank employees say personalisation is a clear priority for the company. But 63% described resources as limited or only available after demonstrating clear business cases.

  McKinsey’s The data and analytics edge in corporate and commercial banking points out how advanced analytics are empowering frontline bank employees to give customers more personalised experiences at every stage :

  • Pre-meeting/meeting prep : Using advanced analytics to assess customer potential, recommend products, and identify prospects who are most likely to convert
  • Meetings/negotiation : Applying advanced models to support price negotiations, what-if scenarios and price multiple products simultaneously
  • Post-meeting/tracking : Using advanced models to identify behaviours that lead to high performance and improve forecast accuracy and sales execution

  Today’s banks must deliver the personalisation that drives customer satisfaction and engagement to outperform their competitors.

  The rise of AI and its role in banking

  With AI and machine learning technologies becoming more powerful and accessible, financial institutions around the world are already reaping the rewards.

  McKinsey estimates that AI in banking could add $200 to 340 billion annually across the global banking sector through productivity gains.

  • Credit card fraud prevention : Algorithms analyse usage to flag and block fraudulent transactions.
  • More accurate forecasting : AI-based tools can analyse a broader spectrum of data points and forecast more accurately.
  • Better risk assessment and modelling : More advanced analytics and predictive models help avoid extending credit to high-risk customers.
  • Predictive analytics : Help spot clients most likely to churn 
  • Gen-AI assistants : Instantly analyse customer profiles and apply predictive models to suggest the next best actions.

  Considering these market trends, let’s discuss how you can move your bank into the future.

  Using analytics to minimise risk and establish a competitive edge 

  With the right approach, you can leverage analytics and AI to help future-proof your bank against changing customer expectations, increased fraud, and new regulations.

  Use machine learning to prevent fraud

  Every year, more consumers are victims of credit and debit card fraud. Debit card skimming cases nearly doubled in the US in 2023. The last thing you want as a bank is to put your customer in a situation where a criminal has spent their money.

  This not only leads to a horrible customer experience but also creates a lot of internal work and additional costs.Thankfully, machine learning can help identify suspicious activity and stop transactions before they go through. For example, Mastercard’s fraud prevention model has improved fraud detection rates by 20–300%.

  

  Implementing a solution like this (or partnering with credit card companies who use it) may be a way to reduce risk and improve customer trust.

  Foresee and avoid future issues with AI-powered risk management

  Regardless of what type of financial products organisations offer, AI can be an enormous tool. Here are just a few ways in which it can mitigate financial risk in the future :

  • Predictive analytics can evaluate risk exposure and allow for more informed decisions about whether to approve commercial loan applications.
  • With better credit risk modelling, banks can avoid extending personal loans to customers most likely to default.
  • Investment banks (or individual traders or financial analysts) can use AI- and ML-based systems to monitor market and trading activity more effectively.

  Those are just a few examples that barely scratch the surface. Many other AI-based applications and analytics use cases exist across all industries and market segments.

  Protect customer privacy while still getting detailed analytics

  New regulations and increasing consumer privacy concerns don’t mean banks and financial institutions should forego website analytics altogether. Its insights into performance and customer behaviour are simply too valuable. And without customer interaction data, you’ll only know something’s wrong if someone complains.

  Fortunately, it doesn’t have to be one or the other. The right financial analytics solution can give you the data and insights needed without compromising privacy while complying with regulations like GDPR and CCPA.

  That way, you can track usage patterns and improve site performance and content quality based on accurate data — without compromising privacy. Reliable, precise analytics are crucial for any bank that’s serious about user experience.

  Use A/B testing and other tools to improve digital customer experiences

  Personalised digital experiences can be key differentiators in banking and finance when done well. But there’s stiff competition. In 2023, 40% of bank customers rated their bank’s online and mobile experience as excellent. 

  Improving digital experiences for users while respecting their privacy means going above and beyond a basic web analytics tool like Google Analytics. Invest in a platform with features like A/B tests and user session analysis for deeper insights into user behaviour.

  

  Behavioural analytics are crucial to understanding customer interactions. By identifying points of friction and drop-off points, you can make digital experiences smoother and more engaging.

  Matomo offers all this and is a great GDPR-compliant alternative to Google Analytics for banks and financial institutions. 

  Of course, this can be challenging. This is why taking an ethical and privacy-centric approach to analytics can be a key competitive edge for banks. Prioritising data security and privacy will attract other like-minded, ethically conscious consumers and boost customer loyalty.

  Get privacy-friendly web analytics suitable for banking & finance with Matomo

  Improving digital experiences for today’s customers requires a solid web analytics platform that prioritises data privacy and accurate analytics. And choosing the wrong one could even mean ending up in legal trouble or scrambling to reconstruct your entire analytics setup.

  Matomo provides privacy-friendly analytics with 100% data accuracy (no sampling), advanced privacy controls and the ability to run A/B tests and user session analysis within the same platform (limiting risk and minimising costs). 

  It’s easy to get started with Matomo. Users can access clear, easy-to-understand metrics and plenty of pre-made reports that deliver valuable insights from day one. Form usage reports can help banks and fintechs identify potential issues with broken links or technical glitches and reveal clues on improving UX in the short term.

  Over one million websites, including some of the world’s top banks and financial institutions, use Matomo for their analytics.

  Start your 21-day free trial to see why, or book a demo with one of our analytics experts.

• Open .avi with OpenCV 2.4 & Ubuntu 11.04

  25 juin 2012, par CTZStef

  I try to open and read video files in .avi format using OpenCV. Here is my code :

  void MainWindow::on_actionOuvrir_fichier_triggered()
  
   140    +   {
  
   141    +    //mettre a -1 streamId
  
   142    +    streamId = -1;
  
   143    +    //ouvrir fenetre navigation fichiers pour recuperer path vers .avi
  
   144    +    QString fileName = QFileDialog::getOpenFileName(this,tr("Ouvrir fichier video"),"/home",
  
   145    +    tr("Videos (*.avi)"));
  
   146    +    std::string utf8_text = fileName.toUtf8().constData();
  
   147    +    //ouvrir .avi
  
   148    +    capture = new VideoCapture(utf8_text);
  
   149    +    //check ouverture
  
   150    +    if(!capture->isOpened())
  
   151    +    cout << "probleme ouverture fichier video" << endl;
  
   152    +    //calculer delay between each frame in ms
  
   153    +    rate = capture->get(CV_CAP_PROP_FPS);
  
   154    +    delay = 1000 / rate;
  
   155    +    //demarrer timer recordId
  
   156    +    recordId = startTimer(delay);
  
   157    +    //capture premiere frame
  
   158    +    if(!capture->read(in))
  
   159    +    cout << "probleme lecture frame fichier video" << endl;
  
   160    +   }

  I get no problem at compilation time, but I can't open a video file. While in debug mode I saw that string utf8_text had the good absolute path to my video, so obviously the problem comes from the constructor of the VideoCapture object. Then, I tried to install every codec pack I could or thought was relevant. But the problem is still there, capture->isOpened() still returns false, and in debug mode I can see that capture contains nothing.

  I am lost here, don't know what to try next. Any idea ??

  Thanks !!!

  [EDIT]
  Just in case, here is the output of ffmpeg -i myFile.avi

  faraday@faraday-Compaq-Evo-D510-e-pc:~/QtProjects/visionDev$ ffmpeg -i 1.avi
  
  FFmpeg version 0.6.6-4:0.6.6-0ubuntu0.11.04.1, Copyright (c) 2000-2010 the Libav developers
  
    built on Jun 12 2012 16:28:21 with gcc 4.5.2
  
    configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --enable-shared --disable-static
  
    WARNING: library configuration mismatch
  
    libavutil   configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libavcodec  configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libavformat configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libavdevice configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libavfilter configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libswscale  configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libpostproc configuration: --extra-version=4:0.6.6-0ubuntu0.11.04.1 --prefix=/usr --enable-avfilter --enable-avfilter-lavf --enable-vdpau --enable-bzlib --enable-libgsm --enable-libschroedinger --enable-libspeex --enable-libtheora --enable-libvorbis --enable-pthreads --enable-zlib --enable-libvpx --disable-stripping --enable-runtime-cpudetect --enable-vaapi --enable-gpl --enable-postproc --enable-swscale --enable-x11grab --enable-libdc1394 --shlibdir=/usr/lib/i686/cmov --cpu=i686 --enable-shared --disable-static --disable-ffmpeg --disable-ffplay
  
    libavutil     50.15. 1 / 50.15. 1
  
    libavcodec    52.72. 2 / 52.72. 2
  
    libavformat   52.64. 2 / 52.64. 2
  
    libavdevice   52. 2. 0 / 52. 2. 0
  
    libavfilter    1.19. 0 /  1.19. 0
  
    libswscale     0.11. 0 /  0.11. 0
  
    libpostproc   51. 2. 0 / 51. 2. 0
  
  Input #0, avi, from '1.avi':
  
    Duration: 00:02:35.39, start: 0.000000, bitrate: 110595 kb/s
  
      Stream #0.0: Video: rawvideo, bgr24, 640x480, 15 tbr, 15 tbn, 15 tbc
  
  At least one output file must be specified

  I do not see anything wrong here, but I thought maybe someone will.

  I really need this to work soon, and right now it's a dead end...

  thanks

  [EDIT 2]

  I have just read this in the book OpenCV 2 Computer Vision Application Programming Cookbook by R. Laganiere :

  It is important to note that in order to open the specified video
  file, your computer must have the corresponding codec installed,
  otherwise cv::VideoCapture will not be able to understand the input
  file. Normally, if you are able to open your video file with a video
  player on your machine (such as the Windows Media Player), then OpenCV
  should also be able to read this file.

  Well, on my machine it is not that easy mister Laganiere... I hate this book.

• ffmpeg API h264 encoded video does not play on all platforms

  19 juillet 2012, par TheSHEEEP

  Edit : In the previous version I used a very old ffmpeg API. I now use the newest libraries. The problem has only changed slightly, from "Main" to "High".

  I am using the ffmpeg C API to create a mp4 video in C++.

  I want the resulting video to be of the profile "Constrained Baseline", so that the resulting video can be played on as much platforms as possible, especially mobile, but I get "High" profile every time, even though I hard coded the codec profile to be FF_PROFILE_H264_CONSTRAINED_BASELINE. As a result, the video does not play on all our testing platforms.

  This is what "ffprobe video.mp4 -show_streams" tells about my video streams :

    Metadata:
  
  major_brand     : isom
  
  minor_version   : 512
  
  compatible_brands: isomiso2avc1mp41
  
  creation_time   : 1970-01-01 00:00:00
  
  encoder         : Lavf53.5.0
  
    Duration: 00:00:13.20, start: 0.000000, bitrate: 553 kb/s
  
  Stream #0:0(und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p, 320x180,
  
  424 kb/s, 15 fps, 15 tbr, 15 tbn, 30 tbc
  
  Metadata:
  
    creation_time   : 1970-01-01 00:00:00
  
    handler_name    : VideoHandler
  
  Stream #0:1(und): Audio: aac (mp4a / 0x6134706D), 44100 Hz, stereo, s16, 12
  
  kb/s
  
  Metadata:
  
    creation_time   : 1970-01-01 00:00:00
  
    handler_name    : SoundHandler
  
  -------VIDEO STREAM--------
  
  [STREAM] 
  
  index=0
  
  codec_name=h264
  
  codec_long_name=H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10
  
  
  
  profile=High <-- This should be "Constrained Baseline"
  
  
  
  codec_type=video
  
  codec_time_base=1/30
  
  codec_tag_string=avc1
  
  codec_tag=0x31637661
  
  width=320
  
  height=180
  
  has_b_frames=0
  
  sample_aspect_ratio=N/A
  
  display_aspect_ratio=N/A
  
  pix_fmt=yuv420p
  
  level=30
  
  timecode=N/A
  
  is_avc=1
  
  nal_length_size=4
  
  id=N/A
  
  r_frame_rate=15/1
  
  avg_frame_rate=15/1
  
  time_base=1/15
  
  start_time=0.000000
  
  duration=13.200000
  
  bit_rate=424252
  
  nb_frames=198
  
  nb_read_frames=N/A
  
  nb_read_packets=N/A
  
  TAG:creation_time=1970-01-01 00:00:00
  
  TAG:language=und
  
  TAG:handler_name=VideoHandler
  
  [/STREAM]
  
  -------AUDIO STREAM--------
  
  [STREAM]
  
  index=1
  
  codec_name=aac
  
  codec_long_name=Advanced Audio Coding
  
  profile=unknown
  
  codec_type=audio
  
  codec_time_base=1/44100
  
  codec_tag_string=mp4a
  
  codec_tag=0x6134706d
  
  sample_fmt=s16
  
  sample_rate=44100
  
  channels=2
  
  bits_per_sample=0
  
  id=N/A
  
  r_frame_rate=0/0
  
  avg_frame_rate=0/0
  
  time_base=1/44100
  
  start_time=0.000000
  
  duration=13.165714
  
  bit_rate=125301
  
  nb_frames=567
  
  nb_read_frames=N/A
  
  nb_read_packets=N/A
  
  TAG:creation_time=1970-01-01 00:00:00
  
  TAG:language=und
  
  TAG:handler_name=SoundHandler
  
  [/STREAM]

  This is the function I use to add a video stream. All the values that come from ptr-> are defined from outside, do those values have to be specific values to get the correct profile ? :

  static AVStream *add_video_stream( Cffmpeg_dll * ptr, AVFormatContext *oc, enum   CodecID codec_id )
  
  {
  
  AVCodecContext *c;
  
  AVStream *st;  
  
  AVCodec* codec;
  
  
  
  // Get correct codec
  
  codec = avcodec_find_encoder(codec_id);
  
  if (!codec) {
  
      av_log(NULL, AV_LOG_ERROR, "%s","Video codec not found\n");
  
      exit(1);
  
  }
  
  
  
  // Create stream
  
  st = avformat_new_stream(oc, codec);
  
  if (!st) {
  
      av_log(NULL, AV_LOG_ERROR, "%s","Could not alloc stream\n");
  
      exit(1);
  
  }
  
  
  
  c = st->codec;
  
  
  
  /* Get default values */
  
  codec = avcodec_find_encoder(codec_id);
  
  if (!codec) {
  
      av_log(NULL, AV_LOG_ERROR, "%s","Video codec not found (default values)\n");
  
      exit(1);
  
  }
  
  avcodec_get_context_defaults3(c, codec);
  
  
  
  c->codec_id = codec_id;
  
  c->codec_type = AVMEDIA_TYPE_VIDEO;
  
  
  
  c->bit_rate = ptr->video_bit_rate;
  
  av_log(NULL, AV_LOG_ERROR, " Bit rate: %i", c->bit_rate);
  
  
  
      c->qmin = ptr->qmin;
  
      c->qmax = ptr->qmax;
  
      c->me_method = ptr->me_method;
  
      c->me_subpel_quality = ptr->me_subpel_quality;
  
      c->i_quant_factor = ptr->i_quant_factor;
  
      c->qcompress = ptr->qcompress;
  
      c->max_qdiff = ptr->max_qdiff;
  
  
  
      // We need to set the level and profile to get videos that play (hopefully) on all platforms
  
      c->level = 30;
  
      c->profile = FF_PROFILE_H264_CONSTRAINED_BASELINE;
  
  
  
  c->width = ptr->dstWidth; 
  
  c->height = ptr->dstHeight; 
  
  
  
  c->time_base.den = ptr->fps;
  
  c->time_base.num = 1;
  
  c->gop_size = ptr->fps;
  
  c->pix_fmt = STREAM_PIX_FMT;
  
  c->max_b_frames = 0;
  
  
  
  // some formats want stream headers to be separate
  
  if(oc->oformat->flags & AVFMT_GLOBALHEADER)
  
      c->flags |= CODEC_FLAG_GLOBAL_HEADER;
  
  
  
  return st;
  
  }

  Additional info :

  As a reference video, I use the gizmo.mp4 that Mozilla serves as an example that plays on every platform/browser. It definitely has the "Constrained Baseline" profile, and definitely works on all our testing smartphones. You can download it here. Our self-created video doesn't work on all platforms and I'm convinced this is because of the profile.

  I am also using qt-faststart.exe to move the headers to the start of the file after creating the mp4, as this cannot be done in a good way in C++ directly. Could that be the problem ?

  Obviously, I am doing something wrong, but I don't know what it could be. I'd be thankful for every hint ;)