Cleverbridge says a third party copied card data; its page names no fields, a news report says the CVV was included
Cleverbridge's incident page, as saved on 22 November 2026, says a third party copied payment card data stored on its platform and that notices began 16 days after detection (derived). The page names no card field; a news report of a notice it was shown says the card security code was among them.
By Parminder Kumar Sharma · LinkedIn · · 17 min read
16 days from detection to the first notices, and a page that names no card field (derived)
Cleverbridge's Incident Update and FAQs page, which this site saved at about 16:05 UTC on 22 November 2026, says that on 4 November 2026 Cleverbridge detected unauthorised activity in its platform and that all systems were brought back online on 4 November 2026. It then says "our investigation subsequently determined that a third party copied payment card data stored on our platform" and that it began notifying affected individuals on 20 November. From 4 November to 20 November is 16 days (derived: 20 minus 4). From 4 November to the news report of 22 November is 18 days (derived: 22 minus 4). The saved page carries no date of its own: this site found no date line, no date field and no time stamp in it, only the two days named in its text (4 November 2026, and 20 November with no year printed).
The second angle: the card security code. The page does not say which card fields were copied. BleepingComputer's article, stamped 22 November 2026 at 10:43 AM as printed (15:43 UTC, from the page's own data), says a notice shown to it lists "your card number, expiry date, card security code (CVV/CVC)" and says "no other personal data" was copied. That notice is not public and this site has not seen it. The PCI Security Standards Council's FAQ, a blog post of 2 November 2017, says card verification codes must not be stored after authorisation, whatever the encryption or the customer's permission. This brief reports each page and stops where the pages stop.
What this does not establish. The saved pages do not say whether the platform held security codes after authorisation or only during transactions in flight, why a code would be present, whether the reported fields are the same for every affected cardholder, or whether Cleverbridge or any seller was assessed against the rule. They do not name a single seller whose customers are affected, a cardholder count, a country, a card brand, the period of the copying, how the attacker got in, who the attacker is, or whether the data was encrypted, used or sold. This site alleges no breach of the PCI standard: it states the rule, states that the reported fields would be of the kind the rule covers if the notice is accurate, and stops.
Whose interest. Cleverbridge describes itself as a global ecommerce provider that helps businesses manage online purchases, payments, and subscriptions, so it sells that service to businesses and has an interest in how this incident is read. BleepingComputer is a news publisher; its saved page carries a promotional block for an email security scan, which has no part in this story. The PCI Security Standards Council describes itself as a global forum for payments industry stakeholders that develops data security standards. The page names TransUnion/Cyberscout as a vendor Cleverbridge engaged for notifications. No vendor pays this site, and it shares no vendor's interest.
What the incident page says, in its order, and what it leaves open
Diagram 1 draws the dates the page prints on a time axis from 1 to 26 November 2026, to scale, with the spans in days. The table gives the page's own words for each statement and what the statement leaves open. The opening paragraph and the first FAQ answer between them give the sequence.
The incident page, statement by statement (page saved about 16:05 UTC on 22 November 2026; quotations are the page's own)
| Statement | As the page words it | What it leaves open |
|---|---|---|
| Detection | "On 4 November 2026, Cleverbridge detected unauthorised activity in our platform" | The time of day, how it was detected, and what the activity was. |
| Containment | "affected systems were temporarily taken offline"; "All systems were brought back online on 4 November 2026" | Which systems, and for how long. |
| The finding | "our investigation subsequently determined that a third party copied payment card data stored on our platform" | The day of the finding, and the period of the copying. |
| Not ransomware | "No. None of our systems were encrypted." | Whether any data was encrypted at rest or in transit. |
| Notices | "began notifying affected individuals on 20 November where appropriate" | Who is outside "where appropriate", and how many were notified. |
| Status | "Whilst our investigation remains ongoing" | An end date, and what further findings may follow. |
The gap between 4 and 20 November. The page answers the question why individuals were not notified sooner by saying that, once it learned there may have been unauthorised access, it acted quickly, identified the individuals whose personal information may have been involved and notified them "without undue delay". It does not say when the investigation determined that card data was copied, so the 16 days cannot be split between investigating and notifying. This site draws no conclusion about whether 16 days is long or short: the page prints no standard to measure it against, and this site read no regulator's page.
Whose purchases. The page says that if you purchased a product or service from one of the businesses supported by Cleverbridge, Cleverbridge may have processed or managed that transaction, and that it holds the information because it was used in connection with such a purchase. It names no business. That matters for the reader: a cardholder may not know that a seller used Cleverbridge (this site's inference), and the page gives no list to check.
One answer states the copying, another says the data may include card details
The page is confident in one place and hedged in another, and this site quotes both without choosing between them. In the answer to What happened, the page says "a third party copied payment card data stored on our platform": that is stated. In the answer to What data was affected, it says that, based on its investigation to date, the information involved "may include payment card details used to make a purchase through Cleverbridge": that is hedged. The opening paragraph speaks of "individuals whose personal information may have been involved". The page uses "payment card data" in one answer and "payment card details" in another, and does not say whether it means the same set of items. Both statements were read in the copy saved at about 16:05 UTC on 22 November 2026.
The ten FAQ questions on the incident page and what each answer does (page saved about 16:05 UTC on 22 November 2026; count derived)
| Question | What the answer does | Sends the reader to the notification |
|---|---|---|
| What happened? | Gives the sequence and states that a third party copied payment card data stored on the platform. | No |
| Who/what is Cleverbridge? | Describes the company and says it "may have processed or managed that transaction". | No |
| What data was affected? | Says the information involved "may include payment card details" and sends the reader to the notification. | Yes |
| Was this a ransomware attack? | "No. None of our systems were encrypted." | No |
| Why does Cleverbridge have my data? | Says it was used in connection with a purchase or transaction with one of the businesses it supports. | No |
| What should I do to protect myself if I was affected? | Gives the advice set out below. | No |
| Who is TransUnion/Cyberscout? | A vendor engaged to support notifications; a notification from it is legitimate and the reader is encouraged to review it for more information. | Yes |
| Will there be identity and credit monitoring services? | Offered to affected cardholders "where available"; take up is explained in the notification. | Yes |
| Why weren't affected individuals notified sooner? | Says it acted quickly and notified "without undue delay". | No |
| Who can I contact for more information? | Sends the reader to the notification for details of the support available. | Yes |
Four of ten. The page has 10 FAQ questions (derived by counting the question headings). Four answers send the reader to the notification for the substance of what they asked: what data was affected, who TransUnion/Cyberscout is, how to take up the monitoring offer and who to contact (derived). Three of them use the same words, "refer to the notification we sent them", and the fourth says to review it for more information. The data question is among the four, so the page's answer on data is a hedge plus a pointer. The text of the contact answer names no email address, telephone number or form. The notification itself is not public; this site could not read it.
What BleepingComputer reports from a notice it was shown, and where it differs from the page
BleepingComputer's article says that a breach notification shared with it reveals that the information includes payment card numbers, expiration dates and CVV/CVC security codes, and it quotes the notice. It adds that the notice says no other personal data was copied, and that the affected card ends in four digits, which BleepingComputer redacted. This site reads that last line as suggesting a notice is written per card (inference); no page says how many notices one person may receive.
Where BleepingComputer's article and the incident page differ or add (both saved on 22 November 2026; quotations are the pages' own)
| Topic | The incident page | BleepingComputer |
|---|---|---|
| Card fields | Does not name them: "may include payment card details" | A notice shown to it lists notably your card number, expiry date, card security code (CVV/CVC) |
| Other personal data | Not addressed in the FAQ answer on data | The notice says no other personal data (for example your name, contact or billing details) were copied |
| Confidence word | "may include" | The notice, as quoted, says the information involved "includes" the payment card details |
| Who was told | No such statement on the saved page | Says the company has notified data protection authorities, law enforcement, payment card networks, and payment partners, without saying where the company said so |
| Monitoring | "credit or identity monitoring services where available" | "complimentary credit monitoring and fraud assistance" |
| Wording of the act | "a third party copied payment card data" | Headline and text say hackers stole card numbers and codes |
| Who was notified | "affected individuals" | "affected customers" |
| Questions put to the company | Not applicable | On count, access, encryption and why the codes were accessible; the company has not responded to our questions. |
Where the sources differ. The page's "may include" and the notice's "includes" are two levels of confidence about the information involved. They may come from different texts written at different times; this site cannot tell, because it has only the page and a relay of the notice. The article's list of who was notified is attributed to the company, and the saved incident page carries no such statement: the pages do not say where the company said it. BleepingComputer's words "hackers" and "stole" are its own; the page says a third party copied the data. This site follows the page's verb.
Customers. BleepingComputer says the company lists numerous technology brands as customers and has not disclosed which businesses' customers were affected. This site does not repeat the brand names: neither saved page says any of them is affected, and a customer list is not an affected list.
The security code: what the PCI council's 2017 FAQ says, and what it cannot tell us
The PCI Security Standards Council FAQ is a blog post dated 2 November 2017 on FAQ article 1280, 9 years and 20 days (3,307 days, derived) before this site read it on 22 November 2026 at about 16:07 UTC. It cites Requirement 3.2 of PCI DSS, the version current in 2017. This site has not checked the number or the wording in the version current now, and the FAQ says nothing about Cleverbridge. What it says, in brief:
- A card verification code, which the FAQ also calls CAV2, CVC2, CVV2 or CID depending on the payment brand, is the 3 or 4 digit number printed on a payment card.
- Such values are sensitive authentication data. Under Requirement 3.2 they "must not be stored after authorization".
- They are typically used for authorisation in card not present transactions, and the FAQ says they are not needed for card on file or recurring transactions, where storing them is prohibited.
- The standard "does not prohibit the collection of card verification codes/values prior to authorization" of a specific transaction; what is not allowed is keeping the code once that transaction is authorised.
- The FAQ addresses providers that retain cardholder details for potential future transactions: keeping the code for that purpose is also prohibited.
- The requirement "cannot be met by the use of cryptographic techniques", and a customer's request or approval "has no validity for PCI DSS".
- A footnote says only issuers or those providing issuing services may have a legitimate business need to store the data after authorisation.
What this establishes. If the notice BleepingComputer quotes is accurate, the fields it lists include a value of the kind the FAQ says must not be stored after authorisation. This site reads the notice's "CVV/CVC" as that kind of value because the FAQ lists CVC2 and CVV2 among the names (inference). That is a statement about a rule and about a report.
What it does not establish. The saved pages do not say whether the platform held any security code after authorisation or only for transactions in flight. They do not say why a code would be present. They do not say whether the reported fields are the same for every affected cardholder, since the one notice quoted refers to one affected card. They do not say whether Cleverbridge or any of its customers was assessed against the rule, by whom, or with what result. BleepingComputer says it asked the company how many customers were affected, how the attackers got in, whether the data was encrypted and why the codes were accessible; it says the company had not responded when the article was published. This site has no reply from Cleverbridge and did not ask.
What the pages state, and what they do not
Stated or reported, against not stated (pages saved on 22 November 2026; the notice itself is not public and not saved)
| Question | What the saved pages state or report | What they leave open |
|---|---|---|
| What happened | Unauthorised activity detected 4 November 2026; systems back online the same day; a third party copied payment card data stored on the platform; not ransomware. | How the attacker got in, who it was, how long access lasted, whether the data was encrypted. |
| Who is affected | Individuals who bought from businesses supported by Cleverbridge and whose information may have been involved. | Which sellers, how many cardholders, which countries and card brands. |
| Which data | Page: may include payment card details. Relay of a notice: card number, expiry date, card security code, and no other personal data. | A field list on the company's own page, and whether every cardholder has the same fields. |
| The security code | The PCI council's 2017 FAQ: codes must not be stored after authorisation (Requirement 3.2, the version then current). | Whether any code was held after authorisation, why, and whether anyone was assessed. |
| Timing | Detection and recovery 4 November; notices from 20 November; investigation ongoing. | The day the finding was made, the period of the copying, an end date. |
| Who was told | BleepingComputer says the company notified data protection authorities, law enforcement, card networks and payment partners. | Where the company said so; which authorities and networks; the saved page carries no such statement. |
| After the copying | Check statements, tell the issuer, contact the issuer; monitoring where available. | Whether issuers have reissued cards, and whether the data was used or sold. |
| Technical detail | The page prints no indicators, no software versions and no CVE. | Any of them. |
A line the page does not carry matters as much as one it does. The page names no card field, no seller, no count and no cause. Where it is silent, this brief is silent. Where a relay fills the gap, the relay is attributed and its limits are stated.
What the company advises, in its words
The primary's advice comes first. Per the incident page, saved at about 16:05 UTC on 22 November 2026:
- Check your card statements carefully and tell your card issuer right away about any transaction you do not recognise.
- You may also wish to contact your card issuer about this incident and follow any advice it gives, as it may decide to replace your card.
- Follow general best online security practices, remain vigilant and be aware of phishing attempts; be cautious of unexpected emails, calls or messages about this incident.
- The page says: "Cleverbridge will never ask you for your card details, passwords, or security codes by email, phone, or text message."
- If you received a notification on behalf of Cleverbridge from TransUnion/Cyberscout, the page says it is legitimate and encourages you to review it; monitoring is offered "where available" and the notification explains how to take it up.
The sentence about what the company will never ask for is useful against phishing. It is not a statement about which fields were copied, and this site does not read it as one.
What to do, in order
For a cardholder: the company's advice above is the starting point, in the order the page gives it. The list below is this site's own, for a business that sells through a payments or ecommerce platform or uses payment suppliers. None of it is the page's advice.
Take this with you
This site's suggestions for a business that sells through a payments or ecommerce platform
- Ask your platform in writing whether your customers' cards are in scope of the incident, and which fields it held for them.
- Ask every payment supplier what sensitive authentication data it retains after authorisation and for how long, and ask for the answer in a form you can file.
- Check your own card on file and recurring flows for any retained security code, in databases, logs, backups and support tools.
- Watch for fraud and chargeback spikes on cards used with the affected sellers over the period, and note that the period is not stated.
- Prepare a customer notice route now: who sends it, from which address, with what wording, so a real notice is not mistaken for phishing.
The question the page leaves open
Cleverbridge's page gives 4 November for detection, 20 November for the first notices and no date for the finding in between. A relay of a notice names a security code that the council's own FAQ says must not be kept after authorisation. Both statements sit on pages this site could read; neither is a finding about how the data came to be held. The exposing question for any business that takes cards online is the one the page cannot answer for you: which of your suppliers hold your customers' card data, what would you learn from them if one of them were in the news tomorrow, and how many days would it take?
Key facts
Sources
- PrimaryCleverbridge's incident page, a living page with no date of its own, saved at about 16:05 UTC on 22 November 2026: detection on 4 November 2026, copying of payment card data, notices from 20 November, FAQ answers and adviceCleverbridge (Incident Update and FAQs page)accessed 2026-11-22
- PrimaryPCI SSC blog post of 2 November 2017 on FAQ article 1280, saved at about 16:07 UTC on 22 November 2026: card verification codes and Requirement 3.2 of the version then currentPCI Security Standards Council (blog)accessed 2026-11-22
- Reported byBleepingComputer's article of 22 November 2026 (10:43 AM as printed, 15:43 UTC), saved at about 16:04 UTC: the only source for the card fields, from a notice it says it was shown; the notice is not publicBleepingComputeraccessed 2026-11-22


