2 ms·
Presumably the idea is that the account number (i.e. credit card number) is randomised for each transaction - but still valid. So authentication etc. would happ
by untog 13y ago
Presumably the idea is that the account number (i.e. credit card number) is randomised for each transaction - but still valid. So authentication etc. would happen exactly as it does right now. But that number would become invalid immediately after it is debited. That way even if someone intercepted the number they would not be able to use it in the future.
Obviously this only really works for online transactions that don't require a physical card - and even then introduces a ton of complexity to things like refunds. But the idea is interesting.
- dakrisht 13y agoI understand what randomizing a number means. But this doesn't answer the question of how the terminal/processing system knows it's your account being debited? The whole concept of randomization with payments (or anything for that matter with respect to authentication) is impossible. There will ALWAYS have to be some sort of static identifier in order for this to work. Common sense I think. The idea is interesting but I'm not sure exactly what the idea is!! :) If you have an AMEX and you randomize the account number on each transaction, AMEX still has to IDENTIFY your account with something? A name? A PIN? A unique ID? AKA an account number.
- untog 13y agoBut this doesn't answer the question of how the terminal/processing system knows it's your account being debited? It doesn't. It debits an account that is signified by the randomly generated account number. The connection between that number and your actual account would be done by AMEX/in the backend somewhere. In fact, the whole point of such a system would be that the terminal would be blind to it. There would always be a static identifier, but the key is taking that identifier away from the end user. That's where the card details get duplicated.