Skip to main content

Security report for zarpay.app

ZAR Wallet · Finance · N/a

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

Security score

65/100

Risk levelMedium

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

ZAR Wallet is a fintech platform offering a borderless USD wallet service available in over 110 countries. It enables users, particularly in cash-based economies, to convert cash into digital dollars instantly through a network of local merchants (agents). The platform also provides virtual and physical Visa debit cards integrated with Apple Pay and Google Pay, allowing global spending without foreign transaction fees. The business model centers on a 1% platform fee on transactions, targeting underserved populations to accelerate stablecoin adoption. Technically, the website is built on Webflow with modern web technologies including GSAP for animations, Lenis for smooth scrolling, and Facebook Pixel for tracking. The site is mobile optimized, fast loading, and uses HTTPS with CDN hosting via AWS Cloudfront. However, it lacks some security headers and a cookie consent mechanism, which are areas for improvement. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. There are no visible vulnerabilities or outdated libraries. However, the absence of published security policies and incident response contacts reduces transparency. Privacy compliance is basic, with a privacy policy present but no explicit GDPR compliance or cookie consent. Overall, ZAR Wallet presents a professional and trustworthy fintech service with a clear business focus and modern technical implementation. Strategic improvements in privacy compliance, security policy transparency, and user data protection would enhance trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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

5 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching zarpay.app

This scan found 26 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. 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
72
Security headers
30
Email security
55
DNS health
80
Network security
100
GDPR outside view
53
Average
65

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

ZAR Wallet occupies a niche in the fintech sector by bridging cash economies and digital stablecoins, targeting users in emerging markets who lack traditional banking access. Its agent-based model allows local merchants to facilitate cash-to-digital dollar exchanges, creating new revenue streams for agents and expanding financial inclusion. The platform's integration with global payment networks and mobile wallets positions it competitively for cross-border spending. The company leverages social media for brand presence but could benefit from expanded contact channels and clearer corporate disclosures to strengthen credibility and customer trust.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and no apparent exposure of sensitive information. The use of third-party scripts like Facebook Pixel is managed asynchronously, reducing performance impact. However, the lack of security headers such as Content Security Policy (CSP), HSTS, and X-Frame-Options is a gap. No incident response or vulnerability disclosure policies are published, which limits transparency and preparedness. Privacy compliance is minimal, with no cookie consent mechanism despite tracking usage. Addressing these gaps would improve the security posture and regulatory compliance.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, and X-Frame-Options to mitigate common web attacks.
  2. Publish a detailed security policy and incident response plan accessible to users and security researchers.
  3. Add a cookie consent banner to comply with GDPR and other privacy regulations given the use of tracking pixels.
  4. Expand contact information to include phone numbers and physical addresses to enhance business credibility.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerabilities are introduced.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
ZAR Wallet
Description
ZAR is a borderless USD wallet available in 110+ countries, enabling users to save and spend in dollars globally without traditional banking limitations. It bridges the gap between cash-based economies and web3, accelerating stablecoin adoption for underserved populations. The platform facilitates instant cash-to-digital dollar exchanges via local merchants (agents), offers virtual and physical Visa debit cards, and supports Apple Pay and Google Pay. Users can avoid foreign transaction fees and access funds worldwide.
Key services
Cash to digital dollar exchange via agents, Virtual and physical Visa debit cards, Integration with Apple Pay and Google Pay, Agent network for buying and selling digital dollars, Mobile app for wallet management
Content quality
good
Branding
consistent

Technology

Stack
Webflow, Google Fonts, Facebook Pixel, Lenis (smooth scrolling), GSAP (animation), SplitType (text animation), jQuery
Frameworks
Webflow CMS
Platforms
Web
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of Facebook Pixel with async loading
  • No visible vulnerable libraries

Analytics and tracking

Services
Facebook Pixel
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented with clear business focus on digital dollar wallets and agent network.
  3. No cookie consent mechanism detected despite use of tracking pixels.
  4. Contact information limited to a single email address; no phone or physical address found.
  5. No explicit security or incident response policies published.
  6. Use of modern web technologies and animations enhances user experience.
  7. Social media presence on Facebook, Instagram, and X (Twitter) is evident.
  8. Privacy policy and terms of service pages are present but privacy policy is basic and lacks GDPR compliance indicators.
Technical notes

Notes

The website is built using Webflow CMS, leveraging modern JavaScript libraries such as GSAP for animations and Lenis for smooth scrolling. It uses Google Fonts and Facebook Pixel for tracking and marketing analytics. Hosting is via AWS Cloudfront CDN, ensuring fast content delivery globally. The site is mobile responsive with good SEO meta tags and Open Graph data for social sharing. Accessibility features are basic but present. There is no evidence of legacy or vulnerable libraries. Performance is optimized with asynchronous script loading and image optimization. Opportunities exist to enhance accessibility and implement advanced security headers.
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 zarpay.app. 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 zarpay.app.

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.