Skip to main content

Security report for finchpay.io

UAB FINCH TECHNOLOGIES · Finance · Lithuania

Low risk. 3 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

79/100

Risk levelLow

0–100, higher is better. How it is calculated

FinchPay is a Lithuania-based cryptocurrency exchange platform founded in 2021, offering secure and reliable services for buying and selling cryptocurrencies for fiat currencies. The company operates under EU regulation with Virtual Asset Service Provider registration, serving over 100 countries and supporting more than 20 cryptocurrencies. Their business model focuses on providing fast, convenient crypto transactions with integrated payment methods including bank cards and alternative options. The platform targets institutional and professional clients, emphasizing compliance, security, and user experience. Technically, FinchPay employs a modern technology stack including React and Next.js, hosted with Cloudflare DNS and CDN services. The website is fast, mobile-optimized, and well-structured with good SEO and accessibility features. Analytics are implemented via Google Tag Manager, and the site integrates third-party widgets for currency calculations and crypto transactions. From a security perspective, FinchPay enforces HTTPS, uses clientTransferProhibited domain status, and integrates automated KYC/AML verification for transactions exceeding 500 EUR. While explicit security headers are not fully confirmed, the platform uses recognized anti-fraud and anti-money laundering solutions. No critical vulnerabilities or suspicious activities were detected. The domain WHOIS data shows privacy protection typical for fintech startups, with registration consistent with the company’s founding date and business claims. Overall, FinchPay presents a professional, trustworthy, and compliant cryptocurrency exchange service with strong EU regulatory backing. Recommendations include enabling DNSSEC, publishing a security policy or incident response page, and adding a vulnerability disclosure mechanism to further enhance security posture and transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

3 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

Need hands-on remediation? Email guard@offseq.com

Keep watching finchpay.io

This scan found 17 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. The full timeline opens with your unlock code.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
75
Security headers
65
Email security
85
DNS health
80
Network security
100
GDPR outside view
68
Average
79

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

FinchPay positions itself as a secure and EU-regulated cryptocurrency exchange targeting institutional and professional clients globally. Its competitive advantages include regulatory compliance, a broad range of supported cryptocurrencies and fiat currencies, and multiple payment methods. The business model revolves around transaction fees and payment processing services. The company demonstrates growth potential through continuous addition of new coins and expansion of payment options. Partnerships with exchange aggregators and media platforms enhance its market presence. The company maintains a small size with focused operations in Lithuania and Poland, leveraging technology to deliver fast and reliable crypto transactions.

Security posture

FinchPay exhibits a mature security posture with enforced HTTPS, clientTransferProhibited domain status, and integration of third-party anti-fraud and AML solutions. Automated KYC/AML verification for transactions above 500 EUR adds a layer of compliance and fraud prevention. However, explicit security headers like X-Frame-Options and X-Content-Type-Options are not clearly present, and no public security or incident response policies were found. The absence of a vulnerability disclosure program or security.txt file indicates room for improvement in transparency and community engagement. Overall, the platform is secure but could enhance its security communication and DNS security by enabling DNSSEC.

Recommendations

  1. Enable DNSSEC to improve DNS security and prevent spoofing.
  2. Publish a dedicated security policy and incident response page to increase transparency.
  3. Implement and document explicit security headers such as X-Frame-Options and X-Content-Type-Options.
  4. Establish a vulnerability disclosure program or publish a security.txt file to encourage responsible reporting.
  5. Continue expanding payment methods and maintain strong regulatory compliance to enhance market trust.

Contact details published on the site

Addresses
Legal name
UAB FINCH TECHNOLOGIES
Registration number
306113100
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
UAB FINCH TECHNOLOGIES
Description
FinchPay offers a secure and reliable solution for buying and selling cryptocurrencies for fiat currencies.
Key services
Buy and sell cryptocurrencies, Payment processing via bank cards and alternative methods, Over-the-counter (OTC) trading, Cryptocurrency wallet integration
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Cloudflare DNS, Google Tag Manager, Custom JavaScript widgets
Frameworks
Next.js
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • ClientTransferProhibited domain status
  • EU regulatory compliance
  • Automated KYC/AML verification for transactions > 500 EUR
  • Use of third-party anti-fraud and anti-money laundering solutions

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
good

Advertising

Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Strong EU regulatory compliance and VASP registration.
  3. Comprehensive legal and policy documents available.
  4. Clear contact information with multiple channels.
  5. Modern, performant, and mobile-optimized website.
  6. Use of reputable third-party services for analytics and payment processing.
  7. No signs of suspicious or malicious activity.
  8. Good trust signals including reviews and partner logos.
Technical notes

Notes

The website is built on a modern React and Next.js framework, ensuring server-side rendering and good SEO performance. Hosting and DNS are managed via Cloudflare, providing CDN and security benefits. The site loads quickly and is mobile-optimized with responsive design. Analytics are implemented through Google Tag Manager, and external widgets are used for currency calculations and crypto transactions. No CMS is detected, indicating a custom-built platform. The technical infrastructure is robust with minimal technical debt, though enabling DNSSEC and enhancing security headers would further strengthen the platform.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with finchpay.io. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review finchpay.io.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.