Comparison Overview

Mambu Payments (formerly Numeral)

VS

Atlassian

Mambu Payments (formerly Numeral)

Paris, FR
Last Update: 2026-04-02
Between 750 and 799

Numeral, now Mambu Payments, is a payment technology provider for fintechs and banks. We offer financial institutions a universal gateway to connect to partner banks and access schemes and a modern payments hub to automate payment processing. With Numeral, fintechs and banks can unlock growth by launching new products and expanding geographically faster, eliminating hidden payment complexity and making their payments future-proof and ever-compliant. Launched in 2021 and acquired by Mambu (www.mambu.com) in 2024, Numeral provides the payment infrastructure for the most innovative European banks and fintechs like WorldFirst, Argentex and Alma and partners with Europe’s leading banks, including BNP Paribas, Barclays, BPCE, HSBC and LHV. Since May 2025, Numeral is Mambu Payments: a composable, end-to-end payments offering built directly into Mambu’s core banking platform. As part of this chapter, we said goodbye to numeral.io and our beloved blue colours on August 26. You can find us at our new home at mambu.com, under Mambu Payments. The same goes for this LinkedIn account: from now on, you’ll find all Mambu Payments content on Mambu’s LinkedIn page.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 37
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Atlassian

Level 6/341 George St, Sydney, NSW, AU, 2000
Last Update: 2026-04-02
Between 700 and 749

Atlassian powers the collaboration that helps teams accomplish what would otherwise be impossible alone. From space missions and motor racing to bugs in code and IT requests, no task is too large or too small with the right team, the right tools, and the right practices. Over 300,000 global companies and 80% of the Fortune 500 rely on Atlassian’s software, like Jira, Confluence, Loom, and Trello, to help their teams work better together and deliver quality results on time. With our 300,000+ customers and team of 10,000+ Atlassians, we are building the next generation of team collaboration and productivity software. We believe the power of teams has the potential to change the world — one that is more open, authentic, and inclusive.

NAICS: 5112
NAICS Definition: Software Publishers
Employees: 21,511
Subsidiaries: 1
12-month incidents
2
Known data breaches
0
Attack type number
3

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/joinnumeral.jpeg
Mambu Payments (formerly Numeral)
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/atlassian.jpeg
Atlassian
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
Mambu Payments (formerly Numeral)
100%
Compliance Rate
0/4 Standards Verified
Atlassian
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Software Development Industry Average (This Year)

No incidents recorded for Mambu Payments (formerly Numeral) in 2026.

Incidents vs Software Development Industry Average (This Year)

Atlassian has 69.49% more incidents than the average of same-industry companies with at least one recorded incident.

Incident History — Mambu Payments (formerly Numeral) (X = Date, Y = Severity)

Mambu Payments (formerly Numeral) cyber incidents detection timeline including parent company and subsidiaries

Incident History — Atlassian (X = Date, Y = Severity)

Atlassian cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/joinnumeral.jpeg
Mambu Payments (formerly Numeral)
Incidents

No Incident

https://images.rankiteo.com/companyimages/atlassian.jpeg
Atlassian
Incidents

Date Detected: 3/2026
Type:Vulnerability
Attack Vector: Malicious JavaScript injection via Icon URL field in custom priority settings
Blog: Blog

Date Detected: 1/2026
Type:Vulnerability
Attack Vector: Authenticated access with elevated privileges
Blog: Blog

Date Detected: 12/2025
Type:Cyber Attack
Attack Vector: Voice Phishing (Vishing), Phishing Kits, MFA Bypass (Push Notifications, OTPs)
Motivation: Data Theft, Financial Gain, Credential Harvesting
Blog: Blog

FAQ

Mambu Payments (formerly Numeral) company demonstrates a stronger AI Cybersecurity Score compared to Atlassian company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Atlassian company has historically faced a number of disclosed cyber incidents, whereas Mambu Payments (formerly Numeral) company has not reported any.

In the current year, Atlassian company has reported more cyber incidents than Mambu Payments (formerly Numeral) company.

Neither Atlassian company nor Mambu Payments (formerly Numeral) company has reported experiencing a ransomware attack publicly.

Neither Atlassian company nor Mambu Payments (formerly Numeral) company has reported experiencing a data breach publicly.

Atlassian company has reported targeted cyberattacks, while Mambu Payments (formerly Numeral) company has not reported such incidents publicly.

Atlassian company has disclosed at least one vulnerability, while Mambu Payments (formerly Numeral) company has not reported such incidents publicly.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds any compliance certifications.

Neither company holds any compliance certifications.

Both Atlassian company and Mambu Payments (formerly Numeral) company have a similar number of subsidiaries worldwide.

Atlassian company employs more people globally than Mambu Payments (formerly Numeral) company, reflecting its scale as a Software Development.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds SOC 2 Type 1 certification.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds SOC 2 Type 2 certification.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds ISO 27001 certification.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds PCI DSS certification.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds HIPAA certification.

Neither Mambu Payments (formerly Numeral) nor Atlassian holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

nimiq/core-rs-albatross is a Rust implementation of the Nimiq Proof-of-Stake protocol based on the Albatross consensus algorithm. Prior to version 1.3.0, two peer-facing consensus request handlers assume that the history index is always available and call blockchain.history_store.history_index().unwrap() directly. That assumption is false by construction. HistoryStoreProxy::history_index() explicitly returns None for the valid HistoryStoreProxy::WithoutIndex state. when a full node is syncing or otherwise running without the history index, a remote peer can send RequestTransactionsProof or RequestTransactionReceiptsByAddress and trigger an Option::unwrap() panic on the request path. This issue has been patched in version 1.3.0.

Risk Information
cvss3
Base: 5.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Description

PraisonAI is a multi-agent teams system. Prior to version 1.5.95, FileTools.download_file() in praisonaiagents validates the destination path but performs no validation on the url parameter, passing it directly to httpx.stream() with follow_redirects=True. An attacker who controls the URL can reach any host accessible from the server including cloud metadata services and internal network services. This issue has been patched in version 1.5.95.

Risk Information
cvss3
Base: 8.6
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, OAuthManager.validate_token() returns True for any token not found in its internal store, which is empty by default. Any HTTP request to the MCP server with an arbitrary Bearer token is treated as authenticated, granting full access to all registered tools and agent capabilities. This issue has been patched in version 4.5.97.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.97, the PraisonAI Gateway server accepts WebSocket connections at /ws and serves agent topology at /info with no authentication. Any network client can connect, enumerate registered agents, and send arbitrary messages to agents and their tool sets. This issue has been patched in version 4.5.97.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

PraisonAI is a multi-agent teams system. Prior to version 4.5.90, MCPToolIndex.search_tools() compiles a caller-supplied string directly as a Python regular expression with no validation, sanitization, or timeout. A crafted regex causes catastrophic backtracking in the re engine, blocking the Python thread for hundreds of seconds and causing a complete service outage. This issue has been patched in version 4.5.90.

Risk Information
cvss3
Base: 6.5
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H