4 ms·
The first paragraph suggests you'll need to explicitly aurhorise the first payment. The third paragraph suggests you'll just receive cancellation instructions
by rahimnathwani 8y ago
The first paragraph suggests you'll need to explicitly aurhorise the first payment.
The third paragraph suggests you'll just receive cancellation instructions before the first payment.
The former would be a massive improvement. The latter is similar to what most (sadly, not all) companies do already.
Not sure which is the case. Anyone got a better source?
- nobrains 8y agoYes. This was my same thought. So what if they will send you instructions to cancel? As petilion (https://news.ycombinator.com/user?id=petilon https://news.ycombinator.com/user?id=petilon) mentioned here (https://news.ycombinator.com/item?id=18927948 https://news.ycombinator.com/item?id=18927948) the instructions are designed to make you give up the cancellation process. The right mechanism should be to request explicit authorization.
- sirn 8y agoThe whole credit card payment system is built on another legacy system (we have emboss letter on credit card because of compatibility with a zip-zap machine!) so having explicit authorization consent for recurring payment is probably not going to be as easy as it seems. The last time payment industry tried to do something that resembles an explicit user consent, it resulted in the 3-D Secure system, which is horrendous and not even secure.
- Silhouette 8y agoThe last time payment industry tried to do something that resembles an explicit user consent, it resulted in the 3-D Secure system, which is horrendous and not even secure. Meanwhile, merchants in Europe are looking forward to the new Strong Customer Authentication rules under PSD2 that will come into effect later this year. At least it will be interesting to have hard data on how much damage that causes and whether the damage is worse than the cost of fraud it will supposedly prevent.
- sirn 8y agoAFAIK the new Strong Customer Authentication will be based on 3-D Secure 2, which as far as I know is basically bundling a couple of existing verification method (e.g. AVS, Address Verification System) under a new scheme and fallback to 3-D Secure authentication if the trust level isn’t met. The issue is that, well, the whole scheme is designed to protect the merchant (via liability shift) and not the user, and we still have to trust the bank to “verify” us (might not be a big problem in EU, but in Asia it’s still common to have OTP code over SMS or even... a 6 digit passcode)
- tyfon 8y agoAnd now all the companies will charge you 1 cent for the "free trial" so that the card can be "activated" and then refunded. I see that already from many including our country's national rail company.
- sirn 8y agoThis is probably enforced at the policy level rather than systematic, like many other things in the credit card industry. The likely implementation of this, is that the merchant will be liable for chargebacks if they can't prove that the they've sent the consent email or text message. Usually a recurring transaction has a different indicator flag set (ISO 8583 field 22, IIRC), and AFAIK subjected to a different liability profile than a standard e-commerce transaction. So I believe this has more impact on the merchant side than a customer. Disclosure: I (used to) work in credit card payment industry. I have not read the details on this one, though.