[lyall]

Yes, the rails used should not affect the consumer protections you do or do not receive. If it's a debit card, it's a debit card regardless of if it's processed over a credit network.

Exactly how long the transaction takes to _clear_ your account may vary depending on the semantics of the network and integration used, but processing a debit card over a credit network doesn't mean you get to hold onto your money for any longer than you would otherwise. The auth will put a hold on the funds in your account instantly and you will effectively have that much less money in your account.

[cobertos]

The terminology makes this so much harder to distinguish. My bank does have different consumer protections for different cards issued through them (debit cards require you to report fraud within 7 days, credit cards require you to report within 30). I didn't realize that the payment network used was not coupled to these mechanisms.

I wonder if financial marketing understands this? Associating credit with less risk, less requirements, in naming of the networks themselves? Even though settlement can occur on each network

[tjrDL6MjB2Zwwa]

There are consumer protection laws in place wrt to your liability based upon discovering fraud. It's something like no liability w/i 48 hours, $50 in liability with 1 week, full liability after that. I may be getting the specifics wrong, but the gist is correct.

It sounds like your bank has made the decision to eat the small liability as a customer value add.

One of the reasons why people are often wrong about CC being safer than debit is because many banks will also make you whole the next day after reporting fraud rather than waiting for it to process before returning the funds. They're not legally required to do this, but neither are credit card companies, both are doing it to gain customers.

[lyall]

The payment processing space, like basically anything when you look close enough, has a fractal-like complexity to it. And in my opinion the industry as a whole does a pretty poor job of abstracting away that complexity, often leaking it through, such as with the "debit or credit?" question.

But turns out it's pretty difficult to hide the complexity, and many businesses are built around hiding it as a service. It usually involves taking on risks others aren't willing to or having an Apple-like resolve to piss off some customers by deciding what's best for them without asking or, rarely, the power and/or innovation to actually change how things are done.

[onphonenow]

False. Charging back a debit transaction can be massively more difficult - the network rules are very different between Amex etc and debit. The minimums are the same but as Zelle folks are finding out - payment rails matter in terms of protection