Page 23 of 23 FirstFirst ... 13212223
Results 221 to 228 of 228

Thread: ATF raids polymer 80.

  1. #221
    Four String Fumbler Joe in PNG's Avatar
    Join Date
    Feb 2011
    Location
    Papua New Guinea; formerly Florida
    Then there's the data that Facebook, Google, Youtube, and others get.
    "You win 100% of the fights you avoid. If you're not there when it happens, you don't lose." - William Aprill
    "I've owned a guitar for 31 years and that sure hasn't made me a musician, let alone an expert. It's made me a guy who owns a guitar."- BBI

  2. #222
    Also...

    I think that a belief that there is some kind of regulatory buffer on this kind of information is wildly naive.

    1) Somewhere in the 300 page Patriot Act, I'm sure you can find some exception that makes any data, anywhere fair game.

    2) Any regulation that "protects" the information can be undone. Do you really think that Amazon, VISA, Master Cards, Stamps.com and etc are gonna fight hard to not turn over their records regarding "illegal shoulder things that go up?"

    3) People cheat. Parallel construction is a thing.
    I was into 10mm Auto before it sold out and went mainstream, but these days I'm here for the revolver and epidemiology information.

  3. #223
    Quote Originally Posted by scw2 View Post
    I thought Level 3 data provided some level of granularity on what was being purchased. Not an expert in this area so no idea if my understanding of the data being shared may be wrong, but I would imagine the credit card companies could easily tie you to the purchase if it's provided.
    I don't think so?

    https://www.magtek.com/content/docum.../d99800004.pdf

    I had to look it up. It's been years since I even thought about what was encoded on the mag stripe.

  4. #224
    Quote Originally Posted by Lester Polfus View Post
    And just debit/credit activity in a certain area is a pattern of life, regardless of whether or not you are able to ascertain someone's favorite flavor of Boones farm.
    Indeed. Most people have very consistent routines. That was one of the more interesting bits to come from the iTunes unencrypted backup fiasco a decade ago. Apple was keeping a timestamp and geolocation information of every wireless hotspot your iPhone connected to, IIRC. Which made it easy to map out peoples' daily routines. You can generate similar insights from financial data, cell phone tower hits, etc.

    Also, it's common practice for any online vendor to email you a copy of your invoice that lists exactly what you bought.
    Yeah, online vendors are inescapable. If you bought it online then every marketing company on planet Earth will know about it before UPS does.

    But in person transactions aren't as... thoroughly documented yet.

  5. #225
    Quote Originally Posted by CleverNickname View Post
    I work for a bank you've probably heard of, and the business unit that I work for currently stores card transaction data for 7 years, and it'll be upped to 15 years worth of transactions in a few years.
    Ah. Good to know.

    I believe it's regulatory requirements, but I'm on the IT side of things so I don't care as much about the "why" so much as the "how."
    "how": copy to public s3 bucket. Put up digital "no trespassing" sign. Clock out at 5pm and go to happy hour.

    ...I kid. Mostly.

  6. #226
    Site Supporter
    Join Date
    Aug 2014
    Location
    Northern Virginia
    Quote Originally Posted by CleverNickname View Post
    I work for a bank you've probably heard of, and the business unit that I work for currently stores card transaction data for 7 years, and it'll be upped to 15 years worth of transactions in a few years. I believe it's regulatory requirements, but I'm on the IT side of things so I don't care as much about the "why" so much as the "how."
    Is that in alignment with PCI-DSS (not relevant if you're not storing cardholder data)? PCI-DSS says to keep the data for as short a time period as necessary. 15 years feels excessive and may not be legally justifiable if there was a breach that exposed that data to unauthorized entities.

    Chris

  7. #227
    Quote Originally Posted by jh9 View Post
    I don't think so?

    https://www.magtek.com/content/docum.../d99800004.pdf

    I had to look it up. It's been years since I even thought about what was encoded on the mag stripe.
    Ah, I see where our disconnect was as the Level 3 data is not tied to your mag stripe. It is data sent from the merchant to the card issuer, in exchange for a discount on the fees they pay. The more detailed data corresponds to a higher level (Level 1, 2, 3) and also higher discounts. So the merchant may not have that info, but your bank very well might. Probably more likely if you're dealing with a bigger retailer versus a local mom and pop type store.

  8. #228
    Quote Originally Posted by scw2 View Post
    Ah, I see where our disconnect was as the Level 3 data is not tied to your mag stripe. It is data sent from the merchant to the card issuer, in exchange for a discount on the fees they pay. The more detailed data corresponds to a higher level (Level 1, 2, 3) and also higher discounts. So the merchant may not have that info, but your bank very well might. Probably more likely if you're dealing with a bigger retailer versus a local mom and pop type store.
    Huh. New to me.

    I don't think B2C transactions qualify, but I base that on a quick google and not first hand experience.

    https://www.centurybizsolutions.net/level-3-processing/

    Rando .net URL. Not sure how valid it is. Disclaimer: I have no first hand experience in the B2B or B2C payment world, just P2P. (Where I don't think I ever saw collecting that sort of data... but it also wouldn't make a lot of sense since there are no line items to speak of. Just 2 individuals with at most the equivalent of a "comment" field on a paper check.)

    If the link is (still?) correct then your average merchant PoS won't qualify. I assume that includes SquareCash type setups that are increasingly common amongst your smaller businesses.

User Tag List

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •