From 3bc76b328c0ba8b2273214c6f4cb10fb681ce3d0 Mon Sep 17 00:00:00 2001 From: PrismaFox Date: Wed, 22 Jan 2025 18:28:25 -0500 Subject: [PATCH] Update README.md 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. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fc48a80..88e1d33 100644 --- a/README.md +++ b/README.md @@ -47,7 +47,7 @@ for ATH Móvil Payment Button API. The ATH Móvil Payment Button is an API REST based application implemented to support ecommerce payments for ATH Business merchants. The API is available for integration, but the merchant must have an active ATH Business account with an active ATH card to receive payments. -Ours clients that use the Payment Button (PB) will be able to integrate each of these granular services into their business components and/or applications. This code works with HTTP protocols offered by REST based interfaces that are implemented through a separately web-based API layer. They can take advantage of multiple deployable service components, scalability, and a high degree of application and component decoupling provided by the API. +Our clients that use the Payment Button (PB) will be able to integrate each of these granular services into their business components and/or applications. This code works with HTTPS protocols offered by RESTful interfaces that are implemented through a separate web-based API layer. They can take advantage of multiple deployable service components, scalability, and a high degree of application and component decoupling provided by the API. The API called for this JavaScript code is build based on JWT protocol to securely authenticate the communication between our services.