[RC_ITR]

Or as is even more often the case with HN:

In practice, “Date of Birth mandatory” is a merchant controlled setting in Klarna [0]. I’ve used Klarna for card countless times and never hit a site that requires it. I’m guessing GP saw it once and never bothered to update his dataset (a surprisingly coming problem among us intellectuals)

[0] https://www.klarna.com/assets/sites/6/2021/09/20095942/user_...

[buro9]

Nice.

So I've followed up and called one of the retailers to ask why it's mandatory and got "We use Klarna and Klarna requires it, but you can enter a fake one and still get through as it's not verified.". This is awd-it.co.uk which was one of the two merchants in which I encountered it.

I suspect they're wrong though, and that you are right. Klarna didn't require this, but someone at this company configured it. Perhaps it's something about PC components for gaming computers, some kind of data gathering that helps protect against kids using their parents card.

There wasn't a way that I could configure not to give it though... I'm just a customer. Whilst I could use a fake date I'm more likely to treat this as a "your data is about to go to another third party" red flag and shop elsewhere still.

[morganvachon]

Thanks for the info. I wonder if, now or at some point in the past, Klarna had mandatory customer DOB as opt-out rather than opt-in for a default card processing setup on the merchant facing side, and many small businesses in my experience either don't have IT staff or it's their cousin's wife's uncle doing IT for them on the cheap, and they just don't see it or understand its significance.

I know there were dozens of switches to flip when we switched to a new storefront and shopping cart vendor a few years ago, and I missed a few initially despite my experience with setting those up in the past. That's what sandboxing is designed to catch, but I can picture PHBs in every industry saying "damn the testing, full speed ahead!" with no thought for consequences.