Websites
How to accept payments on your website: Stripe, PayPal or Square?
To take card payments on your website you need a payment processor such as Stripe, PayPal or Square. In the US, Stripe charges 2.9% + 30¢ per online card payment with no monthly fee, PayPal Checkout 3.49% + 49¢, and Square 3.3% + 30¢ on its free plan. The cheapest setup for most small businesses is a hosted checkout page from the processor: card data never touches your site, and your security paperwork stays minimal.
Contents
Key points
- Stripe charges 2.9% + 30¢ per US online card payment, PayPal Checkout 3.49% + 49¢, Square 3.3% + 30¢ on its free plan.
- International cards cost about 1.5% more with all three.
- Processors review your website before approval: contact details, prices, terms, shipping and refund policy.
- A hosted checkout page keeps card data off your server, which keeps PCI compliance to the shortest form.
- You don't need an online store to get paid online: a payment link on a button works for deposits, vouchers and services.
Card payments on a website don't go to your bank directly. They go through a payment processor, a company that takes the money from the customer, checks the payment and pays it out to your bank account minus its fee. Below are the main options for a small business, what each costs, and what your site needs before a processor will approve it. What the rest of an online store costs is in our guide to online store pricing.
Stripe vs PayPal vs Square: what each costs
Three processors cover most small business websites in the US:
| Processor | Online card fee (US) | Monthly fee | Best for |
|---|---|---|---|
| Stripe | 2.9% + 30¢ | None | Online stores, subscriptions, custom sites |
| PayPal Checkout button | 3.49% + 49¢ | None | Buyers who prefer to pay with PayPal or Venmo |
| PayPal card processing | 2.89% + 29¢ | None | Card payments if you already use PayPal |
| Square (Free plan) | 3.3% + 30¢ | None | Businesses that also take payments in person with Square |
| Square (Plus or Premium) | 2.9% + 30¢ | Plan fee | Higher-volume Square users |
Prices are from each company's own pricing page in October 2026. All three add about 1.5% for cards issued outside the US, and charge extra when a currency has to be converted. Square's online rate depends on your plan, so comparisons that show 2.9% + 30¢ for every Square user are out of date.
What it costs on a real month
A percentage means little until you put your own volume on it. Take 100 orders a month at $50 each, $5,000 in sales:
| Payment method | Calculation | Monthly cost |
|---|---|---|
| PayPal card processing | 2.89% × $5,000 + 100 × 29¢ | $173.50 |
| Stripe | 2.9% × $5,000 + 100 × 30¢ | $175 |
| Square, Free plan | 3.3% × $5,000 + 100 × 30¢ | $195 |
| PayPal Checkout button | 3.49% × $5,000 + 100 × 49¢ | $223.50 |
The fixed fee matters most on small orders: on a $10 sale, Stripe's 30¢ adds another 3%. If your average order is small, compare the total, not the percentage.
What processors check before approving you
Every processor reviews your business and your website before it lets you take payments, because it answers to the card networks for the merchants it signs up. Have ready:
- Business details on the site: legal name, address, email and phone.
- Terms of service and a privacy policy.
- Shipping and refund policy, with timeframes and who pays for returns.
- Final prices on every product or service.
- A business bank account and your tax ID (EIN or SSN for sole proprietors).
What else the law expects on a business website is in our guide to website legal requirements.
Hosted checkout or a card form on your own page?
For most small businesses, the hosted checkout page is the right choice. The customer clicks "Pay", lands on the processor's page (Stripe Checkout, for example), pays and comes back to your site. Card numbers never pass through your server, so you qualify for the shortest PCI self-assessment and have far less to secure.
A card form embedded in your own page looks more seamless, but it takes more work to build and more care to keep secure. For a small shop, the conversion gain rarely pays for the effort.
Turn on Apple Pay and Google Pay in the processor's dashboard; there's usually no extra charge. On a phone they cut checkout to a tap, because the customer doesn't type a card number.
Getting paid without an online store
You don't need a shopping cart to take card payments. A few options:
- Payment links: Stripe Payment Links, PayPal and Square create a link you put on a button or send by email and text. Good for deposits, gift vouchers, classes and services paid upfront.
- Deposits at booking: booking systems can take a card deposit when the client books, which cuts no-shows. See online booking for salons and clinics.
- Subscriptions: monthly or yearly recurring payments for memberships, classes or retainers. Stripe and Square both support them.
If you sell food, ordering directly on your own site without delivery-app commission is covered in commission-free online ordering.
Payouts, sales tax and disputes
Payouts. Processors pay out on a schedule, usually a couple of business days after the payment. The payout is net of fees, so your bank statement won't match your orders one to one. Your bookkeeper needs the processor's payout report, which lists each payment and its fee.
Sales tax. Since the Supreme Court's South Dakota v. Wayfair decision in 2018, states can require out-of-state sellers to collect sales tax once they pass an economic threshold. If you ship to other states, check with your accountant; Stripe, Square and most store platforms can calculate the tax for you.
Disputes. When a customer disputes a charge with their bank, the processor asks you for evidence: order confirmation, proof of delivery, messages. At Stripe in the US, each dispute costs $15. Clear descriptions on your site and confirmation emails are what win disputes.
Checklist
- Your site shows business details, terms, shipping, refunds and final prices.
- You compared at least two processors on your real monthly volume.
- Checkout runs on the processor's hosted page, with Apple Pay and Google Pay on.
- Customers get a payment confirmation and receipt by email.
- Your bookkeeper gets the payout report every month.
- Someone knows how to answer a dispute and what evidence to send.
We connect the sites and stores we build to the processor you choose and to your invoicing, so a paid order flows through to the receipt on its own. See our web development page.
Questions
What is the cheapest way to accept payments on a website?
For most small businesses, Stripe or PayPal's card processing at around 2.9% plus a fixed fee, with no monthly fee. PayPal's own checkout button costs more (3.49% + 49¢). Above a few hundred thousand dollars a year, ask processors for custom or interchange-plus pricing.
Stripe vs PayPal: which is better for a small business?
Use Stripe (or PayPal's card processing) for the main card form, and add the PayPal button only if your customers ask for it. Stripe is cheaper on cards and easier to connect to invoicing and subscriptions; PayPal's button helps when buyers don't want to type card details.
Can I accept payments without an online store?
Yes. Stripe Payment Links, PayPal and Square all create a payment link you can put on a button or send by email or text. It works well for deposits, services, classes and gift vouchers.
Do I need to be PCI compliant?
Yes, every business that takes cards does, but with a hosted checkout page the card data never touches your site and you qualify for the shortest self-assessment questionnaire. Building your own card form means more work.
How much does a chargeback cost?
At Stripe in the US, $15 per dispute. If you win, the disputed amount comes back to you. Clear product descriptions, delivery confirmation and order emails are your evidence.
Sources
- Stripe pricing (United States), Stripe
- PayPal business fees (US), last updated 1 October 2026, PayPal
- What are Square's fees?, Square
- South Dakota v. Wayfair, Inc., 585 U.S. 162 (2018), Legal Information Institute, Cornell Law School
- Commission Delegated Regulation (EU) 2018/389 on strong customer authentication, EUR-Lex