Recherche avancée

Sur d’autres sites (5341)

• RaspberryPi HQ camera not working with FFMPEG [closed]

  12 mars 2024, par GeeTee

  I just want to prefix this by saying I'm still quite fresh to linux so please bare with me as I don't always know exactly what I'm looking at.

  


  Hardware : Raspberry Pi 5 4GB / Pi HQ camera (connected with adapter cable)
OS : Debain V12 (bookworm)
FFMPEG : ffmpeg version 5.1.4-0+rpt3+deb12u1
I2C = Enabled
X / Wayland : Wayland (had to use this for VNC)

  


  I know the camera works as : when I use rpicam-vid -t 0 I have a working preview without issue (albeit slightly stuttery)

  


  When I try to enter ffmpeg -f v4l2 -i /dev/video0 I get the following :
(with the goal of having some video in a preview window)

  


  [video4linux2,v4l2 @ 0x5555a0811a20] ioctl(VIDIOC_G_PARM): Inappropriate ioctl for device
[video4linux2,v4l2 @ 0x5555a0811a20] Time per frame unknown
[video4linux2,v4l2 @ 0x5555a0811a20] ioctl(VIDIOC_STREAMON): Invalid argument
/dev/video0: Invalid argument


  


  I have also tried ffplay -f v4l2 -i /dev/video0 and get the same error as above.

  


  Following other forums I've tried (I'm not sure this is all necessary but to cover all bases, and save time) :

  


  Prompt : ffmpeg -sources device /dev/video0
Out : none (as in libpostproc    56.  6.100 / 56.  6.100 is the last line)

  


  Promt : v4l2-ctl --list-devices
Out :

  


  pispbe (platform:1000880000.pisp_be):
    /dev/video20
    /dev/video21
    /dev/video22
    /dev/video23
    /dev/video24
    /dev/video25
    /dev/video26
    /dev/video27
    /dev/video28
    /dev/video29
    /dev/video30
    /dev/video31
    /dev/video32
    /dev/video33
    /dev/video34
    /dev/video35
    /dev/video36
    /dev/video37
    /dev/media1
    /dev/media2

rp1-cfe (platform:1f00110000.csi):
    /dev/video0
    /dev/video1
    /dev/video2
    /dev/video3
    /dev/video4
    /dev/video5
    /dev/video6
    /dev/video7
    /dev/media0

rpivid (platform:rpivid):
    /dev/video19
    /dev/media3


  


  (seems to me rp1-cfe is what I want / need ? which is good that it shows up ?)

  


  Prompt : strace cat /dev/video0
Out :

  


  execve("/usr/bin/cat", ["cat", "/dev/video0"], 0x7fffc4c80c38 /* 41 vars */) = 0
brk(NULL)                               = 0x55567d41c000
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=80471, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 80471, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fff59df4000
close(3)                                = 0
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0py\2\0\0\0\0\0"..., 832) = 832
newfstatat(3, "", {st_mode=S_IFREG|0755, st_size=1651472, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 1826976, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fff59c34000
mmap(0x7fff59c40000, 1761440, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0) = 0x7fff59c40000
munmap(0x7fff59c34000, 49152)           = 0
munmap(0x7fff59df0000, 8352)            = 0
mprotect(0x7fff59dc8000, 81920, PROT_NONE) = 0
mmap(0x7fff59ddc000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x18c000) = 0x7fff59ddc000
mmap(0x7fff59de4000, 41120, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fff59de4000
close(3)                                = 0
set_tid_address(0x7fff59e4b010)         = 1526021
set_robust_list(0x7fff59e4b020, 24)     = 0
rseq(0x7fff59e4b660, 0x20, 0, 0xd428bc00) = 0
mprotect(0x7fff59ddc000, 16384, PROT_READ) = 0
mprotect(0x5556410fc000, 16384, PROT_READ) = 0
mprotect(0x7fff59e44000, 16384, PROT_READ) = 0
prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0
munmap(0x7fff59df4000, 80471)           = 0
getrandom("\x5c\x96\x77\x22\xd2\x25\xd3\x23", 8, GRND_NONBLOCK) = 8
brk(NULL)                               = 0x55567d41c000
brk(0x55567d440000)                     = 0x55567d440000
openat(AT_FDCWD, "/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
newfstatat(3, "", {st_mode=S_IFREG|0644, st_size=3048976, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 3048976, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fff59954000
close(3)                                = 0
newfstatat(1, "", {st_mode=S_IFCHR|0620, st_rdev=makedev(0x88, 0x1), ...}, AT_EMPTY_PATH) = 0
openat(AT_FDCWD, "/dev/video0", O_RDONLY) = 3
newfstatat(3, "", {st_mode=S_IFCHR|0660, st_rdev=makedev(0x51, 0x13), ...}, AT_EMPTY_PATH) = 0
fadvise64(3, 0, 0, POSIX_FADV_SEQUENTIAL) = 0
mmap(NULL, 163840, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7fff5992c000
read(3, 0x7fff59930000, 131072)         = -1 EINVAL (Invalid argument)
write(2, "cat: ", 5cat: )                    = 5
write(2, "/dev/video0", 11/dev/video0)             = 11
openat(AT_FDCWD, "/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 4
newfstatat(4, "", {st_mode=S_IFREG|0644, st_size=2996, ...}, AT_EMPTY_PATH) = 0
read(4, "# Locale name alias data base.\n#"..., 4096) = 2996
read(4, "", 4096)                       = 0
close(4)                                = 0
openat(AT_FDCWD, "/usr/share/locale/en_GB.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_GB.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en_GB/LC_MESSAGES/libc.mo", O_RDONLY) = 4
newfstatat(4, "", {st_mode=S_IFREG|0644, st_size=1433, ...}, AT_EMPTY_PATH) = 0
mmap(NULL, 1433, PROT_READ, MAP_PRIVATE, 4, 0) = 0x7fff59e34000
close(4)                                = 0
openat(AT_FDCWD, "/usr/share/locale/en.UTF-8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en.utf8/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/usr/share/locale/en/LC_MESSAGES/libc.mo", O_RDONLY) = -1 ENOENT (No such file or directory)
write(2, ": Invalid argument", 18: Invalid argument)      = 18
write(2, "\n", 1
)                       = 1
munmap(0x7fff5992c000, 163840)          = 0
close(3)                                = 0
close(1)                                = 0
close(2)                                = 0
exit_group(1)                           = ?
+++ exited with 1 +++


  


  (no idea what I'm reading here and if it's good or bad so I included it all)

  


  Prompt : ffmpeg -f v4l2 -list_formats all -i /dev/video0
Out :

  


  [video4linux2,v4l2 @ 0x55561cd9da20] Raw       :     yuyv422 :           YUYV 4:2:2 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :     uyvy422 :           UYVY 4:2:2 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported :           YVYU 4:2:2 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported :           VYUY 4:2:2 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :    rgb565le :     16-bit RGB 5-6-5 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :    rgb565be :  16-bit RGB 5-6-5 BE : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :    rgb555le : 16-bit A/XRGB 1-5-5-5 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :    rgb555be : 16-bit A/XRGB 1-5-5-5 BE : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :       rgb24 :     24-bit RGB 8-8-8 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :       bgr24 :     24-bit BGR 8-8-8 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :        0rgb : 32-bit A/XRGB 8-8-8-8 : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : bayer_bggr8 : 8-bit Bayer BGBG/GRGR : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : bayer_gbrg8 : 8-bit Bayer GBGB/RGRG : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : bayer_grbg8 : 8-bit Bayer GRGR/BGBG : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : bayer_rggb8 : 8-bit Bayer RGRG/GBGB : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 10-bit Bayer BGBG/GRGR Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 10-bit Bayer GBGB/RGRG Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 10-bit Bayer GRGR/BGBG Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 10-bit Bayer RGRG/GBGB Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 12-bit Bayer BGBG/GRGR Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 12-bit Bayer GBGB/RGRG Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 12-bit Bayer GRGR/BGBG Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 12-bit Bayer RGRG/GBGB Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 14-bit Bayer BGBG/GRGR Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 14-bit Bayer GBGB/RGRG Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 14-bit Bayer GRGR/BGBG Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 14-bit Bayer RGRG/GBGB Packed : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 16-bit Bayer BGBG/GRGR : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 16-bit Bayer GBGB/RGRG : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 16-bit Bayer GRGR/BGBG : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 16-bit Bayer RGRG/GBGB : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Compressed: Unsupported : PiSP Bayer Compressed Format : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Compressed: Unsupported : PiSP Bayer Compressed Format : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Compressed: Unsupported : PiSP Bayer Compressed Format : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Compressed: Unsupported : PiSP Bayer Compressed Format : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :        gray :      8-bit Greyscale : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 10-bit Greyscale (MIPI Packed) : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 12-bit Greyscale (MIPI Packed) : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       : Unsupported : 14-bit Greyscale (MIPI Packed) : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Raw       :    gray16le :     16-bit Greyscale : {16-16384, 2}x{16-16384, 1}
[video4linux2,v4l2 @ 0x55561cd9da20] Compressed: Unsupported : PiSP Bayer Compressed Format : {16-16384, 2}x{16-16384, 1}
/dev/video0: Immediate exit requested


  


  Not sure why so many of these are unsupported, I saw a video on YouTube with the same camera and older Pi and he did not have so many unsupported.

  


  Also, I ran the config file in the ffmpeg directory and I think it generated some additional files (wasn't working before either) are these normal ? (ffmpeg $ ls)

  


  Changelog        COPYING.LGPLv2.1  INSTALL.md   libpostproc    presets
compat           COPYING.LGPLv3    libavcodec   libswresample  README.md
configure        CREDITS           libavdevice  libswscale     RELEASE
CONTRIBUTING.md  doc               libavfilter  LICENSE.md     tests
COPYING.GPLv2    ffbuild           libavformat  MAINTAINERS    tools
COPYING.GPLv3    fftools           libavutil    Makefile


  


  A side question : How do I enable and disable libraries ? I tried entering —enable-pulse for example (with and without spaces and prefixed by ffmpeg) but get an error along the lines of unrecognised option or command not found. (I've tried google but as mentioned prior, I'm a bit lost)

  


  Thanks in advance.

  


• Fintech Content Marketing : 10 Best Practices & Growth Strategies

  24 juillet 2024, par Erin

  Content marketing is an effective strategy for growth and building trust. This is especially true in the fintech industry, where competition is intense and trust is crucial. Content marketing helps you strengthen customer relationships, engage your audience, and differentiate yourself from competitors.

  To get the most out of your fintech content marketing, you need to develop the right strategy.

  In this guide, we’ll cover everything you need to know about content marketing for fintech companies so you can expand your reach and grow your business.

  What is fintech content marketing ?

  Fintech content marketing is creating content around financial topics on the internet to attract, engage, and convert audiences.

  Fintech companies can use a content strategy to drive leads by creating educational content.

  

  While financial content is important, it’s easy for it to feel boring, unrelatable, or confusing. But, when done right, fintech companies can educate their audiences with great content marketing that helps their audience understand financial topics in-depth.

  Fintech companies can create written, audio, or video content to inform their audiences about financial topics they’re interested in.

  From there, each piece of content can then be distributed to different mediums :

  • Blogs
  • Website
  • Facebook
  • YouTube
  • Instagram
  • Other websites
  • Apps
  • And more

  Once content is distributed, fintech companies can then analyse how effective the content is by tracking web analytics data like search engine traffic, social media engagement, and new customers.

  7 reasons fintech companies need content marketing

  Before we dive into fintech content marketing best practices, let’s recap why fintech companies need to lean into content to grow their business.

  Here are seven reasons your financial company needs to deploy a robust content strategy :

  

  1. Reach new audiences

  If you want to grow your fintech company, you need to find new customers. Creating content is a proven path to marketing yourself online and attracting a larger audience.

  By using search engine optimisation (SEO), social media marketing, and YouTube, you can expand your audience and grow your customer base.

  With content marketing, you can find new audiences without needing a massive budget, making scaling easier.

  2. Engage current audience

  While content can be a powerful method to reach new customers, it isn’t the only thing it’s good for.

  If you want to grow your business, another way to leverage your content is to keep your current audience engaged.

  You can create financial content to educate, inform, and add value to your current audience who already knows you. Repurposing content between the different platforms your audience is on keeps them engaged with you and your brand.

  It’s a simple way to capture and keep the attention of your audience, build trust, and convert more prospects into customers.

  3. Build relationships with customers

  You should leverage content marketing in various spaces, such as social media, your website, a blog, or even YouTube. Creating content on different channels allows you to build relationships with your customers on autopilot.

  The general rule in marketing is that the more touch points you have with your customers, the more you’ll sell. Creating more content means you always have new opportunities to increase those touchpoints, build deeper relationships, and sell more.

  4. Grow authority in a space

  If you want people to trust you and your financial tech, you need to be seen as an authority. How can someone trust that your app or web platform will help them with their finances if they don’t trust you’re a financial expert ?

  You should use informative content to become a thought leader in your space. You can post content on social media or your own platforms.

  You can also spread your authority by leveraging other brands’ or influencers’ audiences through guest blog posting and guest podcasting.

  5. Drive new leads

  Content marketing isn’t just a fun hobby for businesses. It’s one of the smartest ways to drive new leads.

  You should be crafting content for your top-of-funnel marketing strategy to attract potential customers.

  Creating content consistently is a great way to bring in new audience members into your funnel.

  Once you grow your top-of-funnel audience, you can convert them into leads by getting them to join your email list or trial your financial software.

  One tip to get more out of your content strategy is creating evergreen content to continually drive leads. For example, create “set-it-and-forget it” blog posts or YouTube videos that will continue working for you daily to attract new audience members searching for helpful financial information. Then, provide a call to action on that content to join your email list (by leveraging a lead magnet).

  6. Convert prospects to customers

  When you have a continual flow of new top-of-funnel prospects, you always have a fresh cycle of prospects you can convert into customers.

  Content is primarily used to attract new audience members and engage your current audience at the top of your funnel. But it can also be used to convert your audience into customers.

  Try mixing up your content types to drive conversions :

  • Educational
  • Entertaining
  • Promotional

  Don’t just show off educational content.

  You should also mix in “authority” content by displaying case studies of user success stories and calling to action to sign up for a free trial or request a demo.

  7. Lower Customer Acquisition Cost (CAC)

  On the business side, if you want a marketing strategy that will keep expenses low long term, you’ll want to invest more in content.

  Content marketing has a great return on investment (ROI) for your time and effort.

  Why ?

  Because the customer acquisition costs (CAC) are so low.

  You can create content that can bring in leads for months if not years.

  If you only use Google or Facebook ads to drive new leads, you always have to “pay-to-play.” When you turn the advertising tap off, your leads dry up.

  But, with blogs and videos, you can create content that can bring in organic customers on repeat. It’s like a snowball effect that keeps going long after you’ve completed the initial work.

  10 fintech content marketing best practices

  Here are ten best practices to establish a strong content marketing strategy as a fintech company :

  

  1. Set SMART goals

  A good content strategy starts with goal-setting. You’ll never get there if you don’t know where you’re going.

  To make sure your fintech content marketing strategy is a success, you need to set SMART goals :

  • Specific
  • Measurable
  • Achievable
  • Relevant
  • Time-bound

  For example, you might set a goal to reach 20,000 blog visits in one year and convert blog visits at a rate of 3%.

  Setting clear content goals will streamline operations, so you stay consistent and get the most out of your efforts.

  3. Be transparent

  Transparency is crucial for fintech companies, as they handle sensitive financial data and, in many cases, monetary transactions.

  It’s essential for you to be open and clear about your products, services, and data practices. By being honest about privacy and security measures, fintechs can build and maintain trust with their customers.

  This transparency not only helps in establishing credibility but also ensures customers feel confident about how their financial information is managed and protected.

  

  4. Take an education-first approach

  Content isn’t just about “hooking” or entertaining your audience. That’s just one aspect of a content strategy.

  The best approach to building authority and converting leads from your content is to take an education-first approach.

  Remember above, when we touched on understanding your ICP ? You need to know your ICP’s interests and pain points inside and out and then map your product’s strengths to those that are relevant.

  Always start with your ICP, then build the content strategy around them based on your product.

  Find connections and identify how your product can address the ICP’s interests and pain points.

  For example, let’s say your ICPs are Gen Z consumers. They’re interested in independence and saving for future goals. Their pain points might include lack of investment knowledge and managing student debts and other loans.

  Let’s say your product is a personal finance app. Some of your benefits might be budget tracking and beginner-friendly investment options. You could create a content strategy around budgeting in your 20s and investing for beginners.

  Content strategies will vary widely based on your ICP. For instance, content for a fintech company targeting those approaching retirement will need a different focus compared to that aimed at younger consumers.

  Remember : practical, step-by-step, value-driven content performs best regarding conversions.

  5. Leverage the right tools

  If you’re going to succeed with content, you need to lean on the right tools.

  Here are a few types of tools you should consider (and recommendations) :

  • Project management (i.e., Asana)
  • Content management system (i.e., WordPress)
  • Content scheduling (i.e., Hootsuite)
  • Design (i.e., Canva)
  • SEO (i.e., Ahrefs)
  • Web analytics (i.e., Matomo)

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  6. Promote your content on different platforms

  You’ll want to promote your fintech content marketing strategy on different channels and platforms to get the most out of your fintech content marketing strategy.

  Start with one core platform before you pick a few platforms to promote your content. You should leverage at least one social media platform.

  Then, create a blog and an email newsletter to ensure you create multiple touchpoints.

  Here are some tips on how to pick the right platform :

  • Consider age range (i.e. TikTok for a younger audience, Facebook for an older audience)
  • Consider your preferred content type (YouTube for long-form video, X for short-form written content
  • Consider your competition (i.e. go where competitive fintech companies already are)

  7. Track results 

  How do you know if you’re on pace to reach the SMART goals you set earlier ?

  By tracking your results. 

  You should dive into your data regularly to ensure your content is working. Make sure to track social media, email marketing, and web results.

  Keep a close eye on your website KPIs and track your conversions to ensure a return on investment (ROI). For more detailed guidance on monitoring your website’s performance, check out our blog on how to check website traffic as accurately as possible.

  Remember, a data-driven approach is the best way to stay on track with your content goals.

  8. Establish a content leader

  Your content marketing needs a leader. You should establish someone on your marketing team to oversee your content plan. 

  They should ensure they collaborate well with different teams, understand social media and SEO, and know how to manage projects.

  Most of all, don’t forget that they’re in charge of tracking your data and reporting to higher-ups, so they should be comfortable with web analytics and know how to track performance well.

  9. Optimise for SEO

  It’s not enough to create a weekly blog post. You could craft the most valuable content on your website, but nobody will find it online if it isn’t optimised for SEO.

  Your content leader should analyse SEO data using a tool like Ahrefs or SEMrush to analyse different keywords to target in your content. 

  A web analytics tool like Matomo can then be used to track results. Matomo offers traditional web analytics, including pageviews, bounce rate, and sources of traffic, alongside features like heatmaps, session recordings, and A/B testing.

  These advanced features provide deeper insights into how users interact with your site and content, helping you pinpoint areas for improvement. Improving the user experience based on these insights can then positively impact your Google rankings.

  Try Matomo for Free

  Get the web insights you need, without compromising data accuracy.

  Start for free

  No credit card required

  10. Stay compliant

  Fintech is a highly regulated industry. Keeping this in mind, you need to ensure you take the necessary steps to ensure you remain compliant with all applicable laws and regulations.

  Non-compliance can result in severe penalties.

  Given these high standards, it’s crucial to ensure that user data remains private and secure. Matomo helps with this by providing a compliant web analytics solution that respects user privacy. With Matomo, you can confidently manage compliance and build trust with your customers while also reliably tracking the performance of your content marketing.

  

  Drive your content marketing strategy with Matomo

  Leaning into content marketing can be one of the best ways your fintech company can attract, engage, convert, and retain your audience.

  By creating high-quality content for your audience on social media, YouTube, and your website, you can establish your brand as an authority to grow your business for years to come.

  But remember, you need to make sure you’re only using privacy-friendly, compliant tools to protect your audience’s data.

  Thankfully, Matomo has you covered.

  As a privacy-friendly web analytics tool, Matomo ensures that your website data is tracked and stored in compliance with privacy laws.

  Trusted by over 1 million websites, it offers reliable data without sampling, guaranteeing accuracy. Matomo is designed to be fully compliant with privacy regulations such as GDPR and CCPA, while also providing advanced features like heatmaps, session recordings, and A/B testing to help you track and enhance your website’s performance.

  Request a demo to see how Matomo can benefit your fintech business now.

  Try Matomo for Free

  21 day free trial. No credit card required.

  
  

  Your email address
  

  Your website address
  

  Your Analytics subdomain will be .matomo.cloud (change)

  Choose your analytics subdomain
  

  .matomo.cloud

  I accept the terms and conditions and data processing agreement (DPA)

  
  Your information will be used to create an account on our cloud service. For more information please consult our privacy policy.
  
  
  

  Start improving your websites now

  

• A Quick Start Guide to the Payment Services Directive (PSD2)

  22 novembre 2024, par Daniel Crough — Banking and Financial Services, Privacy

  In 2023, there were 266.2 billion real-time payments indicating that the demand for secure transactions has never been higher. As we move towards a more open banking system, there are a host of new payment solutions that offer convenience and efficiency, but they also present new risks.

  The Payment Services Directive 2 (PSD2) is one of many regulations established to address these concerns. PSD2 is a European Union (EU) business initiative to offer smooth payment experiences while helping customers feel safe from online threats. 

  In this post, learn what PSD2 includes, how it improves security for online payments, and how Matomo supports banks and financial institutions with PSD2 compliance.

  What is PSD2 ? 

  PSD2 is an EU directive that aims to improve the security of electronic payments across the EU. It enforces strong customer authentication and allows third-party access to consumer accounts with explicit consent. 

  Its main objectives are :

  • Strengthening security and data privacy measures around digital payments.
  • Encouraging innovation by allowing third-party providers access to banking data.
  • Improving transparency with clear communication regarding fees, terms and conditions associated with payment services.
  • Establishing a framework for sharing customer data securely through APIs for PSD2 open banking.

  Rationale behind PSD2 

  PSD2’s primary purpose is to engineer a more integrated and efficient European payment market without compromising the security of online transactions. 

  The original directive aimed to standardise payment services across EU member states, but as technology evolved, an updated version was needed.

  PSD2 is mandatory for various entities within the European Economic Area (EEA), like :

  • Banks and credit institutions
  • Electronic money institutions or digital banks like Revolut
  • Card issuing and acquiring institutions
  • Fintech companies
  • Multi-national organisations operating in the EU

  PSD2 implementation timeline

  With several important milestones, PSD2 has reshaped how payment services work in Europe. Here’s a closer look at the pivotal events that paved the way for its launch.

  • 2002 : The banking industry creates the European Payments Council (EC), which drives the Single Euro Payments Area (SEPA) initiative to include non-cash payment instruments across European regions. 
  • 2007 : PSD1 goes into effect.
  • 2013 : EC proposes PSD2 to include protocols for upcoming payment services.
  • 2015 : The Council of European Union passes PSD2 and gives member states two years to incorporate it.
  • 2018 : PSD2 goes into effect. 
  • 2019 : The final deadline for all companies within the EU to comply with PSD2’s regulations and rules for strong customer authentication. 

  PSD2 : Key components 

  PSD2 introduces several key components. Let’s take a look at each one.

  Strong Customer Authentication (SCA)

  The Regulatory Technical Standards (RTS) under PSD2 outline specific requirements for SCA. 

  SCA requires multi-factor authentication for online transactions. When customers make a payment online, they need to verify their identity using at least two of the three following elements :

  • Knowledge : Something they know (like a password, a code or a secret answer)
  • Possession : Something they have (like their phone or card)
  • Inherence : Something they are (like biometrics — fingerprints or facial features)

  

  Before SCA, banks verified an individual’s identity only using a password. This dual verification allows only authorised users to complete transactions. SCA implementation reduces fraud and increases the security of electronic payments.

  SCA implementation varies for different payment methods. Debit and credit cards use the 3D Secure (3DS) protocol. E-wallets and other local payment measures often have their own SCA-compliant steps. 

  3DS is an extra step to authenticate a customer’s identity. Most European debit and credit card companies implement it. Also, in case of fraudulent chargebacks, the issuing bank becomes liable due to 3DS, not the business. 

  However, in SCA, certain transactions are exempt : 

  • Low-risk transactions : A transaction by an issuer or an acquirer whose fraud level is below a specific threshold. If the acquirer feels that a transaction is low risk, they can request to skip SCA. 
  • Low-value transactions : Transactions under €30.
  • Trusted beneficiaries : Trusted merchants customers choose to safelist.
  • Recurring payments : Recurring transactions for a fixed amount are exempt from SCA after the first transaction.

  Third-party payment service providers (TPPs) framework

  TPPs are entities authorised to access customer banking data and initiate payments. There are three types of TPPs :

  Account Information Service Providers (AISPs)

  AISPs are services that can view customers’ account details, but only with their permission. For example, a budgeting app might use AISP services to gather transaction data from a user’s bank account, helping them monitor expenses and oversee finances. 

  Payment Initiation Service Providers (PISPs)

  PISPs enable clients to initiate payments directly from their bank accounts, bypassing the need for conventional payment options such as debit or credit cards. After the customer makes a payment, PISPs immediately contact the merchant to ensure the user can access the online services or products they bought. 

  Card-Based Payment Instruments (CBPII)

  CBPIIs refer to services that issue payment cards linked to customer accounts. 

  Requirements for TPPs

  To operate effectively under PSD2, TPPs must meet several requirements :

  Consumer consent : Customers must explicitly authorise TPPs to retrieve their financial data. This way, users can control who can view their information and for what purpose.

  Security compliance : TPPs must follow SCA and secure communication guidelines to protect users from fraud and unauthorised access.

  API availability : Banks must make their Application Programming Interfaces (APIs) accessible and allow TPPs to connect securely with the bank’s systems. This availability helps in easy integration and lets TPPs access essential data. 

  Consumer protection methods

  PSD2 implements various consumer protection measures to increase trust and transparency between consumers and financial institutions. Here’s a closer look at some of these key methods :

  • Prohibition of unjustified fees : PSD2 requires banks to clearly communicate any additional charges or fees for international transfers or account maintenance. This ensures consumers are fully aware of the actual costs and charges.
  • Timely complaint resolution : PSD2 mandates that payment service providers (PSPs) have a straightforward complaint procedure. If a customer faces any problems, the provider must respond within 15 business days. This requirement encourages consumers to engage more confidently with financial services.
  • Refund in case of unauthorised payment : Customers are entitled to a full refund for payments made without their consent.
  • Surcharge ban : Additional charges on credit and debit card payments aren’t allowed. Businesses can’t impose extra fees on these payment methods, which increases customers’ purchasing power.

  Benefits of PSD2 

  Businesses — particularly those in banking, fintech, finserv, etc. — stand to benefit from PSD2 in several ways.

  Access to customer data

  With customer consent, banks can analyse spending patterns to develop tailored financial products that match customer needs, from personalised savings accounts to more relevant loan offerings.

  Innovation and cost benefits 

  PSD2 opened payment processing up to more market competition. New payment companies bring fresh approaches to banking services, making daily transactions more efficient while driving down processing fees across the sector.

  Also, banks now work alongside payment technology providers, combining their strengths to create better services. This collaboration brings faster payment options to businesses, helping them stay competitive while reducing operational costs.

  Improved customer trust and experience

  Due to PSD2 guidelines, modern systems handle transactions quickly without compromising the safety of payment data, creating a balanced approach to digital banking.

  

  Banking customers now have more control over their financial information. Clear processes allow consumers to view and adjust their financial preferences as needed.

  Strong security standards form the foundation of these new payment systems. Payment provider platforms must adhere to strict regulations and implement additional protection measures.

  Challenges in PSD2 compliance 

  What challenges can banks and financial institutions face regarding PSD2 compliance ? Let’s examine them. 

  Resource requirements

  For many businesses, the new requirements come with a high price tag. PSD2 requires banks and fintechs to build and update their systems so that other providers can access customer data safely. For example, they must develop APIs to allow TPPs to acquire customer data. 

  Many banks still use older systems that can’t meet PSD2’s added requirements. In addition to the cost of upgrades, complying with PSD2 requires banks to devote resources to training staff and monitoring compliance.

  The significant costs required to update legacy systems and IT infrastructure while keeping services running remain challenging.

  Risks and penalties

  Organisations that fail to comply with PSD2 regulations can face significant penalties.

  Additionally, the overlapping requirements of PSD2 and other regulations, such as the General Data Protection Regulation (GDPR), can create confusion. 

  Banks need clear agreements with TPPs about who’s responsible when things go wrong. This includes handling data breaches, preventing data misuse and protecting customer information. 

  Increased competition 

  Introducing new players in the financial ecosystem, such as AISPs and PISPs, creates competition. Banks must adapt their services to stay competitive while managing compliance costs.

  PSD2 aims to protect customers but the stronger authentication requirements can make banking less convenient. Banks must balance security with user experience. Focused time, effort and continuous monitoring are needed for businesses to stay compliant and competitive.

  How Matomo can help 

  Matomo gives banks and financial institutions complete control over their data through privacy-focused web analytics, keeping collected information internal rather than being used for marketing or other purposes. 

  Its advanced security setup includes access controls, audit logs, SSL encryption, single sign-on and two-factor authentication. This creates a secure environment where sensitive data remains accessible only to authorised staff.

  While prioritizing privacy, Matomo provides tools to understand user flow and customer segments, such as session recordings, heatmaps and A/B testing.

  Financial institutions particularly benefit from several key features : 

  • Tools for obtaining explicit consent before processing personal data like this Do Not Track preference
  • Insights into how financial institutions integrate TPPs (including API usage, user engagement and potential authentication drop-off points)
  • Tracking of failed login attempts or unusual access patterns
  • IP anonymization to analyse traffic patterns and detect potential fraud

  

  PSD3 : The next step 

  In recent years, we have seen the rise of innovative payment companies and increasingly clever fraud schemes. This has prompted regulators to propose updates to payment rules.

  PSD3’s scope is to adapt to the evolving digital transformation and to better handle these fraud risks. The proposed measures : 

  • Encourage PSPs to share fraud-related information.
  • Make customers aware of the different types of fraud.
  • Strengthen customer authentication standards.
  • Provide non-bank PSPs restricted access to EU payment systems. 
  • Enact payment rules in a directly applicable regulation and harmonise and enforce the directive.

  Web analytics that respect user privacy 

  Achieving compliance with PSD2 may be a long road for some businesses. With Matomo, organisations can enjoy peace of mind knowing their data practices align with legal requirements.

  Ready to stop worrying over compliance with regulations like PSD2 and take control of your data ? Start your 21-day free trial with Matomo.