Enter password to view Website Audit
Analysis
Website
Paysend
Analysis
Website
Paysend
Analysis
Website
Paysend
Published on
2026-03-18
For
Paysend
Score
44
Paysend is a global fintech payments platform enabling consumers to send money internationally to 170+ countries and businesses to process cross-border payments via API. Known for flat-fee card-to-card transfers (£1/€1.50/$2), real-time FX rates, and a network connecting 20 billion+ card endpoints across Mastercard, Visa, UnionPay and local schemes. FCA regulated. 12M+ customers. $227M total funding.
Market
International Money Transfer / Consumer Remittance / Cross-Border Payments API / Fintech
Audience
Consumer remittance senders (diaspora, expats, migrant workers); Enterprise/SMB clients integrating payment APIs; Developers building on Paysend Network
HQ
London, UK / Miami, FL (US HQ)
Website
Performance
35
Social Proof
38
Copy
40
Navigation
45
Copy
48
Copy
50
Freshness
48
Social Proof
52
SEO
36
Copy
50
Performance
Root Domain paysend.com Returns HTTP 403 to Standard Crawlers
Score
35
Severity
High
Finding
paysend.com returns a 403 Forbidden error to standard HTTP fetch requests and redirects to geo-specific URLs (paysend.com/en-us, paysend.com/en-gb, etc.) based on IP geolocation. This means: (1) any visitor using a VPN or accessing from an unrecognised IP gets a 403 instead of the homepage; (2) social media link previews (Open Graph scrapers from Twitter/X, LinkedIn, WhatsApp, iMessage) may receive 403s and generate blank previews when users share paysend.com; (3) monitoring tools, uptime checkers, and security scanners that test the root domain will report it as down; (4) international users whose geo-detection fails land on an error page rather than a language selector. Competitors like Wise and Remitly serve the root domain to all visitors with a country selector.
Recommendation
Serve a genuine root domain landing page at paysend.com that is accessible to all HTTP clients regardless of IP geolocation. This page should present a country/language selector and function as the canonical homepage — with proper Open Graph tags, hreflang canonicals pointing to geo-specific URLs, and a non-blocking response to all crawlers and social scrapers. The geo-redirect can still exist as a soft redirect suggestion, but the root domain must never return 403. Fix by deploying a static HTML fallback at the CDN edge layer that serves all uncategorised IPs and all known bot user-agents.
Performance
Root Domain paysend.com Returns HTTP 403 to Standard Crawlers
Score
35
Severity
High
Finding
paysend.com returns a 403 Forbidden error to standard HTTP fetch requests and redirects to geo-specific URLs (paysend.com/en-us, paysend.com/en-gb, etc.) based on IP geolocation. This means: (1) any visitor using a VPN or accessing from an unrecognised IP gets a 403 instead of the homepage; (2) social media link previews (Open Graph scrapers from Twitter/X, LinkedIn, WhatsApp, iMessage) may receive 403s and generate blank previews when users share paysend.com; (3) monitoring tools, uptime checkers, and security scanners that test the root domain will report it as down; (4) international users whose geo-detection fails land on an error page rather than a language selector. Competitors like Wise and Remitly serve the root domain to all visitors with a country selector.
Recommendation
Serve a genuine root domain landing page at paysend.com that is accessible to all HTTP clients regardless of IP geolocation. This page should present a country/language selector and function as the canonical homepage — with proper Open Graph tags, hreflang canonicals pointing to geo-specific URLs, and a non-blocking response to all crawlers and social scrapers. The geo-redirect can still exist as a soft redirect suggestion, but the root domain must never return 403. Fix by deploying a static HTML fallback at the CDN edge layer that serves all uncategorised IPs and all known bot user-agents.
Performance
Root Domain paysend.com Returns HTTP 403 to Standard Crawlers
Score
35
Severity
High
Finding
paysend.com returns a 403 Forbidden error to standard HTTP fetch requests and redirects to geo-specific URLs (paysend.com/en-us, paysend.com/en-gb, etc.) based on IP geolocation. This means: (1) any visitor using a VPN or accessing from an unrecognised IP gets a 403 instead of the homepage; (2) social media link previews (Open Graph scrapers from Twitter/X, LinkedIn, WhatsApp, iMessage) may receive 403s and generate blank previews when users share paysend.com; (3) monitoring tools, uptime checkers, and security scanners that test the root domain will report it as down; (4) international users whose geo-detection fails land on an error page rather than a language selector. Competitors like Wise and Remitly serve the root domain to all visitors with a country selector.
Recommendation
Serve a genuine root domain landing page at paysend.com that is accessible to all HTTP clients regardless of IP geolocation. This page should present a country/language selector and function as the canonical homepage — with proper Open Graph tags, hreflang canonicals pointing to geo-specific URLs, and a non-blocking response to all crawlers and social scrapers. The geo-redirect can still exist as a soft redirect suggestion, but the root domain must never return 403. Fix by deploying a static HTML fallback at the CDN edge layer that serves all uncategorised IPs and all known bot user-agents.
Social Proof
Customer Count Inconsistency — '10 million' vs '12 million' on Live Pages
Score
38
Severity
High
Finding
The /en-us/send page (the effective US homepage, the most-trafficked landing page) prominently states 'Join our 12 million customers & counting' in the CTA section. However, the news article published January 10, 2025 celebrating a milestone says '10 million customers worldwide' — and the Google Play Store listing still reads 'Join 10 million+ customers worldwide' and '33,000+ Trustpilot reviews'. Three different customer counts are live simultaneously across Paysend's own properties: 10M (news article), 10M+ (app store), and 12M (website). For a consumer fintech where trust and scale are primary conversion drivers, contradictory headline stats on simultaneous live pages actively undermine credibility. A suspicious user who cross-checks the app store against the website sees an immediate discrepancy.
Recommendation
Conduct a full audit of every customer count claim across paysend.com, the App Store listing, Google Play listing, and all active blog/news pages. Establish a single canonical figure updated monthly, and apply it consistently everywhere within 7 days of each update. If the 12M figure on the /send page is accurate as of March 2026, update the app store listings and news page text immediately. If it is a forward projection or rounding, dial it back to the verified figure. The Trustpilot review count (33,000+ vs the Currency Expert review's 36,000+) shows the same drift — all social proof figures need a quarterly refresh protocol.
Social Proof
Customer Count Inconsistency — '10 million' vs '12 million' on Live Pages
Score
38
Severity
High
Finding
The /en-us/send page (the effective US homepage, the most-trafficked landing page) prominently states 'Join our 12 million customers & counting' in the CTA section. However, the news article published January 10, 2025 celebrating a milestone says '10 million customers worldwide' — and the Google Play Store listing still reads 'Join 10 million+ customers worldwide' and '33,000+ Trustpilot reviews'. Three different customer counts are live simultaneously across Paysend's own properties: 10M (news article), 10M+ (app store), and 12M (website). For a consumer fintech where trust and scale are primary conversion drivers, contradictory headline stats on simultaneous live pages actively undermine credibility. A suspicious user who cross-checks the app store against the website sees an immediate discrepancy.
Recommendation
Conduct a full audit of every customer count claim across paysend.com, the App Store listing, Google Play listing, and all active blog/news pages. Establish a single canonical figure updated monthly, and apply it consistently everywhere within 7 days of each update. If the 12M figure on the /send page is accurate as of March 2026, update the app store listings and news page text immediately. If it is a forward projection or rounding, dial it back to the verified figure. The Trustpilot review count (33,000+ vs the Currency Expert review's 36,000+) shows the same drift — all social proof figures need a quarterly refresh protocol.
Social Proof
Customer Count Inconsistency — '10 million' vs '12 million' on Live Pages
Score
38
Severity
High
Finding
The /en-us/send page (the effective US homepage, the most-trafficked landing page) prominently states 'Join our 12 million customers & counting' in the CTA section. However, the news article published January 10, 2025 celebrating a milestone says '10 million customers worldwide' — and the Google Play Store listing still reads 'Join 10 million+ customers worldwide' and '33,000+ Trustpilot reviews'. Three different customer counts are live simultaneously across Paysend's own properties: 10M (news article), 10M+ (app store), and 12M (website). For a consumer fintech where trust and scale are primary conversion drivers, contradictory headline stats on simultaneous live pages actively undermine credibility. A suspicious user who cross-checks the app store against the website sees an immediate discrepancy.
Recommendation
Conduct a full audit of every customer count claim across paysend.com, the App Store listing, Google Play listing, and all active blog/news pages. Establish a single canonical figure updated monthly, and apply it consistently everywhere within 7 days of each update. If the 12M figure on the /send page is accurate as of March 2026, update the app store listings and news page text immediately. If it is a forward projection or rounding, dial it back to the verified figure. The Trustpilot review count (33,000+ vs the Currency Expert review's 36,000+) shows the same drift — all social proof figures need a quarterly refresh protocol.
Copy
Trustpilot Claim Discrepancy — '85% excellent' vs Independent '4.1 Great' Rating
Score
40
Severity
High
Finding
Paysend's own pages and app store listings cite '85% rate us as excellent on Trustpilot' — a figure sourced from the '85% Excellent' star distribution in Trustpilot reviews. However, Trustpilot's weighted aggregate score produces a 4.1/5 rating classified as 'Great' — not 'Excellent' (which requires 4.5+). The 85% claim is technically defensible (85% of reviewers gave 5 stars) but is presented without the overall score, which is what prospective users see when they visit Trustpilot independently. Currency Expert's independent review confirms: '4.1 out of 5 on Trustpilot from over 36,000 reviews, classified as Great.' A new user who sees '85% excellent' on the Paysend site, then visits Trustpilot and sees 4.1 'Great', experiences a credibility gap. Wise, by comparison, holds 4.3 and Remitly 4.1 — Paysend is competitive but its framing inflates the implied rating.
Recommendation
Replace '85% rate us as excellent on Trustpilot' with the actual aggregate score and classification: '4.1/5 on Trustpilot — Rated Great by 36,000+ customers.' This is more honest and still competitive in the remittance space. If the score has genuinely improved above 4.2 recently, use the updated figure — but link directly to the live Trustpilot page so visitors can verify in real time. The '85% excellent' framing is a known dark pattern in review display; informed users recognise it as cherry-picking the 5-star distribution and it erodes trust in the entire social proof section. An honest 4.1 from 36K reviews is a strong signal; no need to spin it.
Copy
Trustpilot Claim Discrepancy — '85% excellent' vs Independent '4.1 Great' Rating
Score
40
Severity
High
Finding
Paysend's own pages and app store listings cite '85% rate us as excellent on Trustpilot' — a figure sourced from the '85% Excellent' star distribution in Trustpilot reviews. However, Trustpilot's weighted aggregate score produces a 4.1/5 rating classified as 'Great' — not 'Excellent' (which requires 4.5+). The 85% claim is technically defensible (85% of reviewers gave 5 stars) but is presented without the overall score, which is what prospective users see when they visit Trustpilot independently. Currency Expert's independent review confirms: '4.1 out of 5 on Trustpilot from over 36,000 reviews, classified as Great.' A new user who sees '85% excellent' on the Paysend site, then visits Trustpilot and sees 4.1 'Great', experiences a credibility gap. Wise, by comparison, holds 4.3 and Remitly 4.1 — Paysend is competitive but its framing inflates the implied rating.
Recommendation
Replace '85% rate us as excellent on Trustpilot' with the actual aggregate score and classification: '4.1/5 on Trustpilot — Rated Great by 36,000+ customers.' This is more honest and still competitive in the remittance space. If the score has genuinely improved above 4.2 recently, use the updated figure — but link directly to the live Trustpilot page so visitors can verify in real time. The '85% excellent' framing is a known dark pattern in review display; informed users recognise it as cherry-picking the 5-star distribution and it erodes trust in the entire social proof section. An honest 4.1 from 36K reviews is a strong signal; no need to spin it.
Copy
Trustpilot Claim Discrepancy — '85% excellent' vs Independent '4.1 Great' Rating
Score
40
Severity
High
Finding
Paysend's own pages and app store listings cite '85% rate us as excellent on Trustpilot' — a figure sourced from the '85% Excellent' star distribution in Trustpilot reviews. However, Trustpilot's weighted aggregate score produces a 4.1/5 rating classified as 'Great' — not 'Excellent' (which requires 4.5+). The 85% claim is technically defensible (85% of reviewers gave 5 stars) but is presented without the overall score, which is what prospective users see when they visit Trustpilot independently. Currency Expert's independent review confirms: '4.1 out of 5 on Trustpilot from over 36,000 reviews, classified as Great.' A new user who sees '85% excellent' on the Paysend site, then visits Trustpilot and sees 4.1 'Great', experiences a credibility gap. Wise, by comparison, holds 4.3 and Remitly 4.1 — Paysend is competitive but its framing inflates the implied rating.
Recommendation
Replace '85% rate us as excellent on Trustpilot' with the actual aggregate score and classification: '4.1/5 on Trustpilot — Rated Great by 36,000+ customers.' This is more honest and still competitive in the remittance space. If the score has genuinely improved above 4.2 recently, use the updated figure — but link directly to the live Trustpilot page so visitors can verify in real time. The '85% excellent' framing is a known dark pattern in review display; informed users recognise it as cherry-picking the 5-star distribution and it erodes trust in the entire social proof section. An honest 4.1 from 36K reviews is a strong signal; no need to spin it.
Navigation
Dual Audience (Personal + Enterprise) With No Homepage Separation
Score
45
Severity
Medium
Finding
The nav has two top-level sections — Personal and Enterprise — with Personal containing only 'Send money' and 'Help', and Enterprise containing 'Discover Paysend Enterprise', 'Paysend Network', 'API Reference', and 'Customer Support'. There is no homepage-level content that explains or differentiates the two products for a visitor who lands without context. A developer evaluating Paysend's Enterprise API lands on the same /send page as a grandmother sending remittances to Mexico — and has to locate 'Enterprise' in the nav without any above-the-fold signal that an enterprise product exists. The FT logo badges in the footer of the /send page are the only enterprise credibility signal visible on the consumer-facing page.
Recommendation
Create a dedicated enterprise.paysend.com or paysend.com/enterprise homepage that functions as the full enterprise product landing page — with its own hero, customer logos (Visa, Western Union, Deel partnerships), API documentation entry point, case studies, and sales CTA. The root domain and /send page serve consumers; the enterprise product deserves its own dedicated funnel. Alternatively, add an above-the-fold 'Are you a business?' banner that routes enterprise visitors immediately. The current architecture buries a $227M-funded company's B2B product inside a consumer app nav.
Navigation
Dual Audience (Personal + Enterprise) With No Homepage Separation
Score
45
Severity
Medium
Finding
The nav has two top-level sections — Personal and Enterprise — with Personal containing only 'Send money' and 'Help', and Enterprise containing 'Discover Paysend Enterprise', 'Paysend Network', 'API Reference', and 'Customer Support'. There is no homepage-level content that explains or differentiates the two products for a visitor who lands without context. A developer evaluating Paysend's Enterprise API lands on the same /send page as a grandmother sending remittances to Mexico — and has to locate 'Enterprise' in the nav without any above-the-fold signal that an enterprise product exists. The FT logo badges in the footer of the /send page are the only enterprise credibility signal visible on the consumer-facing page.
Recommendation
Create a dedicated enterprise.paysend.com or paysend.com/enterprise homepage that functions as the full enterprise product landing page — with its own hero, customer logos (Visa, Western Union, Deel partnerships), API documentation entry point, case studies, and sales CTA. The root domain and /send page serve consumers; the enterprise product deserves its own dedicated funnel. Alternatively, add an above-the-fold 'Are you a business?' banner that routes enterprise visitors immediately. The current architecture buries a $227M-funded company's B2B product inside a consumer app nav.
Navigation
Dual Audience (Personal + Enterprise) With No Homepage Separation
Score
45
Severity
Medium
Finding
The nav has two top-level sections — Personal and Enterprise — with Personal containing only 'Send money' and 'Help', and Enterprise containing 'Discover Paysend Enterprise', 'Paysend Network', 'API Reference', and 'Customer Support'. There is no homepage-level content that explains or differentiates the two products for a visitor who lands without context. A developer evaluating Paysend's Enterprise API lands on the same /send page as a grandmother sending remittances to Mexico — and has to locate 'Enterprise' in the nav without any above-the-fold signal that an enterprise product exists. The FT logo badges in the footer of the /send page are the only enterprise credibility signal visible on the consumer-facing page.
Recommendation
Create a dedicated enterprise.paysend.com or paysend.com/enterprise homepage that functions as the full enterprise product landing page — with its own hero, customer logos (Visa, Western Union, Deel partnerships), API documentation entry point, case studies, and sales CTA. The root domain and /send page serve consumers; the enterprise product deserves its own dedicated funnel. Alternatively, add an above-the-fold 'Are you a business?' banner that routes enterprise visitors immediately. The current architecture buries a $227M-funded company's B2B product inside a consumer app nav.
Copy
FT 1000 Badge Shows 2023 and 2024 Logos — Neither Updated to 2026 Recognition
Score
48
Severity
Medium
Finding
The /send page displays two FT logo badges: 'FT logo' and 'FT logo 2024'. The image filenames are ft-logo.svg (presumably 2023) and ft-logo-2024.svg. In March 2026, displaying 2023 and 2024 FT recognition badges — without a 2025 or 2026 badge — implicitly raises the question of whether Paysend was *not* recognised in 2025. The FT 1000 2026 list was recently published (confirmed by a search result about Software Mind's 2026 recognition, dated within the last 5 days). Paysend's LinkedIn shows they were on the FT 1000 list in 2024 'for the second year in a row'. If they are on the 2026 list, the badge should be updated immediately; if not, the presence of stale 2023/2024 badges creates an awkward silence.
Recommendation
Update the FT recognition badge to the most recent year Paysend has been recognised — if FT 1000 2026 is out (confirmed), check whether Paysend appears and update the badge within 48 hours of confirmation. If Paysend is not on the 2026 list, remove the dated badges entirely or replace with a more timeless formulation: 'FT 1000 Europe's Fastest-Growing Companies — 2023, 2024'. A badge explicitly showing '2023' and '2024' in a page viewed in 2026 signals either stale maintenance or a lapse in recognition — neither is the intended message.
Copy
FT 1000 Badge Shows 2023 and 2024 Logos — Neither Updated to 2026 Recognition
Score
48
Severity
Medium
Finding
The /send page displays two FT logo badges: 'FT logo' and 'FT logo 2024'. The image filenames are ft-logo.svg (presumably 2023) and ft-logo-2024.svg. In March 2026, displaying 2023 and 2024 FT recognition badges — without a 2025 or 2026 badge — implicitly raises the question of whether Paysend was *not* recognised in 2025. The FT 1000 2026 list was recently published (confirmed by a search result about Software Mind's 2026 recognition, dated within the last 5 days). Paysend's LinkedIn shows they were on the FT 1000 list in 2024 'for the second year in a row'. If they are on the 2026 list, the badge should be updated immediately; if not, the presence of stale 2023/2024 badges creates an awkward silence.
Recommendation
Update the FT recognition badge to the most recent year Paysend has been recognised — if FT 1000 2026 is out (confirmed), check whether Paysend appears and update the badge within 48 hours of confirmation. If Paysend is not on the 2026 list, remove the dated badges entirely or replace with a more timeless formulation: 'FT 1000 Europe's Fastest-Growing Companies — 2023, 2024'. A badge explicitly showing '2023' and '2024' in a page viewed in 2026 signals either stale maintenance or a lapse in recognition — neither is the intended message.
Copy
FT 1000 Badge Shows 2023 and 2024 Logos — Neither Updated to 2026 Recognition
Score
48
Severity
Medium
Finding
The /send page displays two FT logo badges: 'FT logo' and 'FT logo 2024'. The image filenames are ft-logo.svg (presumably 2023) and ft-logo-2024.svg. In March 2026, displaying 2023 and 2024 FT recognition badges — without a 2025 or 2026 badge — implicitly raises the question of whether Paysend was *not* recognised in 2025. The FT 1000 2026 list was recently published (confirmed by a search result about Software Mind's 2026 recognition, dated within the last 5 days). Paysend's LinkedIn shows they were on the FT 1000 list in 2024 'for the second year in a row'. If they are on the 2026 list, the badge should be updated immediately; if not, the presence of stale 2023/2024 badges creates an awkward silence.
Recommendation
Update the FT recognition badge to the most recent year Paysend has been recognised — if FT 1000 2026 is out (confirmed), check whether Paysend appears and update the badge within 48 hours of confirmation. If Paysend is not on the 2026 list, remove the dated badges entirely or replace with a more timeless formulation: 'FT 1000 Europe's Fastest-Growing Companies — 2023, 2024'. A badge explicitly showing '2023' and '2024' in a page viewed in 2026 signals either stale maintenance or a lapse in recognition — neither is the intended message.
Copy
Hero H1 Is a Destination Input, Not a Value Proposition
Score
50
Severity
Medium
Finding
The effective US homepage (/en-us/send) opens with the H1: 'International money transfer from the United States' followed immediately by the calculator widget ('Transfer money online to over 170 countries around the world starting from 0 USD'). This is functionally a conversion tool, not a positioning statement. There is no hero headline that explains *why* Paysend over Wise, Remitly, Western Union, or any other option. The differentiators — flat fee (not percentage-based), card-to-card in minutes, 12M customers, FCA regulated — are only visible after scrolling through the calculator into the 'Benefits' section. A first-time visitor comparing 4-5 remittance options has no reason from the above-the-fold experience to prefer Paysend.
Recommendation
Add a value-proposition H1 above the calculator: 'Send money internationally for a flat £1 / $2 / €1.50 — no percentage fees, arrives in minutes.' This single line communicates the core differentiator (fixed fee vs percentage-based competitors), the speed advantage, and the pricing transparency that Paysend is known for. The calculator can remain directly below as the primary interactive element — but visitors need the 'why Paysend' answer before they engage with the 'how much' calculator. Test a version that leads with the customer count and fee structure together: 'Trusted by 12 million customers. One flat fee. Money delivered in minutes.'
Copy
Hero H1 Is a Destination Input, Not a Value Proposition
Score
50
Severity
Medium
Finding
The effective US homepage (/en-us/send) opens with the H1: 'International money transfer from the United States' followed immediately by the calculator widget ('Transfer money online to over 170 countries around the world starting from 0 USD'). This is functionally a conversion tool, not a positioning statement. There is no hero headline that explains *why* Paysend over Wise, Remitly, Western Union, or any other option. The differentiators — flat fee (not percentage-based), card-to-card in minutes, 12M customers, FCA regulated — are only visible after scrolling through the calculator into the 'Benefits' section. A first-time visitor comparing 4-5 remittance options has no reason from the above-the-fold experience to prefer Paysend.
Recommendation
Add a value-proposition H1 above the calculator: 'Send money internationally for a flat £1 / $2 / €1.50 — no percentage fees, arrives in minutes.' This single line communicates the core differentiator (fixed fee vs percentage-based competitors), the speed advantage, and the pricing transparency that Paysend is known for. The calculator can remain directly below as the primary interactive element — but visitors need the 'why Paysend' answer before they engage with the 'how much' calculator. Test a version that leads with the customer count and fee structure together: 'Trusted by 12 million customers. One flat fee. Money delivered in minutes.'
Copy
Hero H1 Is a Destination Input, Not a Value Proposition
Score
50
Severity
Medium
Finding
The effective US homepage (/en-us/send) opens with the H1: 'International money transfer from the United States' followed immediately by the calculator widget ('Transfer money online to over 170 countries around the world starting from 0 USD'). This is functionally a conversion tool, not a positioning statement. There is no hero headline that explains *why* Paysend over Wise, Remitly, Western Union, or any other option. The differentiators — flat fee (not percentage-based), card-to-card in minutes, 12M customers, FCA regulated — are only visible after scrolling through the calculator into the 'Benefits' section. A first-time visitor comparing 4-5 remittance options has no reason from the above-the-fold experience to prefer Paysend.
Recommendation
Add a value-proposition H1 above the calculator: 'Send money internationally for a flat £1 / $2 / €1.50 — no percentage fees, arrives in minutes.' This single line communicates the core differentiator (fixed fee vs percentage-based competitors), the speed advantage, and the pricing transparency that Paysend is known for. The calculator can remain directly below as the primary interactive element — but visitors need the 'why Paysend' answer before they engage with the 'how much' calculator. Test a version that leads with the customer count and fee structure together: 'Trusted by 12 million customers. One flat fee. Money delivered in minutes.'
Freshness
Most Recent News Item Is November 2025 — Four Months Stale in March 2026
Score
48
Severity
Low
Finding
The news section (visible from the news page navigation) shows the most recent item as November 27, 2025 (JetBlue/Dominican Republic partnership). The January 22, 2026 AI capabilities announcement seen on Quentic's homepage is more recent than Paysend's most recent visible news item. For a fintech processing millions of transfers in a regulated environment, four months without a visible news update signals either a quiet PR operation or — more concerning to compliance-aware users — inactivity. Partnerships with Visa (October 2025), TelevisaUnivision (July 2025), and Tink (April 2025) were all significant but the cadence drops off in Q4 2025.
Recommendation
Establish a monthly news publishing cadence — at minimum one press release or product announcement per month. Content opportunities available right now: the JetBlue TrueBlue promotion ending March 30, 2026 (a natural 'last chance' news peg); any FT 1000 2026 recognition; new sending corridors or payout methods; Q4 2025 / FY2025 growth figures (£63.6M revenue in 2023 per Tracxn — a 2025 update would be compelling). The news section is also a trust signal for regulated financial services: active, date-stamped news tells regulators, compliance reviewers, and cautious users that the company is operational and communicating.
Freshness
Most Recent News Item Is November 2025 — Four Months Stale in March 2026
Score
48
Severity
Low
Finding
The news section (visible from the news page navigation) shows the most recent item as November 27, 2025 (JetBlue/Dominican Republic partnership). The January 22, 2026 AI capabilities announcement seen on Quentic's homepage is more recent than Paysend's most recent visible news item. For a fintech processing millions of transfers in a regulated environment, four months without a visible news update signals either a quiet PR operation or — more concerning to compliance-aware users — inactivity. Partnerships with Visa (October 2025), TelevisaUnivision (July 2025), and Tink (April 2025) were all significant but the cadence drops off in Q4 2025.
Recommendation
Establish a monthly news publishing cadence — at minimum one press release or product announcement per month. Content opportunities available right now: the JetBlue TrueBlue promotion ending March 30, 2026 (a natural 'last chance' news peg); any FT 1000 2026 recognition; new sending corridors or payout methods; Q4 2025 / FY2025 growth figures (£63.6M revenue in 2023 per Tracxn — a 2025 update would be compelling). The news section is also a trust signal for regulated financial services: active, date-stamped news tells regulators, compliance reviewers, and cautious users that the company is operational and communicating.
Freshness
Most Recent News Item Is November 2025 — Four Months Stale in March 2026
Score
48
Severity
Low
Finding
The news section (visible from the news page navigation) shows the most recent item as November 27, 2025 (JetBlue/Dominican Republic partnership). The January 22, 2026 AI capabilities announcement seen on Quentic's homepage is more recent than Paysend's most recent visible news item. For a fintech processing millions of transfers in a regulated environment, four months without a visible news update signals either a quiet PR operation or — more concerning to compliance-aware users — inactivity. Partnerships with Visa (October 2025), TelevisaUnivision (July 2025), and Tink (April 2025) were all significant but the cadence drops off in Q4 2025.
Recommendation
Establish a monthly news publishing cadence — at minimum one press release or product announcement per month. Content opportunities available right now: the JetBlue TrueBlue promotion ending March 30, 2026 (a natural 'last chance' news peg); any FT 1000 2026 recognition; new sending corridors or payout methods; Q4 2025 / FY2025 growth figures (£63.6M revenue in 2023 per Tracxn — a 2025 update would be compelling). The news section is also a trust signal for regulated financial services: active, date-stamped news tells regulators, compliance reviewers, and cautious users that the company is operational and communicating.
Social Proof
App Store Ratings Not Surfaced on Web Homepage
Score
52
Severity
Low
Finding
Paysend has extremely strong mobile app ratings: 4.8/5 on Google Play from 122,000+ reviews, and 4.8/5 on the App Store from 19,000+ ratings. These are exceptional figures that significantly outperform the 4.1 Trustpilot aggregate. The /send page shows app store download badges (App Store, Google Play, AppGallery) but does not display the star ratings or review counts alongside them. Wise displays its app store ratings prominently; Remitly features '4.9 stars, 500,000+ reviews' directly on its homepage hero. Paysend's highest social proof signals (4.8 from 122K reviews) are invisible at the point where download decisions are made.
Recommendation
Add star ratings and review counts directly beneath the App Store and Google Play download badges on the /send page: '⭐ 4.8 · 122,000+ reviews' (Google Play) and '⭐ 4.8 · 19,000+ ratings' (App Store). These numbers are dramatically stronger than the Trustpilot aggregate and should be the primary social proof element for a mobile-first remittance service. Consider A/B testing a hero variant that leads with '4.8 stars on 122,000+ Google Play reviews' as the primary trust signal above the calculator — this is more persuasive than any copywritten claim and directly addresses the 'is this safe?' hesitation of first-time remittance senders.
Social Proof
App Store Ratings Not Surfaced on Web Homepage
Score
52
Severity
Low
Finding
Paysend has extremely strong mobile app ratings: 4.8/5 on Google Play from 122,000+ reviews, and 4.8/5 on the App Store from 19,000+ ratings. These are exceptional figures that significantly outperform the 4.1 Trustpilot aggregate. The /send page shows app store download badges (App Store, Google Play, AppGallery) but does not display the star ratings or review counts alongside them. Wise displays its app store ratings prominently; Remitly features '4.9 stars, 500,000+ reviews' directly on its homepage hero. Paysend's highest social proof signals (4.8 from 122K reviews) are invisible at the point where download decisions are made.
Recommendation
Add star ratings and review counts directly beneath the App Store and Google Play download badges on the /send page: '⭐ 4.8 · 122,000+ reviews' (Google Play) and '⭐ 4.8 · 19,000+ ratings' (App Store). These numbers are dramatically stronger than the Trustpilot aggregate and should be the primary social proof element for a mobile-first remittance service. Consider A/B testing a hero variant that leads with '4.8 stars on 122,000+ Google Play reviews' as the primary trust signal above the calculator — this is more persuasive than any copywritten claim and directly addresses the 'is this safe?' hesitation of first-time remittance senders.
Social Proof
App Store Ratings Not Surfaced on Web Homepage
Score
52
Severity
Low
Finding
Paysend has extremely strong mobile app ratings: 4.8/5 on Google Play from 122,000+ reviews, and 4.8/5 on the App Store from 19,000+ ratings. These are exceptional figures that significantly outperform the 4.1 Trustpilot aggregate. The /send page shows app store download badges (App Store, Google Play, AppGallery) but does not display the star ratings or review counts alongside them. Wise displays its app store ratings prominently; Remitly features '4.9 stars, 500,000+ reviews' directly on its homepage hero. Paysend's highest social proof signals (4.8 from 122K reviews) are invisible at the point where download decisions are made.
Recommendation
Add star ratings and review counts directly beneath the App Store and Google Play download badges on the /send page: '⭐ 4.8 · 122,000+ reviews' (Google Play) and '⭐ 4.8 · 19,000+ ratings' (App Store). These numbers are dramatically stronger than the Trustpilot aggregate and should be the primary social proof element for a mobile-first remittance service. Consider A/B testing a hero variant that leads with '4.8 stars on 122,000+ Google Play reviews' as the primary trust signal above the calculator — this is more persuasive than any copywritten claim and directly addresses the 'is this safe?' hesitation of first-time remittance senders.
SEO
snackbar.browsers.title / snackbar.browsers.text — i18n Keys Rendering in Page Source
Score
36
Severity
High
Finding
The HTML source of Paysend pages contains unfilled internationalisation (i18n) translation keys rendering as literal strings: 'snackbar.browsers.title' and 'snackbar.browsers.text' appear in the page output. These are untranslated localisation keys from the i18n framework — strings that were supposed to be replaced with actual copy during the build/render process but were not. While these may not be visible to standard users (they likely appear in a browser compatibility snackbar for IE/legacy browsers), they are present in the HTML source where Google's crawler reads them. Any page that ships with raw i18n key names in the source has a broken localisation pipeline for at least one render path.
Recommendation
Audit the i18n pipeline for all Paysend locales to identify which translation keys are missing values. 'snackbar.browsers.title' and 'snackbar.browsers.text' are likely targeted at users on unsupported browsers (Internet Explorer, older Safari), but the fallback should display readable copy — e.g. 'For the best Paysend experience, please use Chrome, Firefox, or Safari.' — not raw key names. Set up automated tests in the CI/CD pipeline that fail the build if any i18n key resolves to its own key name rather than a translated string. This is a basic localisation quality gate that prevents untranslated keys from reaching production.
SEO
snackbar.browsers.title / snackbar.browsers.text — i18n Keys Rendering in Page Source
Score
36
Severity
High
Finding
The HTML source of Paysend pages contains unfilled internationalisation (i18n) translation keys rendering as literal strings: 'snackbar.browsers.title' and 'snackbar.browsers.text' appear in the page output. These are untranslated localisation keys from the i18n framework — strings that were supposed to be replaced with actual copy during the build/render process but were not. While these may not be visible to standard users (they likely appear in a browser compatibility snackbar for IE/legacy browsers), they are present in the HTML source where Google's crawler reads them. Any page that ships with raw i18n key names in the source has a broken localisation pipeline for at least one render path.
Recommendation
Audit the i18n pipeline for all Paysend locales to identify which translation keys are missing values. 'snackbar.browsers.title' and 'snackbar.browsers.text' are likely targeted at users on unsupported browsers (Internet Explorer, older Safari), but the fallback should display readable copy — e.g. 'For the best Paysend experience, please use Chrome, Firefox, or Safari.' — not raw key names. Set up automated tests in the CI/CD pipeline that fail the build if any i18n key resolves to its own key name rather than a translated string. This is a basic localisation quality gate that prevents untranslated keys from reaching production.
SEO
snackbar.browsers.title / snackbar.browsers.text — i18n Keys Rendering in Page Source
Score
36
Severity
High
Finding
The HTML source of Paysend pages contains unfilled internationalisation (i18n) translation keys rendering as literal strings: 'snackbar.browsers.title' and 'snackbar.browsers.text' appear in the page output. These are untranslated localisation keys from the i18n framework — strings that were supposed to be replaced with actual copy during the build/render process but were not. While these may not be visible to standard users (they likely appear in a browser compatibility snackbar for IE/legacy browsers), they are present in the HTML source where Google's crawler reads them. Any page that ships with raw i18n key names in the source has a broken localisation pipeline for at least one render path.
Recommendation
Audit the i18n pipeline for all Paysend locales to identify which translation keys are missing values. 'snackbar.browsers.title' and 'snackbar.browsers.text' are likely targeted at users on unsupported browsers (Internet Explorer, older Safari), but the fallback should display readable copy — e.g. 'For the best Paysend experience, please use Chrome, Firefox, or Safari.' — not raw key names. Set up automated tests in the CI/CD pipeline that fail the build if any i18n key resolves to its own key name rather than a translated string. This is a basic localisation quality gate that prevents untranslated keys from reaching production.
Copy
Western Union Partnership — Announced April 2024, Not Visible on Homepage
Score
50
Severity
Low
Finding
Paysend announced a partnership with Western Union in April 2024 — one of the most recognisable brand names in global remittances with 150+ years of heritage and instant credibility for trust-hesitant first-time users. The partnership was positioned to 'enhance global money transfer solutions' and would plausibly be the single most impactful trust signal Paysend could display. However the /send homepage shows no Western Union logo, no partnership mention, and no reference to the collaboration. The Mastercard, Visa, and UnionPay network logos appear in the footer — but these are processor relationships. A named Western Union partnership is a consumer trust signal of a different order entirely.
Recommendation
Add the Western Union partnership logo/mention to the homepage trust strip, either alongside the Mastercard/Visa network logos or in a dedicated 'Our partners' section. For a consumer audience where Western Union is a household name for international transfers, 'powered in partnership with Western Union' or 'part of the Western Union network' acts as an instant legitimacy transfer. Similarly, the Mastercard Libre product (launched in Mexico) and Visa Enterprise API expansion deserve homepage mention in the Enterprise section. Audit all major 2024-2025 partnerships and surface the three most consumer-recognisable ones above the fold.
Copy
Western Union Partnership — Announced April 2024, Not Visible on Homepage
Score
50
Severity
Low
Finding
Paysend announced a partnership with Western Union in April 2024 — one of the most recognisable brand names in global remittances with 150+ years of heritage and instant credibility for trust-hesitant first-time users. The partnership was positioned to 'enhance global money transfer solutions' and would plausibly be the single most impactful trust signal Paysend could display. However the /send homepage shows no Western Union logo, no partnership mention, and no reference to the collaboration. The Mastercard, Visa, and UnionPay network logos appear in the footer — but these are processor relationships. A named Western Union partnership is a consumer trust signal of a different order entirely.
Recommendation
Add the Western Union partnership logo/mention to the homepage trust strip, either alongside the Mastercard/Visa network logos or in a dedicated 'Our partners' section. For a consumer audience where Western Union is a household name for international transfers, 'powered in partnership with Western Union' or 'part of the Western Union network' acts as an instant legitimacy transfer. Similarly, the Mastercard Libre product (launched in Mexico) and Visa Enterprise API expansion deserve homepage mention in the Enterprise section. Audit all major 2024-2025 partnerships and surface the three most consumer-recognisable ones above the fold.
Copy
Western Union Partnership — Announced April 2024, Not Visible on Homepage
Score
50
Severity
Low
Finding
Paysend announced a partnership with Western Union in April 2024 — one of the most recognisable brand names in global remittances with 150+ years of heritage and instant credibility for trust-hesitant first-time users. The partnership was positioned to 'enhance global money transfer solutions' and would plausibly be the single most impactful trust signal Paysend could display. However the /send homepage shows no Western Union logo, no partnership mention, and no reference to the collaboration. The Mastercard, Visa, and UnionPay network logos appear in the footer — but these are processor relationships. A named Western Union partnership is a consumer trust signal of a different order entirely.
Recommendation
Add the Western Union partnership logo/mention to the homepage trust strip, either alongside the Mastercard/Visa network logos or in a dedicated 'Our partners' section. For a consumer audience where Western Union is a household name for international transfers, 'powered in partnership with Western Union' or 'part of the Western Union network' acts as an instant legitimacy transfer. Similarly, the Mastercard Libre product (launched in Mexico) and Visa Enterprise API expansion deserve homepage mention in the Enterprise section. Audit all major 2024-2025 partnerships and surface the three most consumer-recognisable ones above the fold.
Frequently asked
What kind of companies do you work with?
We work with ambitious tech companies — typically Series A and B — at the moment where the brand and website haven't kept pace with the business.
You've found product-market fit. Now you need to look the part, communicate clearly, and move fast enough to stay ahead.
That's the problem we're built for.
What does a typical project look like?
We've had bad experiences with agencies before. What's different?
Why Framer over other platforms?
How do we get started?
How does pricing work?
Recent work
V7 Labs
Utila
Buena
Enzai
Centific
trawa
Portex Global
Othello AI
Echo
Pools
Contentcloud
Wilson
Perspectives & Insights
Blazing fast brands &
Blazing fast brands &
Blazing fast brands &
websites for startups
websites for startups
websites for startups