Payment processor

Paymaster (RunPay): perimeter and web application testing for a payment processor

Paymaster wanted to know its real exposure to external threats: the perimeter, applications and web services, tested both without an account and authenticated.

Engagement
Perimeter test; web applications, unauthenticated and authenticated
Reference
OWASP Top 10
Letter
26 January 2026

At a glance

The challenge

Assessing the real exposure to external cyber threats for the infrastructure and applications of a licensed payment processor.

The approach

A perimeter test plus scanning of web applications and services, both unauthenticated and authenticated, from an external attacker's perspective, per OWASP Top 10.

The outcome

Identified relevant vulnerabilities with clearly defined impact; a detailed report with findings, risk assessment and remediation recommendations.

In the client’s words

"The tests were carried out from the perspective of an external attacker without privileged access, using structured methodologies and realistic attack scenarios, in line with industry best practice and the OWASP Top 10 reference framework. […] The work led to the identification of relevant vulnerabilities with a clearly defined impact on information security. […] Paymaster considers BSD Management a trustworthy and competent partner."

— IT Director, Paymaster S.R.L. (RunPay)Translated from Romanian; the original letter is in Romanian.

How we run an engagement like this

The steps below describe our usual method for this type of engagement, not the details of the client’s project.

  1. Scope and rules of engagement

    Together we agree what is tested, from where and when, who the emergency contact is and what is off limits. Nothing starts without written authorization.

  2. Reconnaissance

    We start as an outside attacker with no information from the client: which services, applications and entry points are visible from the internet.

  3. Manual testing

    We try every entry point with realistic attack scenarios, using the OWASP Top 10 as a reference, not just automated scanners.

  4. Confirming the findings

    Every vulnerability is confirmed by hand and rated by its real impact, so the report contains no false alarms.

  5. Report and walkthrough

    A summary for management, technical detail for the IT team and remediation advice in order of priority.

  6. Retesting

    After remediation we check the findings again and confirm what has been closed.

What the client received

As the client describes them in the letter.

  • A detailed report: description of findings, risk assessment and remediation advice
  • Relevant vulnerabilities, each with a clearly defined impact
  • Communication aligned with the client’s project-management requirements
  • Delivered on the agreed terms

Related services

Other case studies

← All case studies

Want the same results for your organization?

Book a free consultation and get a quote tailored to your scope — with no hidden costs.