Blog/Engineering
Engineering

Gnosis Pay Breach: Legacy Crypto Card Data Exposed, Funds Unaffected — User and Fintech Protection Checklist

i
iFynx StudioNov 7, 2026 · 8 min read
An Adyen payment terminal, an illustrative card-payment photograph, not the affected Gnosis Pay system

Direct answer: Gnosis Pay confirms a breach of its legacy consumer-card system, detected on 3 November 2026 and disclosed on 6 November. It says funds were not affected and its separate enterprise platform was untouched. Potentially exposed customers should read their own account-specific notice and use the official app directly, not links in unexpected support messages.

Verified 7 November 2026. This report distinguishes the company’s public disclosure from field-level information reported from customer notifications. No stolen card numbers or screenshots containing actual card data are reproduced.

Key facts

  • Affected scope: the legacy B2C system behind Gnosis Pay-branded cards, according to the company.
  • Containment began within two hours of detection; the notice does not say the full investigation finished in two hours.
  • The company says credentials were replaced and the vulnerability addressed; it has not published a technical root-cause explanation in this notice.
  • Mandatory 3D Secure for online card payments is to remain until the legacy system retires on 20 December 2026.
  • No affected-customer count is established by the public company blog.
An Adyen payment terminal, an illustrative card-payment photograph, not the affected Gnosis Pay system
Illustrative card-payment terminal; no claim this device or Adyen was involved. Photo: Alper Çuğun via Wikimedia Commons.jpg), CC BY 2.0, resized with a dark border.

What was exposed: separate the source and the scope

The official post says “certain customer information” was exposed and that every affected customer was emailed with exactly what was taken from their account. It does not enumerate a universal set of fields. Cointelegraph reports that notifications it reviewed listed full payment card numbers (PANs), expiry dates, CVV codes, names, home addresses, linked wallet addresses, email addresses, phone numbers and nationalities; IBAN and BIC details appeared in some cases. That is attributed reporting about customer notices, not a claim that every customer lost every field.

This distinction is useful for action. A card identifier can require issuer-side containment, while an address or wallet linkage can support targeted impersonation after a card is replaced. A real purchase quoted in a phone call is not proof the caller is support. A real home address is not proof that a threat is genuine either: preserve the message, avoid engagement, and seek appropriate help if there is a credible immediate safety concern.

Company timeline and limits

Date or intervalVerified company statementWhat not to infer
3 November 2026Monitoring detected unauthorized access.No exact intrusion-start time was provided.
Within two hours of detectionContainment began.Not proof all remediation was completed within two hours.
6 November disclosureAffected customers emailed; credentials replaced, vulnerability addressed; mandatory online 3DS announced.No precise 3DS activation time or universal data-field inventory published.
20 December 2026Previously scheduled retirement of the legacy B2C system.Not evidence that all enterprise programmes are being retired.

Source for the timeline: Gnosis Pay’s public disclosure. The retirement was already planned; the notice does not describe it as an emergency shutdown newly scheduled because of the breach. The company says it reported to partners and is communicating with applicable data protection authorities and its card issuer. That does not establish a specific legal reporting deadline for a Gulf or Egyptian business.

User checklist for Gulf and Egypt cardholders

  • Open the official Gnosis Pay web app or your known Partner App yourself. Check whether your own account was affected and which fields are listed; absence of a social-media mention is not a clean bill of health.
  • If a card is active and your notice identifies card-data exposure, use the official app and verified issuer support to ask about freezing, cancellation and replacement. Do not assume one customer’s canceled card means everyone’s card is blocked.
  • Review recent transactions and enabled notifications. Report an unrecognized charge through the issuer’s established dispute process and preserve its reference number, without assuming reimbursement is automatic.
  • For freelancers receiving international payments, distinguish your wallet address, card number and bank details. Replacing a card does not change a public wallet address or erase previously exposed contact information.
  • Warn family members and colleagues about Arabic WhatsApp or Telegram impersonation that quotes a real address or purchase. Independently call back through a known support route instead of continuing an inbound call.
  • Never provide a seed phrase, private key, PIN or full card number in a support reply. Never move funds because a caller, letter or email says a “secure account” is required.
  • Keep a private incident record with dates, redacted notices and transaction references. Do not repost the original notification with card details, address or identity data into a public group.

3D Secure adds a verification layer to online card payments; it does not undo disclosure, remove exposed addresses, or guarantee that every fraud attempt will fail. Be alert to fake authentication pages and requests to reveal an OTP. We are not asserting the card is available, licensed or suitable in every Gulf country or Egypt; those are separate product and jurisdiction checks.

White-label card builders: prove the boundary, do not merely name it

The company’s enterprise-unaffected statement is specific to this incident. A regional fintech should still be able to demonstrate which databases, support consoles, credentials and vendor accounts are shared between consumer and enterprise programmes. Calling a service “legacy” is not a security control: its live personal data, access rights and retirement path still need owners.

  • Map data flows from onboarding to processor, issuer, card-management dashboard and customer support. Record why each field is stored and which system can display it; do not copy sensitive authentication data into analytics or ordinary support logs.
  • Validate separation between B2C and white-label environments with evidence: access controls, credential boundaries, change history and vendor attestations. Do not infer isolation merely from a brand or billing account.
  • Test the incident experience in Arabic and English: the notice should identify affected fields, card status, safe next steps and a timestamp without embedding full card data in an email.
  • Plan retirement as a controlled migration with retention/deletion decisions, credential revocation and residual support access reviewed. A scheduled end date is not permission to reduce monitoring before closure.
  • Confirm 3DS enforcement and exception handling with the issuer and processor, and test legitimate customer journeys without disabling controls to improve conversion.
  • Have security, privacy and legal owners review actual contractual and jurisdictional reporting duties. This article does not invent a VARA, CBUAE, SAMA or Egyptian notification deadline.

Frequently asked questions

Was Gnosis Pay hacked?

The company confirms unauthorized access to the legacy system behind Gnosis Pay-branded consumer cards on 3 November 2026. Its public disclosure is dated 6 November.

Were customer funds stolen?

Gnosis Pay says funds were not affected. Data exposure and unauthorized movement of money are distinct incidents; this statement does not make exposed personal information harmless.

Were PANs, CVVs and addresses exposed?

Cointelegraph says notifications it reviewed listed full card numbers, expiry dates, CVVs, home addresses and other fields. The company’s public blog does not publish that field-by-field list; it says affected customers received account-specific emails.

Is the enterprise or white-label platform affected?

Gnosis Pay says its enterprise platform powering all white-label programmes was not affected. Do not extend that assurance to an unrelated provider or assume all crypto cards share the same infrastructure.

When does the old system retire, and when did 3DS become mandatory?

The company says retirement was already planned for 20 December 2026. Its 6 November notice says 3D Secure has been made mandatory for all online card payments until retirement; it does not give a precise activation timestamp.

Was every card canceled, and can I order a replacement?

A notification reviewed by Cointelegraph said one customer’s card was canceled on 3 November. That is not proof all cards were canceled. Check your own official app and notice for status and replacement options; do not use a link from an unsolicited message.

Should I move my crypto or share my recovery phrase with support?

The company says it will never request a seed phrase, private keys, PIN or full card number, and will never ask you to move funds by email, text or phone. Any account change must happen inside the official app.

Sources and next updates

We will update field-level scope, remediation and any affected-user count only with attributable evidence. Comparisons with other card or wallet incidents are not proof of a shared vulnerability or attacker.

Related reading