You'll still get a lot of chargebacks by the way. With a lot of ecomm I've been involved with the fraud you are talking about is actually a small part of chargeback volume. Most is unhappy or demanding customers, or another type of low level fraud, claiming goods didn't arrive despite a photo of the person literally accepting them from the delivery company. This is absolutely rampant in b2c with smaller merchants (I am aware you mentioned this but not sure if you are aware of the scale of it).
This would open the door to cheap or even completely fee-free transactions if the user doesn't want to opt-in to additional protection, which they reasonably may not want when the stakes are low enough (you weren't gonna chargeback a lunch anyway).
But for this to be viable, the risk of unauthorized transactions/origination fraud needs to be eliminated completely at a technical level, something I believe an oAuth-style system would do, and currently none of the many of hacks on top of the legacy system address. Otherwise, you'd still need to take some fees to refund unauthorized transactions, separate of customer-merchant conflicts.
It already works like that here (eu) for debit cards (which most people have; very few have credit cards although they don't know the difference). Double charges from taxi drivers is not possible as it's tapping or dipping your card and you are there for that (we are assuming some system that prevents someone stealing your card like biometrics or whatnot); products not as delivered is responsibility for the seller to refund/replace and in other cases you go through a process of mediation. I had it once in my life, which is now 50 years. It sounds like Americans willy-nilly chargeback whatever because they can (fries were not hot or cold enough): seems not very good for the fees. Most people who travel have creditcards here and the most ones I know have no idea they can chargeback or ever needed it.
You'd be surprised - at least in the public transit context with iOS Express Mode, double Apple Pay taps by transit systems have absolutely been recorded plenty of times. I admit I haven't heard about this in the taxi situation, but unless the technical problem is specific to Express Mode and not general to tap-to-pay, I don't know why it wouldn't ever happen.
> products not as delivered is responsibility for the seller to refund/replace and in other cases you go through a process of mediation.
This assumes the seller is willing to do their job or go through the process of mediation, and/or that the buyer has sufficient legal insurance or available cash to cover the up-front cost of lawyers plus any related expenses plus the possible attorney's fees of the other side if the court decides against them.
Even in the EU, this is far from always true, especially for low-price purchases or when dealing with foreign online merchants who are more likely to ignore EU lawsuits or mediation attempts than to cooperate.
Of course, trying to resolve things with the seller is always the right first step, and that's the usual approach even in the US. It's just great to be able to have the leverage of the chargeback option as extra incentive for the merchant to be reasonable. (By the way - the chargeback right is not unconditional even when the reason claimed is one of the allowed reasons. The merchant can dispute it and can sometimes win depending on the circumstances, the evidence, and the bank.)
> It sounds like Americans willy-nilly chargeback whatever because they can (fries were not hot or cold enough)
To be honest, no, the idea that chargebacks are something Americans rush to do is a stereotype and not true. They're pretty rare when neither the buyer nor the seller is doing something shady, but having the option to charge back is pretty important in order to make US single-factor (no-pin / no app-based verification / no meaningful signature verification) credit cards secure enough for customers to rely on, especially for online purchases from random small merchants who can't be relied upon.
And "fries were not hot or cold enough" would pretty much never be a valid reason for a chargeback, since usually a specific temperature isn't promised before purchase, and probably also since temperature isn't anything inherent to the quality or nature of the product as opposed to a transient characteristic.
> seems not very good for the fees
It definitely affects the fees, but honestly, a bigger impact is that the US does not cap what fees credit card issuers can charge the merchants, so the fees are much higher than the typical EU consumer card regardless of chargebacks. Some of that is of course kept by the banks as profit, but much of it is returned to customers as reward points, cash back, or other perks. It's among the reasons why I continue to use my US credit card as my primary form of payment even here in Germany. Zero foreign transaction or currency conversion fees, great perks. (This card does require a decent US credit history and has an annual transaction fee, but I get enough value out of it to outweigh that fee.)
How many chargebacks have I done in my entire life for a reason other than actual fraudulent / unauthorized transactions? Probably under 5, maybe 1-2 at most. Plus most of the fraudulent transactions were noticed proactively by the bank rather than me having to bring it up to them. Because it's a true credit card and not a debit card, I never had to pay for those fraudulent transactions.
The thing is, even here on HN (where I expect, maybe not warranted, the level to be higher), people seem to absolutely proud and entitled to chargeback whatever for whatever reason. Those are almost 100% Americans (I check) and that is where I got the idea; this sentiment is much higher on tiktok, youtube, reddit etc. I even saw some shorts of people screwing merchants with chargeback like it is some batch of honour.
I'm not American (I'm from the UK), but filing a chargeback is an incredibly satisfying weapon for a consumer.
So many companies try to weasel out of their legal obligations under consumer protection law, so why not hit them with a chargeback when they won't do what they're required to?
After being burned by PayPal protection not working out, I will now buy anything I can directly on a Credit Card, as you just get so much more protection in the UK - both contractually and legally.
I'm sure chargeback abuse is a thing, but in aggregate, I'd argue people are still not doing enough chargebacks, because businesses are still engaging in unethical (& potentially illegal) practices of billing customers for services not rendered, or unclear pricing, or dark patterns.
Dark patterns with regards to payment should be a big no-no, and the fact they're still around suggests this behavior isn't being punished enough. So we should in fact have more chargebacks, until the situation becomes that it's more profitable to play fair and legal than try dirty tricks.
Unlimited, no-confirmation access to pull money just based on a static card number is a bug to begin with - ideally every money movement would be authorized on the spot or preauthorized in advance up to a limit.
But assuming we do have this bug, it seems like merchants are happily abusing it - "free" trials that are impossible to cancel, unexpected charges buried in 50 pages of T&C, etc. Chargeback is a completely normal reaction to this and I recommend it to everyone.
The heuristic I use is simple: did I expect this charge, and would I have agreed to pay for it had I been asked for upfront? If not, the merchant gets a quick email, and if they're not cooperating, taking unreasonable time to action it or are outright unreachable they're eating a chargeback and it'll be up to them & their processor to argue it further. They are welcome to put their processor/acquirer person on hold for hours (like they would do me if I were to play their game) and see how that works out for them.
But it only adds fees aka an extra tax; you are paying for it. Merchants just up the prices, banks up fees, conversion rates, etc etc. Someone is paying for it and it's always most likely you. The strange idea people have that 'this is free because it is law' is interesting. It is VCs (in neo banks), it is you in established banks. I rather do not pay for any of your chargeback behaviour really.
Ideally, we’d have technical means to prevent people from getting stuffed (the oAuth-style token system I’ve described in other comments on this thread), combined with legal means to ensure businesses are discouraged from doing the stuffing in the first place (and those who do are promptly sued out of existence).
Until this happens, consumers (including me) will keep using chargebacks as their only way to defend their interests.
Also, if we were to magically rewrite the system tomorrow and eliminate card fees and the potential for chargebacks, do you really think businesses worldwide will suddenly lower their prices as a result? The market already demonstrated it is willing to pay the current prices, so the savings from lack of fees/chargebacks will end up in executives’ yachts instead or pissed away in more advertising.
That's an example of selection bias and other confounding factors: HN users are disproportionately American, Americans are more likely to know of chargeback rights than people from other countries, Americans are more likely to have credit cards than people from other countries, American statutory rights in this area (especially for credit rather than debit cards) are stronger than in most other countries, people who abuse chargebacks are more likely to be American than from other countries for all of the foregoing reasons, Americans are more likely to boast than people from most other countries, Reddit has disproportionately many Americans, and people who make shorts about chargebacks are more likely to do chargebacks than people who don't.
Consider statistical rather than anecdotal evidence in this area. According to one payments processing company, Clearly Payments, the USA has slightly below average chargeback rates, at 0.47%, behind the UK, Belgium, Germany, and France:
https://www.clearlypayments.com/blog/chargeback-rate-by-coun...
Where? I heard it many years ago a few times but not for a very long time? Maybe it was a bug which got fixed?
If the cardholder doesn't opt-in then the payment is as good as cash (with the same recourse available as if you paid cash).
This could allow low/no-fee transactions for low-stakes situations where the chargeback protection wasn't going to be used anyway.
If chargebacks go away and aren't replaced by something at least as effective, that means that we're losing one of the most significant advantages intrinsic to the payment mechanism: peace of mind.
Pay with cash. No risk of recurring charges, charging more than what you hand over, etc.
When the merchant fails to deliver or underdelivers -- "my fries were cold" -- appropriate customer service should be meeting the customer at that point and addressing it directly.
Modern systems of unempowered on-the-ground employees and endless loop self-service support stand in the way of that. Consumers naturally respond by pulling the levers that remain, which is invoking the wrath of American Express.
- Keep the money in the bank (and earn interest on it) for another month or so
- Contest fraudulent charges or payments for goods or services that are never delivered
- Earn travel rewards (I know, those have systemic downsides)
- Pay any business in essentially any country in any currency with no fee for you and a low fee for the business
1. Banks are also allowed to charge fees for SEPA transfers, with some limitations.
2. It does care about currencies, in that it only supports one: the E stands for Euro, and all SEPA transfers, in the four rails it provides, are in Euros, including transfers from and to countries that are not in the euro zone.
3. And SEPA isn't limited to the European Union, as it has 36 states participating in the scheme, more than the EU's 27.
- SEPA instant transfers (exist, but cost extra)
- A consistent (across all banks) API to poll for received payments for the merchant
- A consistent API (e.g. an URL schema that browsers do support) to quickly fill in payment details with your bank's transfer form.
Last time I checked instant sepa (which was today) it was free as in zero commissions on either side and was actually instant.
But yes, instant SEPA is often free and often available and very nice when both of those are true.
I want to buy a CD from Amazon for 19.99. I click on my bank application (or maybe some QR code on Amazons site) And that tells my bank app on my phone to authenticate my phone agains the bank And ask for a 16 digit number that is solely for amazon, 19.99 and 20240812
Browser-based flow, where you're already logged into the bank in an existing browser tab:
* Amazon redirects you to oauth-proxy.visa.com where you select your bank (if you've done it already once, it remembers and redirects straight to your bank)
* Visa redirects you to your bank - if you're not logged in, you do a login - this is up to your bank on how to do that - authorize with an existing phone, WebAuthn, etc. On OSes supporting it, this URL can be hooked and handled directly by a native app which may use the device's secure element to store its auth credentials for the bank
* Bank displays you the payment request details (which include your Amazon account email, order ID, etc - all info you need to confirm it's indeed your payment request and not someone else's) and allows you to change them (maybe you want to authorize more or less, or make it one-time/recurring with a daily/weekly/monthly/yearly cap, or set an expiry after which the authorization is no longer valid)
* In the background, Amazon gets a success webhook from Visa (or their processor) saying that this authorization request has been granted, or they can poll an endpoint - this eliminates the need for a final redirect back to them like in normal oAuth
* If this is a recurring charge scenario, Amazon can store this payment request token against your account and use it multiple times, as long as the charges fall within the policy set during initial payment request establishment (if you set a max of $20, they can do as many transactions as they want up to a total of $20).
Device-based flow, where you aren't/don't want to login in to the bank the same browser:
* Amazon redirects to oauth.visa.com as above
* Instead of clicking on your bank directly, you say "authorize via phone", it just encodes the URL of the current page in a QR code so you can scan it on the phone - you then do the above flow there. Because the success/failure of a payment request is already communicated directly between the merchant and Visa, there is no need for your phone to pass any data back to the browser, so no need for a "reverse channel" to be set up.
* On your phone, you may have your banking app installed, so it takes over the domain name of your bank and automatically opens the payment request authorization there, using your existing session within the app.
Point is, not only is there no longer a concept of a card number that can be copied, stolen, or leaked, but the user also remains in control - they can control whether the payment is one-time or recurring, set limits on recurring payments, and be able to cancel these authorizations at any time, after which they're guaranteed that nobody can take more money without going through this auth process again. This eliminates many reasons for chargebacks, and reduces fraud risks for merchants too (merchants are no longer vulnerable since the auth to authorize a new payment request is between the user and their bank directly), so things like behavioral fraud detection or captchas on payment pages are no longer needed.
Downside (for scammers): business models based on a free trial that rely on the user forgetting to cancel, or those who intentionally make cancellation annoying or impossible wouldn't work, because payment requests should list upfront the max amount they can take, and the user can adjust that and make sure the unwanted charge just won't go through even if they tried.
My risk to my credit number being stolen is honestly low. The risk is the merchant providing a substandard service 99% of the time, and an OAuth style payment flow does nothing for that.
Someone like Amazon who is a trusted merchant already negotiates fees with their banks and they likely already have an extremely low fee rate.
What Stripe, Square and PayPal provide is a service for integrators who don’t want to spend money talking to a bank, negotiating a rate, and then implementing the required security to execute their own transactions.
Merchants would love to reject all cards that are a Visa Signature and above, leaving only the very low cost cards as accepted. The Card Networks have engineered via branding and contracts that this does not occur though.
It doesn’t cover credit risk-even on a debit card, there can be a “hold” period of an arbitrary amount before the final transaction clears. When you swipe a card at a gas station, they often run a $50 authorization hold on your account.
It also doesn’t cover merchant fraud—- Visa/MC covers you if the merchant doesn’t ship the product because they’re a fake company.
Then there are value-added warranty services that higher end cards offer. These are easily worth the 1%+ fee.
Safeway gas stations upgraded their pumps to have tap-to-pay.
But with increasing gas prices (and not getting into that), they upped the auth hold to up to $125.
Except many card issuers limit contactless payments to $100... rendering tap to pay useless on the pump because it'll deny the preauth and require chip insertion.
I’ve noticed lately that contactless payments that go over the limit don’t require chip insertion, the reader just asks for the PIN to proceed. Maybe there’s been some updates to the standards?
This almost sounds like a subtle recommendation for the Lightning Network. It's based on single-use invoices that are locked to a specific recipient and is usually limited to specific amounts.
Good luck convincing J. Random User that your cryptocurrency is none of these things.
The fact that invoices are temporary in LN is a weakness of the design, not an intentional choice. The lightning network represents a regression from the typical use-case of cryptocurrency because both sender and receiver need to be online to make a payment.
Sweden thought going cashless would reduce crime. Nope, crime increased.
Paypal etc basically exist to deal with the backward underinvested USA payment systems.
Now I'm confused. There's a better way, and other 1st world countries have already adopted it?
The Netherlands had a similar system where they used physical totp (I believe) terminals which generated them from your bank card + pin, completely offline. Nowadays everyone uses iDEAL identically to what you describe.
The product in that case is not "payments as a service" to the consumer but in fact "payer as a service" to the business. If consumers didn't represent an unbounded ability to generate recurring revenue there are lots of profitable businesses that would go under overnight.
This can be generally be accommodated in my suggested model, they just have to specify upfront how much & how often they'd want to charge. If the gym membership is 50 bucks a month, then the token has a monthly limit of 50 (or maybe a bit more, to account for potential extras). The token lifetime could be set for the membership duration.
> car rentals
Get 1 token with your rental fee + a separate token (scoped until car return date + some time to inspect/discover any damage) for the deposit amount?
You could eliminate a lot of the fraud by moving off a mostly-static identifier to merchant, amount and time-limited tokens the user generates with their bank (or the merchant redirects them there). This would address a lot of the issues - the tokens are useless when leaked (as they only work against the merchant's own account) and can't be misused even by the merchant to go beyond the agreed amount or time limit.
One problem you need to keep in mind is that fraud mitigation is a big industry in an of itself (some of it is real, some complete snake oil but relies on the underlying problem being real to sell itself) and wouldn't be in favor of a system that is inherently immune to (at least some types of) fraud.