Skip to main content

Security report for vr-payment.de

VR Payment GmbH · Finance · Germany

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

Security score

62/100

Risk levelMedium

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

VR Payment GmbH is a specialized payment solutions provider serving the Volksbanken Raiffeisenbanken network and their merchants. The company offers a broad range of services including card readers, terminals, cashless payment methods, e-commerce payment integration, and value-added services such as digital receipt management and mobile payment solutions. The website reflects a professional and consistent brand presence targeting merchants, banks, and resellers within the financial and payment technology sectors in Germany. The company maintains a medium-sized market presence with a focus on innovation and customer-centric payment solutions. Technically, the website is built on the Contao CMS platform and leverages modern JavaScript libraries such as jQuery, jQuery UI, and Swipe.js for UI interactions. It uses Matomo for analytics and Usercentrics for consent management, indicating a mature approach to user privacy and data tracking. However, the website suffers from a critical security deficiency due to an invalid or missing SSL certificate and lack of enabled TLS protocols, which severely undermines HTTPS security and user trust. From a security perspective, while the site has HSTS enabled with preload and a valid SPF record, the absence of a valid SSL certificate and TLS support is a major vulnerability. No incident response or explicit security policy information is found, and no vulnerability disclosure or security.txt file is present. Privacy compliance is well addressed with a comprehensive privacy policy and cookie consent mechanism. Contact information is readily available through multiple channels including email, phone, and detailed contact forms. Overall, the website is content-rich, professionally designed, and privacy-conscious but critically impaired by its SSL/TLS configuration issues. Immediate remediation of the SSL certificate and enabling modern TLS protocols is essential to restore security posture and trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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

5 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  2. 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';…

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

Keep watching vr-payment.de

This scan found 17 issues across 5 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. See sample alerts.

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
100
Security headers
85
Email security
70
DNS health
80
Network security
20
GDPR outside view
18
Average
62

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention vr-payment.de, from OffSeq Breach.

Total records
23
Employees
0
Customers
15
Third parties
8
Weak passwords
0%

4 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for vr-payment.de.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

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

Business context

Business profile

VR Payment GmbH operates as a key payment service provider within the German banking ecosystem, specifically aligned with Volksbanken Raiffeisenbanken. Its business model revolves around providing end-to-end payment solutions including hardware (card readers and terminals), software (e-commerce payment integration), and services (digital receipt management, mobile payment apps). The company targets merchants of various sizes, banks, and resellers, offering tailored solutions for POS and online commerce. The presence of partner portals and service portals indicates a well-established partner ecosystem. The company leverages certifications and compliance to build trust and maintain regulatory adherence. Growth indicators include a comprehensive service portfolio and active content marketing via the #PaymentPower magazine and social media channels. Strategic partnerships with banks and technology providers strengthen its market position.

Security posture

The current security posture of the website is moderate to poor due to the absence of a valid SSL certificate and disabled TLS protocols, which are critical for secure communications. While HSTS is enabled with preload, this is ineffective without proper HTTPS support. The SPF record is correctly configured, reducing email spoofing risks. No known vulnerabilities such as Heartbleed or POODLE are detected. The site uses secure forms with GDPR-compliant consent checkboxes, indicating awareness of data protection requirements. However, the lack of incident response contact information and vulnerability disclosure mechanisms limits transparency and readiness for security incidents. The site would benefit from enhanced security headers and improved certificate management to elevate its security maturity.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable secure HTTPS connections.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions to ensure secure data transmission.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Publish a security policy and incident response contact information to improve transparency and readiness.
  5. Add a security.txt file or vulnerability disclosure policy to encourage responsible reporting of security issues.
  6. Enhance security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  7. Optimize website performance to reduce load times and improve user experience.
  8. Continue maintaining GDPR compliance and transparent privacy practices.
Technical notes

Notes

The website is built on the Contao Open Source CMS platform, utilizing jQuery, jQuery UI, and Swipe.js for frontend interactions. It integrates Matomo analytics for user tracking and Usercentrics for consent management, reflecting a modern approach to privacy and analytics. DNS is managed via atruvia.de nameservers, and SPF records are properly configured. However, the SSL/TLS configuration is critically flawed with no valid certificate and no enabled TLS protocols, severely impacting security and trust. The site has a large page size (~428 KB) and slow load time (~8.8 seconds), indicating potential optimization opportunities. Structured data is implemented using JSON-LD for SEO benefits. Overall, the technical stack is mature but requires urgent security and performance improvements.
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 vr-payment.de. 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 vr-payment.de.

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.