Timeline for Using credit/debit card details vs swiping a card in a payment (credit card) terminal
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2019 at 22:49 | comment | added | Makyen | Basically, any terminal with a keypad will have the capability to enter a card number/transaction manually. That feature may be behind a password (either dynamically, or an options setting that is only accessible with a password) that the merchant, or the person running the terminal, does not know. For example, for terminals acquired from the processor, the merchant may have never been given the configuration password. It's also possible that the options are set such that the feature only appears when there are multiple failed attempts to read the card. | |
| May 24, 2019 at 17:06 | comment | added | jcaron | @Accumulation so the risk is on the merchant, not the bank (other than a few cases where the merchant cannot refund the charge, but those are edge cases). | |
| May 24, 2019 at 14:45 | comment | added | Acccumulation | "Usually the risk lies with the bank" The risk pretty much always lies with a bank. With a secure mode, the risk lies with the issuing bank. With insecure methods, the risk lies with the acquiring bank (who then passes the chargeback along to the merchant). | |
| May 23, 2019 at 16:50 | history | answered | jcaron | CC BY-SA 4.0 |