Accepting Payments (Stripe, Square, Payment Processing)

beginner7 min read · updated 2026-06-20

Accepting Payments (Stripe, Square, Payment Processing)

If a customer can't pay you in the moment they decide to buy, you lose the sale. Getting paid is plumbing — boring, unglamorous, and the single most important system in your business. This guide covers how to pick a processor, what you'll actually pay, the compliance floor you can't skip, and a step-by-step setup.

The market is enormous: global digital payment transaction value is projected at roughly 37450000000000 USD for 2026. You are not fighting to invent demand for card payments — you're plugging into a river that already flows.

The two players you'll actually consider

For most small businesses, the real choice is Stripe vs Square, with a few situational alternatives (PayPal, Shopify Payments, Adyen for scale). Both Stripe and Square are "payment service providers" (PSPs) — they let you start taking cards in an afternoon without applying for a traditional merchant account.

• Stripe is developer-first. It shines for online businesses, SaaS, marketplaces, subscriptions, and anything you're building custom. It has the deepest API and the broadest feature set (Billing, Invoicing, Connect, Tax).
• Square is retail-first. It shines for in-person sales — a coffee shop, a salon, a market stall. The hardware (reader, terminal, register) and point-of-sale software are the product, and online tools are bundled in.

A simple rule of thumb: if you swipe cards in person, lean Square; if you charge cards over the internet, lean Stripe. Many businesses end up using both.

What you'll actually pay

These are published standard rates as of this writing. Always confirm on the official pages — processors change pricing.

Stripe (online, domestic cards): 2.9% + 0.30 USD per successful charge. Add ~0.5% for manually keyed cards, ~1.5% for international cards, and ~1% if currency conversion is needed. ACH direct debit is 0.8% capped at $5.00. Disputes (chargebacks) cost 15 USD each.

Square (free plan): in-person tap/dip/swipe is 2.6% + $0.15; online card is 3.3% + $0.30; manual entry / card-on-file is 3.5% + $0.15. Paid tiers (Square Plus at $49/mo, Premium at $149/mo) lower in-person and online rates. (See the Square fees page for the current tier table.)

The headline percentage is not your real cost. Your effective rate is total fees divided by total volume, and it climbs with international cards, chargebacks, currency conversion, and add-on products. Track your effective rate monthly — if you're well above 3% on domestic card volume, something (a pricing tier, an add-on, or a fraud problem) is leaking money.

PCI DSS: the compliance floor

Any business that accepts cards must comply with the Payment Card Industry Data Security Standard (PCI DSS), maintained by the PCI Security Standards Council (founded by Visa, Mastercard, Amex, Discover, and JCB). Compliance is not optional and is not a one-time event.

The good news: if you use Stripe's hosted checkout / Stripe Elements or Square's hosted forms and hardware, the card data never touches your own servers, and your obligation usually collapses to the simplest Self-Assessment Questionnaire (SAQ A) — a short checklist rather than a full audit. The moment you start handling raw card numbers yourself, your scope explodes. Don't. Let the processor's hosted fields carry the cardholder data.

Disclaimer: This entry is educational, not legal, tax, or financial advice. Verify your exact PCI obligations with your processor and a qualified advisor.

Step-by-step: get paid this week

• Decide in-person vs online (or both). This picks your default processor. In-person heavy → Square. Online heavy → Stripe. If both, set up both and route each channel to the cheaper rate.
• Create the account. Sign up at the official site, verify your email, and enable two-factor authentication immediately. This is a money account — treat its security like a bank login.
• Complete business verification (KYC). You'll provide legal business name, EIN or SSN (for sole props), business address, and a bank account for payouts. Use your real legal entity details to avoid payout holds later.
• Connect your payout bank account. Confirm the micro-deposits or instant-verify, and set your payout schedule (daily, weekly, or manual).
• Choose your integration. For online: a no-code Stripe Payment Link or Square Online checkout for the fastest start; hosted checkout (Stripe Checkout / Square Web Payments SDK) for a branded flow; full API only if you have a developer. For in-person: order the reader/terminal and pair it.
• Stay in low-PCI-scope mode. Use hosted/embedded fields so card data never hits your servers — this keeps you on SAQ A. Never log, email, or store raw card numbers.
• Run a real test transaction. Use the processor's test mode first, then push one live transaction with your own card and immediately refund it. Confirm the funds land in your bank on the expected payout date.
• Set up tax, receipts, and refunds. Enable automatic tax (Stripe Tax / Square's tax settings) if you owe sales tax, turn on email receipts, and document your refund policy on the checkout page — clear policies reduce disputes.
• Build a dispute defense routine. Keep order records, delivery proof, and customer communications. When a chargeback arrives you have a short window to respond; organized evidence is how you win them and avoid the per-dispute fee.
• Review your effective rate monthly. Pull the fees report, divide total fees by total processed volume, and renegotiate or switch tiers/processors if it drifts high.

Common mistakes that cost real money

• Storing card data to "save customers time." This blows up your PCI scope and your liability. Use the processor's vault/customer object instead — it stores a token, not the card.
• Ignoring chargebacks. Each one costs a fee and, if your dispute rate gets too high, processors can freeze or terminate your account. Respond to every one.
• Mismatched legal details. A name or tax-ID mismatch between your processor and your bank is the most common cause of payout holds for new accounts.
• Picking on percentage alone. A 0.1% difference is noise next to a fraud problem, a payout-hold, or a checkout that scares customers away. Conversion and reliability beat a slightly lower rate.

The bottom line

Pick the processor that matches where your money comes from, use hosted payment fields to stay in the simplest compliance tier, run one live test-and-refund before you trust it, and watch your effective rate every month. Done right, payments become invisible infrastructure — exactly what you want.