Skip to main content

Security report for trustly.com

Trustly Group AB · Finance · Sweden

Medium risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

72/100

Risk levelMedium

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

Trustly Group AB is a leading payment service provider specializing in Pay by Bank solutions that enable secure, instant bank payments for businesses globally. With over 16 years of Open Banking experience, Trustly powers a large network connecting thousands of merchants to hundreds of millions of consumers. Their services include payment processing, recurring payments, data services, deposits, payouts, and a proprietary data engine called Trustly Azura. The company is regulated by Swedish and UK financial authorities and holds ISO 27001 certification, reflecting a strong commitment to security and compliance. Technically, Trustly's website is built on modern web technologies including Webflow CMS, AWS CloudFront hosting, and advanced JavaScript libraries for animations and user experience. The site is well optimized for performance, mobile responsiveness, and accessibility. Security headers and HTTPS enforcement are properly implemented, although some improvements like HSTS preload and OCSP stapling could enhance security further. From a security posture perspective, Trustly demonstrates enterprise-grade protection with certifications, regulatory oversight, and robust incident management processes. No critical vulnerabilities or exposures were detected. Privacy compliance is strong with GDPR adherence, cookie consent mechanisms, and transparent policies. Overall, Trustly presents a highly professional, trustworthy, and technically mature online presence that aligns well with its market leadership in financial technology. Strategic recommendations include enhancing SSL configurations, publishing a security.txt file, and continuing to maintain transparency and compliance to sustain trust and competitive advantage.

Scanned

This is an earlier scan of trustly.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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 Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • 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

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

Keep watching trustly.com

This scan found 15 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
82
Security headers
70
Email security
50
DNS health
85
Network security
100
GDPR outside view
43
Average
72

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

Trustly occupies a strong market position as a Pay by Bank leader with a comprehensive suite of payment and data services tailored for B2B clients across multiple industries including finance, e-commerce, travel, and utilities. Their business model focuses on direct bank payments that reduce friction and fraud while improving conversion rates. The company serves a large global customer base with localized subsidiaries and regional domains. Trustly's partnership ecosystem includes major brands and payment service providers, enhancing its market reach and credibility. Growth indicators include processing over $10 billion annually and handling hundreds of millions of transactions. The company emphasizes innovation through its Azura data engine and maintains a strong compliance and security posture to meet regulatory demands.

Security posture

Trustly demonstrates a mature security posture with enterprise-grade controls and certifications such as ISO 27001 and TÜV Saarland accreditation. The website enforces HTTPS with strong security headers including HSTS, XSS protection, and frame options. No known SSL/TLS vulnerabilities are present, and cookies are set with secure flags. The company complies with KYC, AML, and CTF regulations and operates under financial supervisory authorities in Sweden and the UK. Incident management processes include 24/7 support and tested business continuity plans. However, OCSP stapling is not enabled and certificate transparency compliance is lacking. There is no public vulnerability disclosure or security.txt file detected. Overall, the security culture appears robust with room for incremental improvements.

Recommendations

  1. Enable HSTS with includeSubDomains and preload to strengthen HTTPS enforcement.
  2. Implement OCSP stapling to improve SSL certificate revocation checking performance and security.
  3. Publish a security.txt file to facilitate responsible vulnerability disclosure and improve transparency.
  4. Add a Content Security Policy (CSP) header to mitigate cross-site scripting and related attacks.
  5. Ensure certificate transparency compliance to enhance trust and detect fraudulent certificates.

Contact details published on the site

Legal name
Trustly Group AB
Registration number
556754-8655
Technical notes

Notes

The website is hosted on AWS CloudFront CDN and built using Webflow CMS, leveraging modern JavaScript libraries such as GSAP for animations, Splide.js for sliders, and Lottie for vector animations. It uses jQuery 3.5.1 and integrates Piwik PRO for analytics and tracking. The site is well optimized for fast loading and mobile responsiveness, with accessibility features such as keyboard navigation and ARIA attributes implemented in interactive components like accordions and dropdowns. Meta tags and Open Graph data are properly configured for SEO and social sharing. The technical stack reflects a modern, scalable infrastructure suitable for an enterprise-grade fintech company. Minor technical debt includes missing OCSP stapling and incomplete certificate transparency compliance.
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

Earlier scans of this domain

  1. 78/100 +1Low22 findingsView report
  2. 77/100Low22 findingsView report
Reviews of this site

Share your experience with trustly.com. 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 trustly.com.

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.