IPCRIME | November 20, 2026. Japan’s Paydon cashless-payment service has suspended its operations after a breach at payment-infrastructure provider Infcurion. The service operator reports 251,172 records leaked through the provider’s Wallet Station platform, including identifying information, account and password data, wallet balances and transaction records.
The disclosure is unusually consequential because it reaches further than mailing-list contact details. The published categories can reveal both personal identity and purchasing behavior. The provider and Paydon describe this as confirmed data leakage, while saying they have not identified fraudulent use of the exposed information as of their first reports.
What happened and when
Infcurion says it detected a high volume of suspicious access to Wallet Station on the evening of November 19 and confirmed unauthorized access. It blocked communications from the source, applied an emergency vulnerability patch, closed the identified route and suspended affected services. The company says it has not observed further unauthorized access through that route since it was blocked.
Paydon says it was told that its payment platform was affected and shut down all Paydon services at 6:20 a.m. Japan time on November 20. Infcurion is also examining other customers that use its platform; the scope beyond this known affected service is still under investigation.
What the affected records contained
Paydon’s Japanese-language customer notice names 251,172 records. Depending on the entry, categories include the customer’s name, birth date, telephone number, sex, email address and password; linked account and point-balance information; transaction date, merchant and amount; and merchant name and contact details. The announcement does not say that every field was present in every record or that 251,172 is a confirmed count of distinct people.
Infcurion’s broader provider notice describes roughly 250,000 personal records connected to an affected customer platform. Those figures refer to the same disclosed event and should not be added together as if they were separate breaches.
Why the operators say the leak is not equivalent to direct theft of funds
Paydon says its payment operations rely on SMS verification tied to a phone number registered with the bank, so the stolen record categories are not by themselves sufficient to conduct an immediate transaction. That claim should be treated as the operator’s description of its current security model, not a reason to dismiss the risks of phishing, impersonation, SIM-swap attempts or password reuse.
A list containing someone’s recent merchant purchases and point balance can make a social-engineering contact seem convincing. Reused passwords may also expose unrelated services, particularly if a user has not enabled additional authentication there.
What customers can do safely
- Visit Paydon’s official website directly for service status; do not trust an unsolicited message saying the service has reopened or offering an urgent refund.
- Change any reused password on unrelated services from a known-clean device, and enable available multi-factor authentication.
- Watch for suspicious requests for verification codes, linked bank details, refunds or account recovery information.
- Review bank and payment-app activity through established channels; keep receipts of any unauthorized activity.
- Avoid sharing personal account records in public forums or online reports of the incident.
A separate earlier Paydon disclosure
Paydon previously described an email-address exposure involving another supplier in early November. That earlier incident, and the new Infcurion Wallet Station breach, should not be combined without evidence of a common technical cause. The November 20 notice concerns payment-platform records, a wider collection of sensitive fields, and a full service shutdown.
Sources
Paydon — November 20 official customer notice; Infcurion — November 20 updated incident statement; Paydon — earlier separate email-related disclosure.
Research is based on original Japanese-language statements. Attacker identity, technical root cause beyond the reported patched path, and subsequent financial misuse remain unconfirmed.