Insights Contact

Data, AI and Testing

Open-Source Software Compliance for Payment Firms

By SP Sankar

Almost every payment app, gateway and core banking system is built on open-source code: Java frameworks, Node.js packages, Python libraries, Linux images and databases. Often 70 to 90 percent of the code that runs in production was written by someone outside the company. That is fine, and usually good. But it creates three duties that regulators and card schemes now check: know what you run, keep it supported and patched, and use it under the right licence.

This guide explains those duties in plain words and gives a simple way to meet them. The dates for each change are on our Open-Source Software Compliance Tracker.

Why payment firms must care

  • PCI DSS: version 4 asks you to keep an inventory of your custom software and the third-party components inside it, and to patch critical security fixes quickly. An old library with a known flaw can fail an assessment.
  • EU Cyber Resilience Act: firms that sell software with digital parts in the EU must handle vulnerabilities for its whole life, report actively exploited flaws, and keep a software bill of materials. Reporting duties come first; the full rules follow later.
  • EU operational resilience (DORA) and bank regulators everywhere: they expect you to manage technology and third-party risk, and open-source code is part of that supply chain.
  • US secure software practices: the NIST Secure Software Development Framework is the common yardstick, and US government buyers ask suppliers to confirm they follow it.
  • Customers: banks now send security questionnaires that ask for your software bill of materials and your patch times.

The four risks

  • End of life: when a version stops getting security fixes (for example an old Java framework, Node.js release or database), every new flaw stays open. Running unsupported software is one of the most common audit findings.
  • Known vulnerabilities: a public flaw in a library you use, sometimes already being exploited. Speed matters most here.
  • Licences: permissive licences such as MIT and Apache 2.0 are easy to use. Copyleft licences such as GPL and AGPL can require you to share your own code, and AGPL can apply even when you only run the software as an online service.
  • Supply chain attacks: fake packages with names close to real ones, hijacked maintainer accounts, or tampered builds. Package registries now publish provenance so you can check where a package was built.

Five steps that work

1. Knowwhat you run2. Watchfor changes3. Decidewhat matters4. Fixon time5. Proveit to auditors
The five steps of open-source compliance

Read the boxes left to right. Each step feeds the next, and the last step, proof, is what auditors and bank customers ask to see.

  1. Know what you run. Generate a software bill of materials (SBOM) for every application in the build pipeline, in a standard format such as CycloneDX or SPDX. Include container images, not only application code.
  2. Watch for changes. Scan the SBOM every day against vulnerability databases and end-of-life calendars. Follow the release plans of your main frameworks, so an end-of-life date is a planned upgrade, not a surprise.
  3. Decide what matters. Not every alert is urgent. Rank by severity, whether it is being exploited, and whether the affected code is reachable in a payment flow. Write the decision down.
  4. Fix it on time. Set patch targets, for example critical flaws within days and high flaws within a month, and plan upgrades at least 90 days before end of life. Test the upgrade like any other payments release: regression, performance and certification where needed.
  5. Prove it. Keep the SBOM, scan results, risk decisions and approvals. A clean evidence trail turns an audit from weeks of searching into a short meeting.

Who owns what

  • Engineering lead: owns the inventory, upgrades and fixes.
  • Application security: runs scanning, sets severity and patch targets, and handles exploited flaws.
  • Legal or open-source office: approves licences and keeps the licence policy.
  • QA and test lead: proves that upgrades do not break payment flows.
  • CISO: signs off on exceptions and reports the risk to leadership.

A quick checklist

  • Every application has a current SBOM, created automatically in the build.
  • No component in production is past end of life, or each one has an approved exception with an end date.
  • Critical and high flaws are fixed within your stated targets, and you can show the numbers.
  • A licence policy exists, and the build blocks licences that are not allowed.
  • New packages are checked for provenance and for look-alike names before first use.
  • Upcoming end-of-life dates are in the release plan at least one quarter ahead.

My take

Open source is not the risk. Not knowing what you run is. Firms that build the SBOM and the end-of-life calendar into their normal release process find that compliance costs very little, while firms that treat it as a yearly audit task spend weeks catching up. Track the dates on our Open-Source Software Compliance Tracker and plan upgrades a quarter ahead.

This guide is a planning summary, not legal advice. Check the official source before acting.

Working on a payments project?

I help banks and fintechs deliver real-time payments, ISO 20022, and AI-driven AML and compliance change, from strategy to go-live.

Connect on LinkedInSee how I can help