Square payment links vs. on-site card forms: which is right for your website?

If you take payments on your website with Square, there are two broad ways to do it. You can embed a card form directly in your pages, or you can send customers to a Square-hosted checkout page using a payment link. Both work. They just suit different businesses.

How hosted payment links work

Your website asks Square (through its Checkout API) to create a payment link for a specific amount - an invoice balance, a deposit, an event ticket. The customer clicks Pay, lands on Square's secure checkout, pays with a card, Apple Pay or Google Pay, and is sent back to your site. Square then tells your system the payment went through, usually within seconds, via a webhook.

Why we usually recommend hosted checkout

• Smaller security burden. Card numbers never touch your server, which keeps your PCI compliance paperwork to the simplest level.
• Apple Pay and Google Pay with no extra work. Wallet payments appear automatically on supported devices.
• Faster to build and cheaper to maintain. There's no payment form to style, test and keep up to date across browsers.
• Familiar and trusted. Many customers already recognise Square's checkout.

When an embedded form makes more sense

If checkout is the heart of your product - a high-volume store where every extra click costs sales, or a subscription flow that needs to feel seamless - an embedded form can be worth the extra development and compliance work. For invoices, deposits, bookings and event registrations, hosted links are almost always the better trade.

Don't forget the back office

Whichever route you choose, the real win is what happens after the payment: the invoice marks itself paid, the booking is confirmed, and the Square processing fee is recorded so your books match your bank deposit. That's the part most quick integrations skip - and the part that saves you hours every month.

Learn more about our Square payment integration work, or tell us how you take payments today.