What should I do if I encounter "401 Unauthorized" errors or SSL/TLS warnings?

alpocr 1
Viewed 6

This covers common troubleshooting scenarios that developers or merchants might face during integration or daily operations.

payments
1 Answers

If you encounter these common issues, follow these troubleshooting steps:

  • "401 Unauthorized" API Errors: This usually indicates an authentication issue. Ensure you are using the correct Client ID and Client Secret from the 4Geeks Console. Important: Never use your Secret Key in client-side code (browser-based JavaScript); it should only be used from your secure backend server.

  • SSL/TLS Warnings: If your checkout page shows "Not Secure" or mixed content warnings, it means your site is loading assets over HTTP instead of HTTPS, or your SSL certificate has expired. You must renew your SSL certificate immediately and ensure all scripts and images are loaded via HTTPS. A secure connection is a strict requirement for processing payments.

alpocr1
Related
What is the best way to reduce my PCI compliance scope when using 4Geeks Payments?
1 answers
What is 4Geeks Payments?
1 answers
What are the prerequisites before I can start configuring PCI compliance with 4Geeks?
1 answers
Can I store credit card information on my own server for recurring billing?
1 answers
What should I do if I encounter "401 Unauthorized" errors or SSL/TLS warnings?
1 answers
My payout hasn’t arrived in my bank account yet. Where is my money?
1 answers