Comparison Overview
Barclaycard Payments

Barclaycard Payments
1 Churchill Place, Canary Wharf, London, E14 5HP, GB
Last Update: 25/02/2026
Welcome to Barclaycard Payments. We’re leading global payment experts who can help you transform your business – whatever its size, sector or ambition. Barclaycard Payments combines over 50 years of payment experience with insight and data across the Barclays group. ...

Westpac Group
275 Kent St, Sydney, 2000, AU
Last Update: 05/09/2026
From rescue helicopters to signing the Equator Principles, from paying super during parental leave to adding 'Touch ID' biometric technology to our banking apps and being first on the scene with a helping hand in times of crisis... we have a proud history of stepping u...
Compliance Ranges Comparison

Barclaycard Payments







Westpac Group






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Barclaycard Payments in 2026.
Incidents vs Financial Services Industry Avg (This Year)
Westpac Group has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Barclaycard Payments (X = Date, Y = Severity)
Barclaycard Payments cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Westpac Group (X = Date, Y = Severity)
Westpac Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Barclaycard Payments

Westpac Group
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)