3D Secure (3DS) for Square Payments in Sparkforge

By Sparkforge Support Team ·Last reviewed May 3, 2026

3D Secure (3DS) on Square adds cardholder authentication to Sparkforge checkouts. It triggers automatically when the card or region requires it, shifts chargeback liability after success, and needs no extra setup beyond a connected Square account.

Sparkforge now supports 3D Secure (3DS) on Square checkouts. When a card or region requires Strong Customer Authentication (SCA), Square asks the buyer to verify identity before the transaction is authorized — and Sparkforge passes the data needed to trigger that step.

What 3DS does for you

  • Fewer payment failures on cards that mandate 3DS, so more checkouts complete.
  • Chargeback liability shifts to the issuing bank once authentication succeeds.
  • Automatic SCA compliance in regions like the UK and EU.
  • In-checkout pop-up keeps the buyer inside your Sparkforge funnel.

Checkout flow

  1. Buyer fills the billing address and contact fields on an Order Form, Payment Element, Invoice, or Store checkout.
  2. Sparkforge sends the transaction to Square. Square's risk rules decide whether 3DS is required.
  3. If 3DS triggers, a secure modal asks the buyer to verify (one-time SMS code, Face ID, or bank redirect).
  4. On success, the payment captures and the order or invoice flips to Paid.
  5. If verification fails or times out, the payment is declined and the gateway error is surfaced so the buyer can retry or use another card.

Prerequisites

  • Square account connected at Sub-Account → Payments → Integrations.
  • Square location set to Live mode.
  • Billing address and email or phone fields visible — and ideally required — on the checkout form.
  • Buyer's card and issuing bank must support 3DS.

3DS is available everywhere you already accept Square card payments in Sparkforge: Order Forms, Payment Links, the Ecommerce Store, and Invoices.

Common 3DS errors

  • Authentication failed — wrong SMS code or declined biometric prompt. Ask the buyer to retry or use a different card.
  • Issuer declined — the bank blocked the transaction. The buyer should contact the bank.
  • 3DS not completed — the buyer closed the pop-up. Encourage them to finish the verification.

Every gateway response is logged under Payments → Transactions.

Frequently Asked Questions

Do I have to enable 3DS manually for Square?
No. With Square it just works once the buyer completes the address and contact fields at checkout. Square decides when 3DS is required.
What is the chargeback benefit?
Once a transaction passes 3DS authentication, fraud-related chargeback liability shifts from you to the card issuer.
Where does 3DS apply in Sparkforge?
Anywhere Square processes card payments: Order Forms, Payment Links, the Ecommerce Store, Invoices, and the Payment Element.
What happens if the buyer fails verification?
The payment declines, the buyer sees the gateway error, and the transaction is logged under Payments → Transactions for review.
Does this make me SCA-compliant in the EU and UK?
Yes. 3DS is the SCA mechanism Square uses to satisfy EU and UK regulations, and Sparkforge passes the data Square needs to invoke it.

Was this article helpful?

Related Articles