Resolve Reports Card Data Theft and Customer Exposure After Hack

Key points

• Resolve disclosed a recent security incident involving unauthorized access.
• Hackers obtained payment card data and exposed customer information.
• The total number of affected customers or cards is not yet known.
• Organizations using Resolve should review exposure and card-processing controls.

Resolve has disclosed a recent security incident after hackers compromised payment card data and exposed customer information. The company has not stated how many cards or customers are affected. The disclosure confirms both card-data theft and broader customer-data exposure.

Because payment cards are involved, affected individuals face potential fraudulent charges and identity-related risk. Organizations that rely on Resolve should treat the event as a vendor incident and determine whether their own customers' card data or account details were within scope.

The limited scale information makes risk assessment difficult. No CVE or technical root cause was provided, so defenders cannot rely on a patch reference. The priority is to validate Resolve's notification details, preserve logs, and monitor for card-testing or fraud activity.

Public-sector and K-12 entities often depend on third-party payment vendors, which means a single vendor incident can reach multiple districts and programs. Even without confirmed local impact, teams should review data-sharing agreements and confirm who is responsible for customer notices.

Watch for updated counts, affected card ranges, and any revised disclosure from Resolve. Reconcile vendor payment flows, confirm contractual notification obligations, and prepare customer communications if your data is implicated.

What to do now

1. Contact Resolve to confirm whether your organization or its customers are in scope and request written incident details.
2. Map all payment flows and integrations that use Resolve, including which cardholder data or customer records were shared.
3. Review card-processing logs and monitor for unusual authorization attempts, card-testing activity, or chargeback spikes.
4. Preserve relevant logs, emails, and configuration records, and restrict access to evidence.
5. Notify privacy, legal, and leadership teams; assess contractual and regulatory notification duties.
6. Rotate credentials and API keys used with Resolve, and enforce MFA and least privilege.
7. Prepare customer guidance and fraud monitoring if exposure is confirmed.

Original source

The Record