Paytaca Users See Fake Orders, Unrequested Payments

Two backend exploits on the self-custody wallet spawned fake trades and payment requests, while private keys on user devices stayed out of reach.

Updated on Nov. 18, 2026 in Cybersecurity

Bold flat-color editorial illustration of a tall unlabeled server cabinet with cables running down a cable tray and a few amber indicator lights, evoking backend infrastructure risk.
Two backend exploits on Paytaca's self-custody Bitcoin Cash wallet on Nov. 17 and Nov. 18 created fake trade orders and unrequested payment requests, though users' private keys stayed on their devices. AI Illustration. Upload story photo >

Paytaca, a self-custody wallet in the Bitcoin Cash (BCH) ecosystem, had two separate vulnerabilities in its backend infrastructure exploited on Nov. 17 and Nov. 18. The Nov. 17 exploit created fake peer-to-peer orders, while the Nov. 18 exploit generated payment requests users had not requested. This is a reported incident affecting shipped, live software, not a research-stage development.

Why it matters

Both attacks targeted Paytaca's backend rather than its users' keys, which illustrates how a wallet can be compromised through server-side infrastructure even when self-custody holds. The incidents underline that self-custody design protects private keys but does not by itself protect the services a wallet relies on for orders and payment requests.

The incidents were reported by Paytaca itself, which described two separate vulnerabilities in its P2P Ramp backend and general backend infrastructure. No measured figures such as affected user counts or losses were provided in the available reporting.

The players

Paytaca

A self-custody wallet in the Bitcoin Cash (BCH) ecosystem that keeps private keys on users' devices and operates a P2P Ramp trading backend.

The details

Paytaca keeps private keys on users' own devices rather than on its backend servers, so the attacks did not directly expose those keys. The exploited flaws sat in server-side components: the P2P Ramp backend, which handles peer-to-peer trading orders, and a separate backend service that generates payment requests. Because the attacker reached these services rather than the keys, the damage took the form of fake orders and unrequested payment requests that users had to decline rather than unauthorized key-based transfers.

Timeline

  1. Nov. 17: P2P Ramp backend vulnerability exploited to create fake peer-to-peer orders

  2. Nov. 18: separate backend vulnerability exploited to generate unrequested payment requests

The Tech Race

The incidents place Paytaca's backend exposure against the self-custody model that many wallet providers promote as their main security advantage. The episode shows that the security boundary in self-custody wallets extends to the server-side services that handle orders and payment requests.

Users of Paytaca should avoid suspicious P2P orders and payment requests, and should not sign any transaction they did not initiate. Because the attacks targeted the backend, users may see unexpected orders or requests even though their keys were not directly exposed.

The takeaway

Self-custody protects private keys, but wallet users should still treat unexpected orders and payment requests as a warning sign. Watch for Paytaca's follow-up disclosures on the number of affected users and whether any funds were lost.

Further reading

For background on how attacks on wallet infrastructure differ from attacks on private keys, see the Cybersecurity section.