Share via

This is a secure 128-bit SSL Encrypted Payment

victor luna 20 Reputation points
2026-05-21T14:49:49.8366667+00:00

This is a secure 128-bit SSL Encrypted Payment how to fix

Microsoft Edge | Microsoft Edge development
0 comments

Answer accepted by question author

AI answer

2026-05-21T14:50:01.53+00:00

The text “This is a secure 128-bit SSL Encrypted Payment” is only a message; it does not itself make a page secure. To “fix” or validate this in Microsoft Edge or a web app, the site must actually use HTTPS with a valid certificate and modern TLS/SSL configuration.

To ensure the payment page is really secure:

  1. Verify HTTPS and padlock in Edge
    • In the Edge address bar, confirm the URL starts with https:// and shows a closed padlock icon.
    • If the page is only http://, it is not encrypted, regardless of any text claiming “secure 128-bit SSL.”
  2. Fix HTTP 403.4 (SSL required) errors
    • If Edge shows an HTTP 403.4 “SSL required” error when browsing to http://..., switch to https://... as required by the server.
    • If managing the site in IIS and the error is unexpected, either:
      • Access the site with https:// (recommended for payment pages), or
      • In IIS SSL settings, clear Require Secure Channel (SSL) and Require 128-bit Encryption if SSL should not be mandatory.
  3. Enforce SSL correctly on the server (for real secure payments)
    • On the web server (IIS), install a valid server certificate and ensure port 443 is configured.
    • In the site properties, enable SSL on port 443 and select Require Secure Channel (SSL) so that any attempt to use http:// is rejected with HTTP 403.4, forcing https://.
  4. For local development and testing
    • When developing a payment page locally (for example in Visual Studio/IIS Express), enable SSL for the project and use the HTTPS URL.
    • Trust the local development certificate when prompted so Edge does not show certificate warnings.
  5. Check certificate trust issues in Edge
    • If Edge shows certificate warnings (e.g., untrusted or invalid certificate), do not rely on the “secure 128-bit” text. The certificate must be valid and trusted by the OS/browser for the connection to be considered secure.

In summary, to “fix” this, ensure the site is actually served over HTTPS with a valid certificate and, if needed, configure IIS to require SSL instead of just displaying a static security message.

References:

AI-generated content may be incorrect. Read our transparency notes for more information.

Was this answer helpful?

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Damien Pham (WICLOUD CORPORATION) 1,755 Reputation points Microsoft External Staff Moderator
    2026-05-22T04:31:49.7766667+00:00

    Hello @victor luna ,

    Thank you for sharing your question

    If you are only visiting the payment page in Edge, the safest check is not the page text itself. The important part is whether the page opens over https:// and Edge does not show a certificate warning. If the page was opened from an email, text message, or popup, I would avoid paying there and instead go to the company’s official website directly. Microsoft’s guidance on safer online payment and scam avoidance is here:

    https://support.microsoft.com/topic/making-safer-financial-transactions-online-d8e8972b-dc56-4ea2-a…

    If you own or manage the site, then this is a web-server configuration issue rather than an Edge issue. I would recommend verifying these:

    1. A valid TLS/SSL certificate is installed for the site.
    2. The certificate is bound to port 443.
    3. The payment page is opened with https://, not http://.
    4. If the site returns HTTP 403.4, that usually means SSL is already being enforced and the page must be accessed over https://.

    If this is an IIS-hosted site, Microsoft’s guidance for enabling SSL and enforcing secure connections is here:

    https://learn.microsoft.com/troubleshoot/developer/webapps/iis/www-authentication-authorization/ena…

    If you are testing locally in Visual Studio/IIS Express, Microsoft also documents enabling SSL for the project, using the SSL URL, and trusting the local development certificate:

    https://learn.microsoft.com/aspnet/web-forms/overview/getting-started/getting-started-with-aspnet-4…

    If you can clarify whether you are the site owner or an end user, I can narrow the answer further.

    If you found my response helpful or informative, I would greatly appreciate it if you could follow this guidance or provide feedback.  

    Thank you.  

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.