Square Payments: Enhanced Security with 3D Secure (3DS)

What is 3D Secure (3DS) for Square?

3D Secure (3DS) is a security protocol that adds an extra verification step during online payments. When enabled, it prompts buyers to confirm their identity—for example, by entering a one-time code sent via SMS or using biometric authentication—before a transaction can be approved. This helps reduce fraud and shifts liability for chargebacks to the card issuer once authentication is successful. The CRM now supports this feature with Square, automatically passing the necessary data to trigger 3DS verification when required.

Key Benefits of 3D Secure (3DS) for Square

Integrating 3DS with Square in your CRM offers several advantages:

• Higher conversion rates: Fewer payments are declined on cards that require 3DS authentication.
• Enhanced fraud protection: Liability for chargebacks shifts to the card issuer after successful verification.
• Automatic compliance: Meets Strong Customer Authentication (SCA) requirements in regions like the UK and EU without additional setup.
• Seamless experience: Buyers stay within your CRM funnel during verification, thanks to an integrated pop-up.

How 3DS Works in the CRM Checkout Flow

Once your Square account is connected, 3DS verification happens automatically:

1. The buyer enters their billing address and contact information during checkout on an Order Form, Payment Element, Invoice, or Store.
2. The CRM sends the transaction details to Square.
3. Square’s risk engine determines if 3DS is needed based on factors like the card used, transaction amount, and location.
4. If required, a secure pop-up appears for the buyer to complete authentication.
5. Upon successful verification, the payment is captured, and the order or invoice status updates to “Paid.”
6. If verification fails or times out, the payment is declined, and the buyer sees an error message prompting them to try another card.

Prerequisites and Supported Flows

3DS for Square is available wherever Square card payments are accepted in the CRM, including Order Forms, Payment Links, Ecommerce Store, and Invoices.

Prerequisites:

• A connected Square account in your CRM under Sub-Account → Payments → Integrations.
• Square location set to Live mode.
• Billing Address and Email or Phone fields visible (and preferably required) on the checkout form.
• The buyer’s card and issuing bank must support 3DS.

Error Handling and Troubleshooting

Common scenarios and how to address them:

• “Authentication failed”: The buyer entered an incorrect code or declined biometric verification. Ask them to retry or use a different card.
• “Issuer declined”: The card-issuing bank blocked the transaction. Suggest the buyer contact their bank.
• “3DS not completed”: The buyer closed the pop-up. Encourage them to complete the verification step.

All transaction responses are logged in the CRM under Payments → Transactions for easy reference.

Frequently Asked Questions

Do I need to enable anything in the Square Dashboard?

No. Square’s Risk Manager applies 3DS automatically based on its default rules.

Does 3DS work for saved “Card on File” payments?

No. 3DS only applies to real-time, cardholder-initiated payments.

Is there an extra fee for using 3DS?

No. Square does not charge additional fees for 3DS; standard processing rates apply.

Will 3DS appear on every transaction?

No. It is triggered only when required by the card issuer or Square’s risk engine.

Can I disable 3DS?

No. Square manages the rules, and disabling it is not recommended, especially in SCA regions.

Does 3DS slow down checkout?

The verification step typically adds only a few seconds and is designed to minimize friction.

Is 3DS supported on POS or Mobile Payments?

No. 3DS is for online payments only. In-person transactions use other security methods.

How do I troubleshoot repeated 3DS failures?

Ensure the billing address matches the card issuer’s records, confirm the buyer’s device allows pop-ups, and suggest trying another card if issues persist.