Fraud Prevention

While classical security with its best practices can be considered a science – fraud prevention is a kind of art. It is not generally possible to build a system which is 100% protected from frauds and cheats – but at least we can try, even when it requires us to cross the line and go into realm of the security-by-obscurity.

Payment Processing. Credit Cards. Chargebacks and Collateral Damage

December 20, 2016 by • “No Bugs” Bunny

Quote:

Chargeback monster will come from under the bed and will eat all your hard-earned money!

Another Quote:

it is trivial to develop a system with guaranteed zero chargeback rate – to achieve this, it is sufficient to decline each and every transaction at pre-filter stage

Filed under: Book: D&D of MOGs 1st beta of Vol. IV-VI 1st beta of Vol. VII-IX On.Security Fraud Prevention

Tagged With: Payments Database Server

War on Clones, Part I. IP-based (non-)Identification. Identifying PCs and Macs

July 11, 2016 by • “No Bugs” Bunny

Quote:

NEVER EVER use IPv4 for long-term bans

Another Quote:

If using MAC addresses to identify devices, you SHOULD gather stats on repeating MAC addresses within your DB

Filed under: Book: D&D of MOGs 1st beta of Vol. IV-VI 1st beta of Vol. VII-IX On.Programming Tips and Tricks Network Programming On.Security Fraud Prevention

Tagged With: multiplayer Spectacular Failure Client

MMOG. RTT, Input Lag, and How to Mitigate Them

January 25, 2016 by • “No Bugs” Bunny

Quote:

For fast-paced games, there is one big problem with the flow shown on this diagram, and the name of the problem is “latency” (a.k.a. 'input lag')

Another Quote:

No, better bandwidth doesn't necessarily mean better latency

Filed under: Book: D&D of MOGs 1st beta of Vol. I-III 1st beta of Vol. VII-IX On.System Architecture Distributed systems On.Programming Network Programming On.Security Fraud Prevention

Tagged With: Latency multiplayer Server Client Protocol

← prev 1 2 3 4 5 next →