How can a marketplace link new accounts to previously banned devices?

Compare available device records for new sign-ups with the sessions associated with banned accounts. A device identifier is not guaranteed to survive cleared storage, changed browsers or deliberate evasion. Treat a match as a reason to review or restrict the account, because shared and second-hand devices exist. Determined attackers change devices or use anti-detect browsers, so combine the device check with payment, address and behaviour.

A device record has two parts. One is an identifier stored in the browser or app, which is exact but disappears when storage is cleared. The other is a set of characteristics collected from the browser and hardware, which may support recognition when storage changes but is not an exact or permanent identity. Each is weak alone. Used together, and compared over several visits, they provide more evidence than either alone, without guaranteeing recognition.

Banned users who want to return know this. They clear storage, open a new browser profile, switch to a virtual machine or a second phone, or use an anti-detect browser that presents a different set of characteristics for each profile. They route traffic through proxies so the network changes too. A marketplace that relies on the device alone will catch the casual returner and miss the organised one.

Marketplaces have other links that are harder to replace. A payout account is another useful comparison: a seller needs a bank account or wallet to be paid, and opening new ones takes effort. Payment cards, phone numbers and identity documents, where you verify sellers, serve the same purpose. Content is a further signal. Returning sellers reuse the same photos, listing text, prices and message templates, and the same behaviour in how they contact buyers.

Build the check into your process. When you ban an account, record every identifier connected to it. Check new accounts against that list at sign-up, and again at the first listing and the first payout request, because attackers often prepare accounts quietly and use them later. Match the response to the strength of the link. A shared payout account merits investigation against your seller policy; legitimate businesses can also share payment arrangements. A device match alone justifies holding listings for review or limiting what the account can do until it has a history.

Leave room for error and for the law. Second-hand phones, family computers and shared workplaces produce innocent matches, so give affected users a route to appeal. Keeping identifiers of banned users is processing of personal data, which needs a lawful basis and a retention period. Agree both with your data protection lead before you build the list.

How Kairal helps

Session linking connects recorded devices, IPs and sessions to the user IDs your integration supplies. Compare those visits with your own account and order records before acting; a device match does not establish that two people are the same person.

Session linking