How to Enable 3D Secure Payments in GoHighLevel — Fraud Protection

If you're running an agency or selling online through GoHighLevel, payment security isn't optional—it's essential. Every declined transaction costs you money. Every successful fraud costs you more. That's where 3D Secure (3DS) authentication comes in.

3D Secure is a cardholder verification protocol that adds an extra layer of security to your checkout process. When enabled with Square payments in GoHighLevel, it automatically triggers verification steps for high-risk transactions, reducing fraud chargebacks while capturing more legitimate sales. In this guide, I'll walk you through exactly how to enable 3D Secure in GoHighLevel, why it matters, and how to troubleshoot common issues.

Ready to strengthen your payment security and reduce fraud? Start your free 30-day GoHighLevel trial and see how thousands of agencies protect their transactions on one unified platform.

What Is 3D Secure (3DS) and Why It Matters

3D Secure is a standardized authentication protocol that verifies cardholders during online transactions. The "3D" stands for three-domain model: the merchant domain, the issuer domain (your customer's bank), and the interoperability domain (the networks connecting them).

Here's what happens when 3DS is enabled: A customer enters their payment information at checkout. Before the transaction processes, the customer's bank may require them to verify their identity—usually through a password, biometric verification, or one-time code. This verification step happens in real-time, and the transaction only completes once the bank confirms the cardholder's authenticity.

Why this matters for your agency:

• Reduces fraud chargebacks: When customers verify their identity, fraudsters can't use stolen cards. Your chargeback rates drop significantly.
• Increases legitimate transaction approval: Banks are more likely to approve 3DS-verified transactions, even for higher amounts.
• Complies with PCI DSS requirements: Strong authentication satisfies Payment Card Industry compliance standards.
• Builds customer trust: Customers know their payments are protected, improving confidence in your brand.

Understanding Strong Customer Authentication (SCA)

Strong Customer Authentication (SCA) is the regulatory framework that powers 3D Secure. If you're selling in Europe or to European customers, SCA is mandatory under the PSD2 (Payment Services Directive 2) regulation. But even in the US, major card networks now recommend SCA implementation.

GoHighLevel's 3DS implementation works with Square's Risk Manager to automatically trigger SCA whenever it's required. You don't manually decide when to authenticate—the system does it intelligently based on risk signals like:

• Transaction amount
• Customer location and IP address
• Purchase history
• Device fingerprinting
• Velocity checks (multiple transactions in short timeframes)

This smart approach means legitimate customers complete their purchases smoothly, while suspicious transactions get the extra verification layer they deserve.

Prerequisites for 3DS with Square Integration

Before you enable 3D Secure in GoHighLevel, make sure you have these elements in place:

• Square account with Risk Manager: 3DS is available to all sellers using Square's Risk Manager. If you don't have Risk Manager enabled, contact Square support to activate it.
• GoHighLevel connected to Square: Your Square account must be properly integrated with GoHighLevel through your payment settings.
• Active checkout or funnel: You'll need at least one active sales funnel, checkout page, or payment form where you want to enable 3DS.
• HTTPS enabled: Your checkout pages must run on HTTPS (secure connection). This is standard for GoHighLevel, but verify it's active.
• Current browser support: 3DS works on all modern browsers. Older browsers may not support the authentication flow, so customers should be using current versions of Chrome, Firefox, Safari, or Edge.

This is built into GoHighLevel. Try it free for 30 days →

How to Enable 3D Secure in GoHighLevel

Enabling 3DS in GoHighLevel is straightforward. Here's the step-by-step process:

Step 1: Navigate to Payment Settings

Log into your GoHighLevel account and go to Settings → Payment Processors. You'll see your connected Square account listed. Click on it to open the Square payment settings.

Step 2: Locate the 3D Secure Toggle

In the Square payment settings, look for the "3D Secure (3DS)" option or "Enable 3DS Authentication" toggle. It's typically in the security or advanced settings section.

Step 3: Enable 3DS

Toggle the 3DS option to the ON position. You'll see a confirmation message indicating that 3DS is now active on your Square integration.

Step 4: Apply to Your Funnels/Checkouts

The setting applies automatically to all funnels and checkout pages connected to this Square processor. You don't need to configure 3DS individually for each funnel—it works globally once enabled.

Step 5: Test the Integration

Create a test transaction using a test card provided by Square. Process a payment and confirm that the 3DS verification flow appears. This ensures everything is working correctly before you go live.

The Complete 3DS Checkout Flow

Understanding the checkout flow helps you anticipate customer experience and troubleshoot issues. Here's what happens when 3DS is enabled:

1. Customer Enters Payment Details

Your customer fills out the standard payment form in GoHighLevel—name, email, card number, expiration, and CVV.

2. Square Risk Manager Evaluates Risk

Square's fraud detection system analyzes the transaction in real-time. It assigns a risk score based on the factors mentioned earlier.

3. 3DS Challenge Is Triggered (If Needed)

If the risk score exceeds the threshold, the customer's bank requires authentication. A modal window appears prompting the customer to verify their identity. They might enter a password, use biometric verification (fingerprint or face ID), or confirm a one-time code sent to their phone.

4. Bank Confirms Authentication

The issuing bank validates the customer's response and sends back an authentication result. This happens seamlessly in the background.

5. Transaction Completes

Once the bank confirms the cardholder, the payment processes. Your customer is redirected to the success page, and you receive the payment confirmation.

Troubleshooting Common 3DS Errors

Error: "3DS Authentication Failed"

If a customer sees this message, they failed the authentication challenge. They can either try again with the correct verification method or use a different card. Make sure your checkout page has clear messaging explaining why authentication is required.

Error: "Your Browser Does Not Support 3DS"

This happens with older browsers or certain mobile devices. Have the customer update their browser or try a different device. On your end, ensure you're using a current version of GoHighLevel—older versions may not support 3DS properly.

Error: "Square Payment Processor Not Connected"

If you can't find the 3DS toggle, your Square account may not be properly integrated. Go to Settings → Payment Processors and re-authenticate your Square connection. Then check if Risk Manager is enabled on your Square account.

Transaction Declined Despite 3DS Verification

Even after successful 3DS authentication, the bank can still decline the transaction for other reasons (insufficient funds, card stolen after verification, etc.). This is rare but possible. Contact the customer and have them verify with their bank.

Best Practices for 3DS Implementation

1. Educate Your Customers

Add a brief explanation to your checkout page: "For your security, we use 3D Secure authentication on eligible purchases. You may need to verify your identity with your bank." This reduces friction and confusion.

2. Test Before Going Live

Use Square's test card numbers to verify the 3DS flow works on your funnels. Test on mobile and desktop to ensure the authentication modal displays correctly on all devices.

3. Monitor Your Metrics

After enabling 3DS, track these metrics: conversion rates, chargeback rates, and fraud rates. You should see chargebacks drop and legitimate conversions increase. GoHighLevel's reporting dashboard shows this data in your sales analytics.

4. Keep Payment Information Updated

Ensure your Square account and GoHighLevel integration are always current. Updates often include security improvements and new features that enhance 3DS performance.

5. Don't Disable 3DS to Boost Conversions

Yes, some transactions are declined due to failed 3DS verification. But disabling 3DS entirely exposes you to fraud liability that costs far more than a few declined conversions. Keep 3DS enabled and focus on clear customer communication instead.