Open
Conversation
This commit corrects the documentation to specify that all API communications are conducted over HTTPS rather than the more general term "HTTP protocols". The original text incorrectly suggested that the API could be accessed via HTTP, which is not secure and not the case here. The ATH Mobil Payment Button API exclusively uses HTTPS to ensure secure communication between the client and server, safeguarding sensitive payment information from interception or tampering. This change: - Clarifies that the API operates strictly over HTTPS, enhancing security awareness among developers and users. - Aligns the documentation with actual implementation details, ensuring that no one attempts to use less secure HTTP connections. - Supports better integration practices by emphasizing the use of secure communication protocols, which is crucial for handling payment transactions. By making this adjustment, we aim to prevent potential security vulnerabilities and ensure that all integrations with the Payment Button API are performed securely. This also helps in maintaining compliance with standards that require secure communication channels for financial transactions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This commit corrects the documentation to specify that all API communications are conducted over HTTPS rather than the more general term "HTTP protocols". The original text incorrectly suggested that the API could be accessed via HTTP, which is not secure and not the case here.
The ATH Mobil Payment Button API exclusively uses HTTPS to ensure secure communication between the client and server, safeguarding sensitive payment information from interception or tampering. This change:
By making this adjustment, we aim to prevent potential security vulnerabilities and ensure that all integrations with the Payment Button API are performed securely. This also helps in maintaining compliance with standards that require secure communication channels for financial transactions.