Regarding the insecure transmission of data over a network.
When it comes to plaintext credit card information and payment details being transferred in this manner over HTTPS. What are the possible methods of attack or vulnerabilities presented to a system administrator over the network API, if any? If so, are they strictly network-based attacks such as simple MITM attacks, by a user using a public proxy setup? Or attacks opened up by a user on the same network.
My main concern is the risk versus reward in this scenario, ultimately, should sensitive credit card details be transmitted over the network in plaintext/binary? Is this good practice.
Or are there preferable standards and methods for the transmission of sensitive data pertaining to payment details in place and documented? Such as global standards for payment processing.
Example Request (User Browser Form) - Copied in Curl Format via HTTPS
curl '' \ -H 'Connection: keep-alive' \ -H 'Accept: application/json' \ -H 'User-Agent: ' \ -H 'Content-Type: application/json' \ -H 'Origin: ' \ -H 'Sec-Fetch-Site: same-site' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Referer: ' \ -H 'Accept-Language: en-US,en; q=0.9' \ --data-binary ' ' \ --compressed
The insecure plaintext payment info is located:
--data--binary 'PAYMENT_INFO_PLAINTEXT' \ --compressed