SOCLYDE logo
Current languageEN
Cybersecurity newsCybersecurityrevolve

Revolve reports exposure of saved payment cards

Some Revolve customers’ saved payment details may have been obtained. Review statements and contact your card issuer through a known channel.

Published on

By Soclyde Team

Unwrapped clothing beside a face-down payment card and phone

In summary

  • Some customers’ saved payment details may have been obtained.
  • State notification counts are not a worldwide total.
  • Review transactions and ask your card issuer about the affected card.

Explore next

Soclyde resources

Article contents

On October 29, 2026, Revolve disclosed unauthorized access to certain systems in a Form 8-K. Some customers’ saved payment information may have been obtained. Shoppers should identify the card stored in their account and review any notice sent to them.

What the official filing establishes

Revolve says it activated incident response, remediated the unauthorized activity and engaged outside security specialists. It also notified federal law enforcement. The filing reports no service interruption and describes an ongoing assessment of the incident’s consequences.

Saved payment details and an uncertain scope

The document describes possible automated collection of names, contact information, payment card numbers and expiration dates for certain customers. It does not identify the intrusion mechanism. A checkout skimmer or stolen shopper password should therefore not be presented as the confirmed cause.

The Record compared notifications in several states. SecurityWeek later examined notification letters covering additional jurisdictions. Their reporting adds detail to the known scope, but does not establish a final global count. Adding regional figures without checking overlap would create false precision.

What customers can check

Open Revolve’s website directly and identify the payment card that was saved in your account. Review recent transactions and contact the issuer through its app or your usual telephone number if something looks wrong. Ask whether a replacement card is appropriate for your circumstances.

A message using your name and purchase details may seem credible after a breach. Verify unexpected requests for payment, banking codes or account confirmation through a separate channel. Changing only the shopping password does not invalidate a copied card number.

For teams managing company purchases

If a company card was stored at Revolve, give a spending administrator responsibility for reviewing transactions and recording disputed charges. Check who receives account notices: an address belonging to a former employee can delay the response. The public disclosure does not justify extending the incident to every online retailer.

How Soclyde relates

Soclyde stores professional credentials in an encrypted vault on devices and supports sharing team access. It can help a business find its shopping account and responsible owner. Blocking or replacing a card remains an action for the bank; Soclyde cannot retrieve data already copied from a retailer.

What to remember

Revolve’s disclosure concerns saved payment information, with scope documented across several filings. Review transactions and the instructions sent to your account. The secure password generator guide explains how to give each shopping account a separate password.

Frequently asked questions

Which information does Revolve describe?

Its filing lists names, contact information, card numbers and expiration dates for certain customers who saved payment information.

Will changing my Revolve password resolve this?

A unique password helps protect the account, but changing it does not replace reviewing payments or working with the card issuer.

Does this affect every customer?

The documents concern certain customers who saved payment details. They do not establish that all shoppers were affected.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading