Enter password to view Website Audit
Analysis
Website
finperks
Analysis
Website
finperks
Analysis
Website
finperks
Summary
About
Company
finperks
Overall Score of Website
41
Analysed on 2026-03-18
Description
finperks is a Berlin-based B2B API infrastructure platform for the global prepaid market, enabling banks, fintechs, HR platforms, retailers, and crypto companies to offer gift cards, cashback, employee benefits, and prepaid wallets through a single API integration with 1,000+ brands across 30+ European markets. Founded in summer 2025 by the viafintech/Barzahlen team (Achim Bönsch, Sebastian Seifert, Andreas Veller — sold to NYSE-listed Paysafe in 2021). Raised €3.4M pre-seed from Motive Partners and seed+speed Ventures in March 2026. Live with FLIZpay, Recardy, and Paylo.
Market
Prepaid Infrastructure API / Gift Card Aggregation / Employee Benefits Platform / Fintech B2B Infrastructure
Audience
Head of Partnerships / Product at banks, fintechs, HR SaaS platforms, retailers, crypto companies seeking prepaid product infrastructure without building it themselves; technical evaluators (CTOs, developers) reviewing API capabilities
HQ
Berlin, Germany
Visualisation
Spider Chart
Copy
32
SEO
38
Brand
36
Performance
42
Copy
45
Social Proof
44
Copy
45
Copy
40
SEO
40
Copy
52
Copy
Stat Inconsistency on Same Page — Hero Carousel '1,000+ brands' vs Stats Section '700+ Brands'
Score
32
Severity
High
Finding
The homepage contains two different brand count figures displayed simultaneously. The hero brand carousel section states '700+ Brands' in the stats bar ('30+ Countries / 700+ Brands / <30 Days to Market'). However the 'Brands Overview' section heading reads 'Get Access to 700+ Brands' — confirming 700+ is the consistent internal figure. But the press releases from March 11, 2026 (EU-Startups, FinTech Global, The Next Web) all state 'over 1,000 brands across Europe.' The nav Resources section links to '/avaialble-brands' (which is itself a typo — see issue #2). The homepage therefore contains one internally consistent count (700+) that conflicts with every external press reference (1,000+). Either the number grew from 700 to 1,000+ between site creation and the pre-seed announcement — in which case the homepage hasn't been updated — or the press materials are rounding up aggressively.
Recommendation
Reconcile the brand count to a single verified figure and update all on-page references on the same day. If the count is now 1,000+ (as stated in the March 11 press release, just one week ago), update the homepage stats bar to '1,000+ Brands' and the Brands Overview section heading to 'Get Access to 1,000+ Brands.' This is the kind of discrepancy that a technical evaluator (a Head of Partnerships at a bank or fintech) will catch immediately when comparing the homepage to press coverage. For a company that just announced its funding and will drive traffic to this site from press articles, the numbers on the site and in the press should match from day one.
Copy
Stat Inconsistency on Same Page — Hero Carousel '1,000+ brands' vs Stats Section '700+ Brands'
Score
32
Severity
High
Finding
The homepage contains two different brand count figures displayed simultaneously. The hero brand carousel section states '700+ Brands' in the stats bar ('30+ Countries / 700+ Brands / <30 Days to Market'). However the 'Brands Overview' section heading reads 'Get Access to 700+ Brands' — confirming 700+ is the consistent internal figure. But the press releases from March 11, 2026 (EU-Startups, FinTech Global, The Next Web) all state 'over 1,000 brands across Europe.' The nav Resources section links to '/avaialble-brands' (which is itself a typo — see issue #2). The homepage therefore contains one internally consistent count (700+) that conflicts with every external press reference (1,000+). Either the number grew from 700 to 1,000+ between site creation and the pre-seed announcement — in which case the homepage hasn't been updated — or the press materials are rounding up aggressively.
Recommendation
Reconcile the brand count to a single verified figure and update all on-page references on the same day. If the count is now 1,000+ (as stated in the March 11 press release, just one week ago), update the homepage stats bar to '1,000+ Brands' and the Brands Overview section heading to 'Get Access to 1,000+ Brands.' This is the kind of discrepancy that a technical evaluator (a Head of Partnerships at a bank or fintech) will catch immediately when comparing the homepage to press coverage. For a company that just announced its funding and will drive traffic to this site from press articles, the numbers on the site and in the press should match from day one.
Copy
Stat Inconsistency on Same Page — Hero Carousel '1,000+ brands' vs Stats Section '700+ Brands'
Score
32
Severity
High
Finding
The homepage contains two different brand count figures displayed simultaneously. The hero brand carousel section states '700+ Brands' in the stats bar ('30+ Countries / 700+ Brands / <30 Days to Market'). However the 'Brands Overview' section heading reads 'Get Access to 700+ Brands' — confirming 700+ is the consistent internal figure. But the press releases from March 11, 2026 (EU-Startups, FinTech Global, The Next Web) all state 'over 1,000 brands across Europe.' The nav Resources section links to '/avaialble-brands' (which is itself a typo — see issue #2). The homepage therefore contains one internally consistent count (700+) that conflicts with every external press reference (1,000+). Either the number grew from 700 to 1,000+ between site creation and the pre-seed announcement — in which case the homepage hasn't been updated — or the press materials are rounding up aggressively.
Recommendation
Reconcile the brand count to a single verified figure and update all on-page references on the same day. If the count is now 1,000+ (as stated in the March 11 press release, just one week ago), update the homepage stats bar to '1,000+ Brands' and the Brands Overview section heading to 'Get Access to 1,000+ Brands.' This is the kind of discrepancy that a technical evaluator (a Head of Partnerships at a bank or fintech) will catch immediately when comparing the homepage to press coverage. For a company that just announced its funding and will drive traffic to this site from press articles, the numbers on the site and in the press should match from day one.
SEO
URL Typo: '/avaialble-brands' — 'Available' Misspelled in Production URL
Score
38
Severity
High
Finding
The Resources section of the navigation links to: https://finperks.com/avaialble-brands — with 'avaialble' as a misspelling of 'available' (letters transposed: 'avai-a-lble' instead of 'available'). This is a live production URL with a typo in the path segment. The consequences: (1) any external site linking to /available-brands (the correct spelling) will 404; (2) Google may index both /avaialble-brands and any corrected /available-brands creating a duplicate content split; (3) every person who types the URL manually gets a 404; (4) it signals imperfect attention to detail at the URL level for a company positioning as technical API infrastructure. The nav item label itself reads 'Available Brands' (correctly spelled) — only the URL has the typo.
Recommendation
Redirect /avaialble-brands to /available-brands immediately, then rename the page to the correct URL. In Webflow, this involves: (1) renaming the page slug to 'available-brands'; (2) adding a 301 redirect from the old typo URL in Webflow's redirect manager; (3) updating all internal links across the site to point to the corrected URL. Check all other page URL slugs for similar transposition typos. While fixing this, also check the page title of the /avaialble-brands destination — if it was built under the same conditions as the URL, the title meta tag may also contain typos or placeholder content.
SEO
URL Typo: '/avaialble-brands' — 'Available' Misspelled in Production URL
Score
38
Severity
High
Finding
The Resources section of the navigation links to: https://finperks.com/avaialble-brands — with 'avaialble' as a misspelling of 'available' (letters transposed: 'avai-a-lble' instead of 'available'). This is a live production URL with a typo in the path segment. The consequences: (1) any external site linking to /available-brands (the correct spelling) will 404; (2) Google may index both /avaialble-brands and any corrected /available-brands creating a duplicate content split; (3) every person who types the URL manually gets a 404; (4) it signals imperfect attention to detail at the URL level for a company positioning as technical API infrastructure. The nav item label itself reads 'Available Brands' (correctly spelled) — only the URL has the typo.
Recommendation
Redirect /avaialble-brands to /available-brands immediately, then rename the page to the correct URL. In Webflow, this involves: (1) renaming the page slug to 'available-brands'; (2) adding a 301 redirect from the old typo URL in Webflow's redirect manager; (3) updating all internal links across the site to point to the corrected URL. Check all other page URL slugs for similar transposition typos. While fixing this, also check the page title of the /avaialble-brands destination — if it was built under the same conditions as the URL, the title meta tag may also contain typos or placeholder content.
SEO
URL Typo: '/avaialble-brands' — 'Available' Misspelled in Production URL
Score
38
Severity
High
Finding
The Resources section of the navigation links to: https://finperks.com/avaialble-brands — with 'avaialble' as a misspelling of 'available' (letters transposed: 'avai-a-lble' instead of 'available'). This is a live production URL with a typo in the path segment. The consequences: (1) any external site linking to /available-brands (the correct spelling) will 404; (2) Google may index both /avaialble-brands and any corrected /available-brands creating a duplicate content split; (3) every person who types the URL manually gets a 404; (4) it signals imperfect attention to detail at the URL level for a company positioning as technical API infrastructure. The nav item label itself reads 'Available Brands' (correctly spelled) — only the URL has the typo.
Recommendation
Redirect /avaialble-brands to /available-brands immediately, then rename the page to the correct URL. In Webflow, this involves: (1) renaming the page slug to 'available-brands'; (2) adding a 301 redirect from the old typo URL in Webflow's redirect manager; (3) updating all internal links across the site to point to the corrected URL. Check all other page URL slugs for similar transposition typos. While fixing this, also check the page title of the /avaialble-brands destination — if it was built under the same conditions as the URL, the title meta tag may also contain typos or placeholder content.
Brand
Founding Team's Viafintech/Paysafe Exit — The Homepage's Strongest Trust Signal, Completely Absent
Score
36
Severity
High
Finding
The finperks founding team — Achim Bönsch, Sebastian Seifert, and Andreas Veller — previously built Barzahlen/viafintech, which was acquired by NYSE-listed Paysafe in a nine-figure deal in 2021. Sebastian Seifert was named Forbes 30 Under 30 in DACH (2019) and Europe Finance (2020). This is the single most persuasive credibility signal available for a pre-seed fintech seeking partnerships with banks, fintechs, and HR platforms: a team that has already built and sold the largest bank-independent cash network in Europe and the US to a NYSE-listed acquirer. Yet the homepage contains zero mention of viafintech, Barzahlen, Paysafe, the exit, or any founder background. The 'About us' page presumably covers this, but the homepage — which is the first touch for any inbound prospect from the press coverage — gives no founder signal whatsoever.
Recommendation
Add a founder credibility section to the homepage, immediately below the hero or above the 'Value finperks Brings' section: 'Founded by the team behind viafintech — acquired by Paysafe (NYSE) in 2021.' This single sentence, with a Paysafe/NYSE reference, transforms finperks from 'another fintech API startup' into 'a second company built by the team that already did this once at scale.' For a B2B infrastructure play where trust and track record drive partnership decisions, the founders' prior exit is a conversion asset more powerful than any feature description. Add headshot thumbnails and one-line bios to the homepage, not just on the About page.
Brand
Founding Team's Viafintech/Paysafe Exit — The Homepage's Strongest Trust Signal, Completely Absent
Score
36
Severity
High
Finding
The finperks founding team — Achim Bönsch, Sebastian Seifert, and Andreas Veller — previously built Barzahlen/viafintech, which was acquired by NYSE-listed Paysafe in a nine-figure deal in 2021. Sebastian Seifert was named Forbes 30 Under 30 in DACH (2019) and Europe Finance (2020). This is the single most persuasive credibility signal available for a pre-seed fintech seeking partnerships with banks, fintechs, and HR platforms: a team that has already built and sold the largest bank-independent cash network in Europe and the US to a NYSE-listed acquirer. Yet the homepage contains zero mention of viafintech, Barzahlen, Paysafe, the exit, or any founder background. The 'About us' page presumably covers this, but the homepage — which is the first touch for any inbound prospect from the press coverage — gives no founder signal whatsoever.
Recommendation
Add a founder credibility section to the homepage, immediately below the hero or above the 'Value finperks Brings' section: 'Founded by the team behind viafintech — acquired by Paysafe (NYSE) in 2021.' This single sentence, with a Paysafe/NYSE reference, transforms finperks from 'another fintech API startup' into 'a second company built by the team that already did this once at scale.' For a B2B infrastructure play where trust and track record drive partnership decisions, the founders' prior exit is a conversion asset more powerful than any feature description. Add headshot thumbnails and one-line bios to the homepage, not just on the About page.
Brand
Founding Team's Viafintech/Paysafe Exit — The Homepage's Strongest Trust Signal, Completely Absent
Score
36
Severity
High
Finding
The finperks founding team — Achim Bönsch, Sebastian Seifert, and Andreas Veller — previously built Barzahlen/viafintech, which was acquired by NYSE-listed Paysafe in a nine-figure deal in 2021. Sebastian Seifert was named Forbes 30 Under 30 in DACH (2019) and Europe Finance (2020). This is the single most persuasive credibility signal available for a pre-seed fintech seeking partnerships with banks, fintechs, and HR platforms: a team that has already built and sold the largest bank-independent cash network in Europe and the US to a NYSE-listed acquirer. Yet the homepage contains zero mention of viafintech, Barzahlen, Paysafe, the exit, or any founder background. The 'About us' page presumably covers this, but the homepage — which is the first touch for any inbound prospect from the press coverage — gives no founder signal whatsoever.
Recommendation
Add a founder credibility section to the homepage, immediately below the hero or above the 'Value finperks Brings' section: 'Founded by the team behind viafintech — acquired by Paysafe (NYSE) in 2021.' This single sentence, with a Paysafe/NYSE reference, transforms finperks from 'another fintech API startup' into 'a second company built by the team that already did this once at scale.' For a B2B infrastructure play where trust and track record drive partnership decisions, the founders' prior exit is a conversion asset more powerful than any feature description. Add headshot thumbnails and one-line bios to the homepage, not just on the About page.
Performance
Brand Carousel Loads the Same 35 Brand Logos Four Times — 140 Image Requests
Score
42
Severity
Medium
Finding
The hero brand carousel section contains approximately 35 brand logos (Zalando, Adidas, Airbnb, Amazon, Apple, ASOS, Decathlon, etc.) loaded four times each in the HTML source to create an infinite scroll animation — producing approximately 140 <img> element requests for the carousel alone. This is the identical infinite-carousel DOM-duplication pattern flagged in audits of Neo4j (88 logo images), coco.delivery (DOM triplication), PandaDoc (doubled video posters), and durable.com. For a Webflow-built site targeting technical API evaluators at banks and fintech companies, a homepage that fires 140 image requests for a decorative logo carousel is a performance signal that conflicts with the 'tech-first platform' positioning.
Recommendation
Implement the brand carousel using CSS animation on a single set of 35 logo images with translateX transforms and animation-iteration-count: infinite. This achieves the same infinite scroll visual effect with a single set of image requests rather than four cloned sets. Alternatively, use a CSS marquee approach with two sets (original + one clone) rather than four — halving the image count to 70 from 140. Run Lighthouse on the homepage to establish a performance baseline; the 140 carousel image requests will likely be the primary LCP contributor. Add loading='lazy' to all carousel images beyond the first visible row.
Performance
Brand Carousel Loads the Same 35 Brand Logos Four Times — 140 Image Requests
Score
42
Severity
Medium
Finding
The hero brand carousel section contains approximately 35 brand logos (Zalando, Adidas, Airbnb, Amazon, Apple, ASOS, Decathlon, etc.) loaded four times each in the HTML source to create an infinite scroll animation — producing approximately 140 <img> element requests for the carousel alone. This is the identical infinite-carousel DOM-duplication pattern flagged in audits of Neo4j (88 logo images), coco.delivery (DOM triplication), PandaDoc (doubled video posters), and durable.com. For a Webflow-built site targeting technical API evaluators at banks and fintech companies, a homepage that fires 140 image requests for a decorative logo carousel is a performance signal that conflicts with the 'tech-first platform' positioning.
Recommendation
Implement the brand carousel using CSS animation on a single set of 35 logo images with translateX transforms and animation-iteration-count: infinite. This achieves the same infinite scroll visual effect with a single set of image requests rather than four cloned sets. Alternatively, use a CSS marquee approach with two sets (original + one clone) rather than four — halving the image count to 70 from 140. Run Lighthouse on the homepage to establish a performance baseline; the 140 carousel image requests will likely be the primary LCP contributor. Add loading='lazy' to all carousel images beyond the first visible row.
Performance
Brand Carousel Loads the Same 35 Brand Logos Four Times — 140 Image Requests
Score
42
Severity
Medium
Finding
The hero brand carousel section contains approximately 35 brand logos (Zalando, Adidas, Airbnb, Amazon, Apple, ASOS, Decathlon, etc.) loaded four times each in the HTML source to create an infinite scroll animation — producing approximately 140 <img> element requests for the carousel alone. This is the identical infinite-carousel DOM-duplication pattern flagged in audits of Neo4j (88 logo images), coco.delivery (DOM triplication), PandaDoc (doubled video posters), and durable.com. For a Webflow-built site targeting technical API evaluators at banks and fintech companies, a homepage that fires 140 image requests for a decorative logo carousel is a performance signal that conflicts with the 'tech-first platform' positioning.
Recommendation
Implement the brand carousel using CSS animation on a single set of 35 logo images with translateX transforms and animation-iteration-count: infinite. This achieves the same infinite scroll visual effect with a single set of image requests rather than four cloned sets. Alternatively, use a CSS marquee approach with two sets (original + one clone) rather than four — halving the image count to 70 from 140. Run Lighthouse on the homepage to establish a performance baseline; the 140 carousel image requests will likely be the primary LCP contributor. Add loading='lazy' to all carousel images beyond the first visible row.
Copy
Six Use Cases in Nav Menu — URL Paths Inconsistent (Mix of /use-cases/ and /use-case/)
Score
45
Severity
Medium
Finding
The primary navigation Use Cases menu links to a mix of URL structures: top-level nav items use /use-cases/ (plural): Cashback → /use-cases/cashback, Employee Benefits → /use-cases/employee-benefit, etc. But the dropdown menu links use /use-case/ (singular): Cashback → /use-case/cashback, Promotions → /use-case/promotions. The nav therefore contains both /use-cases/ and /use-case/ paths for the same content area — singular and plural versions coexisting. If both URL patterns lead to real pages, Google may be indexing two parallel content trees. If one set 404s, half the nav's Use Case links are broken. Either way, the inconsistency is a structural issue in the site's URL architecture that will create confusion for both crawlers and users.
Recommendation
Standardise on a single URL pattern for all use case pages — either all /use-cases/ (plural, recommended for SEO breadcrumb consistency) or all /use-case/ (singular). Then set up 301 redirects from the old pattern to the new one, and update all internal links site-wide. Check the nav HTML carefully: the top-level menu items in the hamburger/mobile nav use /use-cases/ (plural with hyphen), while the mega-menu dropdowns use /use-case/ (singular). This appears to be a nav duplication bug where two different nav templates were built with different URL patterns and both deployed simultaneously.
Copy
Six Use Cases in Nav Menu — URL Paths Inconsistent (Mix of /use-cases/ and /use-case/)
Score
45
Severity
Medium
Finding
The primary navigation Use Cases menu links to a mix of URL structures: top-level nav items use /use-cases/ (plural): Cashback → /use-cases/cashback, Employee Benefits → /use-cases/employee-benefit, etc. But the dropdown menu links use /use-case/ (singular): Cashback → /use-case/cashback, Promotions → /use-case/promotions. The nav therefore contains both /use-cases/ and /use-case/ paths for the same content area — singular and plural versions coexisting. If both URL patterns lead to real pages, Google may be indexing two parallel content trees. If one set 404s, half the nav's Use Case links are broken. Either way, the inconsistency is a structural issue in the site's URL architecture that will create confusion for both crawlers and users.
Recommendation
Standardise on a single URL pattern for all use case pages — either all /use-cases/ (plural, recommended for SEO breadcrumb consistency) or all /use-case/ (singular). Then set up 301 redirects from the old pattern to the new one, and update all internal links site-wide. Check the nav HTML carefully: the top-level menu items in the hamburger/mobile nav use /use-cases/ (plural with hyphen), while the mega-menu dropdowns use /use-case/ (singular). This appears to be a nav duplication bug where two different nav templates were built with different URL patterns and both deployed simultaneously.
Copy
Six Use Cases in Nav Menu — URL Paths Inconsistent (Mix of /use-cases/ and /use-case/)
Score
45
Severity
Medium
Finding
The primary navigation Use Cases menu links to a mix of URL structures: top-level nav items use /use-cases/ (plural): Cashback → /use-cases/cashback, Employee Benefits → /use-cases/employee-benefit, etc. But the dropdown menu links use /use-case/ (singular): Cashback → /use-case/cashback, Promotions → /use-case/promotions. The nav therefore contains both /use-cases/ and /use-case/ paths for the same content area — singular and plural versions coexisting. If both URL patterns lead to real pages, Google may be indexing two parallel content trees. If one set 404s, half the nav's Use Case links are broken. Either way, the inconsistency is a structural issue in the site's URL architecture that will create confusion for both crawlers and users.
Recommendation
Standardise on a single URL pattern for all use case pages — either all /use-cases/ (plural, recommended for SEO breadcrumb consistency) or all /use-case/ (singular). Then set up 301 redirects from the old pattern to the new one, and update all internal links site-wide. Check the nav HTML carefully: the top-level menu items in the hamburger/mobile nav use /use-cases/ (plural with hyphen), while the mega-menu dropdowns use /use-case/ (singular). This appears to be a nav duplication bug where two different nav templates were built with different URL patterns and both deployed simultaneously.
Social Proof
No Named Partner Logos on Homepage — FLIZpay, Recardy, and Paylo Are Live Customers
Score
44
Severity
Medium
Finding
finperks has three confirmed live customer integrations as of the March 2026 pre-seed announcement: FLIZpay (cashback), Recardy (employee benefits), and Paylo (employee benefits). These are real, launched, in-production integrations — not pilot or trial customers. For a pre-seed B2B infrastructure company, three live production integrations six months after founding is an exceptionally strong signal. Yet the homepage displays zero partner or customer logos. The only social proof on the page is the brand catalog (Zalando, Amazon, Netflix etc.) — which are brands in the network, not the actual paying customers. A Head of Product at a bank evaluating finperks as an API provider needs to see who else has already trusted the infrastructure, not just which brands are available.
Recommendation
Add a 'Trusted by' or 'Live integrations' section to the homepage featuring the FLIZpay, Recardy, and Paylo logos with one-line descriptions: 'FLIZpay — brand-funded cashback averaging 5%, paid instantly into bank accounts' and 'Recardy & Paylo — Germany's €50 Sachbezug distributed via finperks without additional infrastructure.' Even three logos with brief attribution converts significantly better than a blank social proof section. As finperks onboards more partners, this section grows into one of the most persuasive conversion elements on the page. The press release quotes from the funding announcement ('six months after launch, already live across multiple platforms') belong on the homepage, not just in press coverage.
Social Proof
No Named Partner Logos on Homepage — FLIZpay, Recardy, and Paylo Are Live Customers
Score
44
Severity
Medium
Finding
finperks has three confirmed live customer integrations as of the March 2026 pre-seed announcement: FLIZpay (cashback), Recardy (employee benefits), and Paylo (employee benefits). These are real, launched, in-production integrations — not pilot or trial customers. For a pre-seed B2B infrastructure company, three live production integrations six months after founding is an exceptionally strong signal. Yet the homepage displays zero partner or customer logos. The only social proof on the page is the brand catalog (Zalando, Amazon, Netflix etc.) — which are brands in the network, not the actual paying customers. A Head of Product at a bank evaluating finperks as an API provider needs to see who else has already trusted the infrastructure, not just which brands are available.
Recommendation
Add a 'Trusted by' or 'Live integrations' section to the homepage featuring the FLIZpay, Recardy, and Paylo logos with one-line descriptions: 'FLIZpay — brand-funded cashback averaging 5%, paid instantly into bank accounts' and 'Recardy & Paylo — Germany's €50 Sachbezug distributed via finperks without additional infrastructure.' Even three logos with brief attribution converts significantly better than a blank social proof section. As finperks onboards more partners, this section grows into one of the most persuasive conversion elements on the page. The press release quotes from the funding announcement ('six months after launch, already live across multiple platforms') belong on the homepage, not just in press coverage.
Social Proof
No Named Partner Logos on Homepage — FLIZpay, Recardy, and Paylo Are Live Customers
Score
44
Severity
Medium
Finding
finperks has three confirmed live customer integrations as of the March 2026 pre-seed announcement: FLIZpay (cashback), Recardy (employee benefits), and Paylo (employee benefits). These are real, launched, in-production integrations — not pilot or trial customers. For a pre-seed B2B infrastructure company, three live production integrations six months after founding is an exceptionally strong signal. Yet the homepage displays zero partner or customer logos. The only social proof on the page is the brand catalog (Zalando, Amazon, Netflix etc.) — which are brands in the network, not the actual paying customers. A Head of Product at a bank evaluating finperks as an API provider needs to see who else has already trusted the infrastructure, not just which brands are available.
Recommendation
Add a 'Trusted by' or 'Live integrations' section to the homepage featuring the FLIZpay, Recardy, and Paylo logos with one-line descriptions: 'FLIZpay — brand-funded cashback averaging 5%, paid instantly into bank accounts' and 'Recardy & Paylo — Germany's €50 Sachbezug distributed via finperks without additional infrastructure.' Even three logos with brief attribution converts significantly better than a blank social proof section. As finperks onboards more partners, this section grows into one of the most persuasive conversion elements on the page. The press release quotes from the funding announcement ('six months after launch, already live across multiple platforms') belong on the homepage, not just in press coverage.
Copy
€3.4M Pre-Seed (March 11, 2026) — Not Mentioned on Homepage
Score
45
Severity
Medium
Finding
finperks announced a €3.4M pre-seed round on March 11, 2026 — one week ago. This is the company's founding credibility event: led by Motive Partners (a specialist fintech investment firm with deep FS relationships) and seed+speed Ventures. Carsten Maschmeyer (the German fintech investor) also participated. The homepage mentions zero funding context — no investor names, no round size, no investor logos. For a company building API infrastructure for banks and fintechs, investor credibility from a specialist like Motive Partners (whose portfolio includes major financial services technology companies) carries significant weight in enterprise partnership conversations. The announcement was covered by EU-Startups, The Next Web, Tech.eu, FinTech Global, and multiple other publications — all driving traffic to finperks.com — yet the homepage gives no indication of the funding or investor backing.
Recommendation
Add a trust strip or footer line referencing the funding: 'Backed by Motive Partners and seed+speed Ventures · March 2026' with investor logos. Motive Partners' reputation in fintech specifically — not just as a generic VC — is a differentiated trust signal for bank and fintech partnership conversations. Consider a hero sub-text addition: 'Backed by Motive Partners — the fintech investment firm behind [portfolio names].' The freshness of the round (one week ago) means this is the peak attention moment for inbound traffic — and the site should capitalise on it by reflecting the company's investor credibility to everyone arriving from press coverage.
Copy
€3.4M Pre-Seed (March 11, 2026) — Not Mentioned on Homepage
Score
45
Severity
Medium
Finding
finperks announced a €3.4M pre-seed round on March 11, 2026 — one week ago. This is the company's founding credibility event: led by Motive Partners (a specialist fintech investment firm with deep FS relationships) and seed+speed Ventures. Carsten Maschmeyer (the German fintech investor) also participated. The homepage mentions zero funding context — no investor names, no round size, no investor logos. For a company building API infrastructure for banks and fintechs, investor credibility from a specialist like Motive Partners (whose portfolio includes major financial services technology companies) carries significant weight in enterprise partnership conversations. The announcement was covered by EU-Startups, The Next Web, Tech.eu, FinTech Global, and multiple other publications — all driving traffic to finperks.com — yet the homepage gives no indication of the funding or investor backing.
Recommendation
Add a trust strip or footer line referencing the funding: 'Backed by Motive Partners and seed+speed Ventures · March 2026' with investor logos. Motive Partners' reputation in fintech specifically — not just as a generic VC — is a differentiated trust signal for bank and fintech partnership conversations. Consider a hero sub-text addition: 'Backed by Motive Partners — the fintech investment firm behind [portfolio names].' The freshness of the round (one week ago) means this is the peak attention moment for inbound traffic — and the site should capitalise on it by reflecting the company's investor credibility to everyone arriving from press coverage.
Copy
€3.4M Pre-Seed (March 11, 2026) — Not Mentioned on Homepage
Score
45
Severity
Medium
Finding
finperks announced a €3.4M pre-seed round on March 11, 2026 — one week ago. This is the company's founding credibility event: led by Motive Partners (a specialist fintech investment firm with deep FS relationships) and seed+speed Ventures. Carsten Maschmeyer (the German fintech investor) also participated. The homepage mentions zero funding context — no investor names, no round size, no investor logos. For a company building API infrastructure for banks and fintechs, investor credibility from a specialist like Motive Partners (whose portfolio includes major financial services technology companies) carries significant weight in enterprise partnership conversations. The announcement was covered by EU-Startups, The Next Web, Tech.eu, FinTech Global, and multiple other publications — all driving traffic to finperks.com — yet the homepage gives no indication of the funding or investor backing.
Recommendation
Add a trust strip or footer line referencing the funding: 'Backed by Motive Partners and seed+speed Ventures · March 2026' with investor logos. Motive Partners' reputation in fintech specifically — not just as a generic VC — is a differentiated trust signal for bank and fintech partnership conversations. Consider a hero sub-text addition: 'Backed by Motive Partners — the fintech investment firm behind [portfolio names].' The freshness of the round (one week ago) means this is the peak attention moment for inbound traffic — and the site should capitalise on it by reflecting the company's investor credibility to everyone arriving from press coverage.
Copy
Grammar Error: 'into you payroll Solutions' in Employee Benefits Micro-Copy
Score
40
Severity
Medium
Finding
The Employee Benefits use-case description in the 'A Better Way To Power Prepaid' page section reads: 'Integrate seamless tax free benefits (e.g. 50€ Sachbezug) with giftcards into you payroll Solutions. Compliant by design.' The phrase 'into you payroll Solutions' has two errors: (1) 'you' should be 'your'; (2) 'Solutions' is capitalised unnecessarily mid-sentence. This is the copy for one of finperks' primary use cases — German HR/payroll platforms integrating the €50 Sachbezug benefit — which is specifically named in the press release as a live production use case (Recardy and Paylo). A grammar error in the description of the product's flagship live use case is a small but visible polish failure.
Recommendation
Fix the grammar: 'Integrate seamless, tax-free benefits (e.g. €50 Sachbezug) via gift cards into your payroll solutions. Compliant by design.' Add a comma after 'seamless', format €50 before the number per European convention, lowercase 'solutions', and fix 'you' → 'your'. Then audit all homepage use-case micro-copy for similar errors — at an early-stage company where every word on the site is a signal about team quality, small errors carry disproportionate weight when a Head of Partnerships at Deutsche Bank is evaluating whether to integrate the API.
Copy
Grammar Error: 'into you payroll Solutions' in Employee Benefits Micro-Copy
Score
40
Severity
Medium
Finding
The Employee Benefits use-case description in the 'A Better Way To Power Prepaid' page section reads: 'Integrate seamless tax free benefits (e.g. 50€ Sachbezug) with giftcards into you payroll Solutions. Compliant by design.' The phrase 'into you payroll Solutions' has two errors: (1) 'you' should be 'your'; (2) 'Solutions' is capitalised unnecessarily mid-sentence. This is the copy for one of finperks' primary use cases — German HR/payroll platforms integrating the €50 Sachbezug benefit — which is specifically named in the press release as a live production use case (Recardy and Paylo). A grammar error in the description of the product's flagship live use case is a small but visible polish failure.
Recommendation
Fix the grammar: 'Integrate seamless, tax-free benefits (e.g. €50 Sachbezug) via gift cards into your payroll solutions. Compliant by design.' Add a comma after 'seamless', format €50 before the number per European convention, lowercase 'solutions', and fix 'you' → 'your'. Then audit all homepage use-case micro-copy for similar errors — at an early-stage company where every word on the site is a signal about team quality, small errors carry disproportionate weight when a Head of Partnerships at Deutsche Bank is evaluating whether to integrate the API.
Copy
Grammar Error: 'into you payroll Solutions' in Employee Benefits Micro-Copy
Score
40
Severity
Medium
Finding
The Employee Benefits use-case description in the 'A Better Way To Power Prepaid' page section reads: 'Integrate seamless tax free benefits (e.g. 50€ Sachbezug) with giftcards into you payroll Solutions. Compliant by design.' The phrase 'into you payroll Solutions' has two errors: (1) 'you' should be 'your'; (2) 'Solutions' is capitalised unnecessarily mid-sentence. This is the copy for one of finperks' primary use cases — German HR/payroll platforms integrating the €50 Sachbezug benefit — which is specifically named in the press release as a live production use case (Recardy and Paylo). A grammar error in the description of the product's flagship live use case is a small but visible polish failure.
Recommendation
Fix the grammar: 'Integrate seamless, tax-free benefits (e.g. €50 Sachbezug) via gift cards into your payroll solutions. Compliant by design.' Add a comma after 'seamless', format €50 before the number per European convention, lowercase 'solutions', and fix 'you' → 'your'. Then audit all homepage use-case micro-copy for similar errors — at an early-stage company where every word on the site is a signal about team quality, small errors carry disproportionate weight when a Head of Partnerships at Deutsche Bank is evaluating whether to integrate the API.
SEO
No Meta Description — Google Will Generate One From '700+ Brands' Stats Section
Score
40
Severity
High
Finding
The homepage has no <meta name='description'> tag (not captured in the fetched content, consistent with a minimal Webflow template deploy). When the meta description is absent, Google auto-generates a snippet from the most prominent page text — in this case likely '700+ Brands / 30+ Countries / <30 Days to Market' or the problem statement copy from 'The Prepaid Market Is Broken.' Neither makes a compelling SERP snippet for a developer or product manager searching for 'prepaid API Europe' or 'gift card API for banks.' With the March 11 press coverage driving traffic to finperks.com from multiple publications, the first week after a funding announcement is the highest-traffic window the site will see for months — and the SERP presentation is uncontrolled.
Recommendation
Add a meta description within 24 hours: 'finperks is the single-API prepaid infrastructure platform for banks, fintechs, and HR platforms — access 1,000+ brands across 30+ European markets through one integration, one contract, one settlement.' At 155 characters, this fits the limit, leads with the primary audience, names the product category, and includes the key differentiator claims. Add Open Graph tags (og:title, og:description, og:image) so that link previews on LinkedIn (where the funding news is being shared by fintech VCs and founders) show a branded, informative card rather than a blank or auto-generated preview.
SEO
No Meta Description — Google Will Generate One From '700+ Brands' Stats Section
Score
40
Severity
High
Finding
The homepage has no <meta name='description'> tag (not captured in the fetched content, consistent with a minimal Webflow template deploy). When the meta description is absent, Google auto-generates a snippet from the most prominent page text — in this case likely '700+ Brands / 30+ Countries / <30 Days to Market' or the problem statement copy from 'The Prepaid Market Is Broken.' Neither makes a compelling SERP snippet for a developer or product manager searching for 'prepaid API Europe' or 'gift card API for banks.' With the March 11 press coverage driving traffic to finperks.com from multiple publications, the first week after a funding announcement is the highest-traffic window the site will see for months — and the SERP presentation is uncontrolled.
Recommendation
Add a meta description within 24 hours: 'finperks is the single-API prepaid infrastructure platform for banks, fintechs, and HR platforms — access 1,000+ brands across 30+ European markets through one integration, one contract, one settlement.' At 155 characters, this fits the limit, leads with the primary audience, names the product category, and includes the key differentiator claims. Add Open Graph tags (og:title, og:description, og:image) so that link previews on LinkedIn (where the funding news is being shared by fintech VCs and founders) show a branded, informative card rather than a blank or auto-generated preview.
SEO
No Meta Description — Google Will Generate One From '700+ Brands' Stats Section
Score
40
Severity
High
Finding
The homepage has no <meta name='description'> tag (not captured in the fetched content, consistent with a minimal Webflow template deploy). When the meta description is absent, Google auto-generates a snippet from the most prominent page text — in this case likely '700+ Brands / 30+ Countries / <30 Days to Market' or the problem statement copy from 'The Prepaid Market Is Broken.' Neither makes a compelling SERP snippet for a developer or product manager searching for 'prepaid API Europe' or 'gift card API for banks.' With the March 11 press coverage driving traffic to finperks.com from multiple publications, the first week after a funding announcement is the highest-traffic window the site will see for months — and the SERP presentation is uncontrolled.
Recommendation
Add a meta description within 24 hours: 'finperks is the single-API prepaid infrastructure platform for banks, fintechs, and HR platforms — access 1,000+ brands across 30+ European markets through one integration, one contract, one settlement.' At 155 characters, this fits the limit, leads with the primary audience, names the product category, and includes the key differentiator claims. Add Open Graph tags (og:title, og:description, og:image) so that link previews on LinkedIn (where the funding news is being shared by fintech VCs and founders) show a branded, informative card rather than a blank or auto-generated preview.
Copy
The Prepaid Market Stats ($4.24T by 2035) — Compelling Market Size Context Missing From Homepage
Score
52
Severity
Low
Finding
Press coverage of the finperks pre-seed references a market size of $4.24 trillion by 2035 for the global prepaid market, and $5.3 trillion for gift cards alone by 2034. The Motive Partners investment thesis (published on their site) frames prepaid as 'a trillion-dollar market' at the 'intersection of several powerful financial ecosystem trends.' None of these market size figures appear on the finperks homepage. For an infrastructure play targeting enterprise partners (banks with enterprise APIs, large HR SaaS platforms), framing the market opportunity on the homepage gives executive sponsors the context they need to approve a partnership internally: 'we're tapping into a $4T market with one integration.'
Recommendation
Add a market context section or a simple stat to the homepage: 'The global prepaid market: $4.24 trillion by 2035. Built on fragmented, legacy infrastructure. Until now.' This framing positions finperks not just as a vendor but as the infrastructure company for a trillion-dollar market transformation — the 'Stripe for prepaid' positioning that appears in all press coverage but nowhere on the homepage. The Motive Partners investment thesis is publicly available and can be used for specific stat attribution. Consider adding the market size figure to the hero sub-head or the 'Broken Market' problem section.
Copy
The Prepaid Market Stats ($4.24T by 2035) — Compelling Market Size Context Missing From Homepage
Score
52
Severity
Low
Finding
Press coverage of the finperks pre-seed references a market size of $4.24 trillion by 2035 for the global prepaid market, and $5.3 trillion for gift cards alone by 2034. The Motive Partners investment thesis (published on their site) frames prepaid as 'a trillion-dollar market' at the 'intersection of several powerful financial ecosystem trends.' None of these market size figures appear on the finperks homepage. For an infrastructure play targeting enterprise partners (banks with enterprise APIs, large HR SaaS platforms), framing the market opportunity on the homepage gives executive sponsors the context they need to approve a partnership internally: 'we're tapping into a $4T market with one integration.'
Recommendation
Add a market context section or a simple stat to the homepage: 'The global prepaid market: $4.24 trillion by 2035. Built on fragmented, legacy infrastructure. Until now.' This framing positions finperks not just as a vendor but as the infrastructure company for a trillion-dollar market transformation — the 'Stripe for prepaid' positioning that appears in all press coverage but nowhere on the homepage. The Motive Partners investment thesis is publicly available and can be used for specific stat attribution. Consider adding the market size figure to the hero sub-head or the 'Broken Market' problem section.
Copy
The Prepaid Market Stats ($4.24T by 2035) — Compelling Market Size Context Missing From Homepage
Score
52
Severity
Low
Finding
Press coverage of the finperks pre-seed references a market size of $4.24 trillion by 2035 for the global prepaid market, and $5.3 trillion for gift cards alone by 2034. The Motive Partners investment thesis (published on their site) frames prepaid as 'a trillion-dollar market' at the 'intersection of several powerful financial ecosystem trends.' None of these market size figures appear on the finperks homepage. For an infrastructure play targeting enterprise partners (banks with enterprise APIs, large HR SaaS platforms), framing the market opportunity on the homepage gives executive sponsors the context they need to approve a partnership internally: 'we're tapping into a $4T market with one integration.'
Recommendation
Add a market context section or a simple stat to the homepage: 'The global prepaid market: $4.24 trillion by 2035. Built on fragmented, legacy infrastructure. Until now.' This framing positions finperks not just as a vendor but as the infrastructure company for a trillion-dollar market transformation — the 'Stripe for prepaid' positioning that appears in all press coverage but nowhere on the homepage. The Motive Partners investment thesis is publicly available and can be used for specific stat attribution. Consider adding the market size figure to the hero sub-head or the 'Broken Market' problem section.