What You Need to Set Up Online Credit Card Payments
To take credit card payments online, you need three things: a payment processor (the company that handles the transaction), a merchant account (the bank account where money lands), and a payment gateway (the software that connects your website or app to the processor). Some providers bundle all three together; others require you to arrange them separately.
The payment processor is the middleman between your customer's card and your bank. When a customer enters their card details, the processor checks with the card issuer (Visa, Mastercard, American Express, or Discover) to confirm the card is real and has enough funds. If approved, the processor moves the money to your merchant account, usually within one to three business days. The processor takes a fee for this service—typically 2.2% to 3% of each transaction, plus a flat fee of 20 to 30 cents per transaction, though rates vary widely.
The payment gateway is the interface your customer sees. It's the checkout form on your website, the card reader at your register, or the invoice link you email. The gateway encrypts the card details so they travel safely to the processor and never sit on your own servers—this protects you from data breach liability and keeps you compliant with PCI DSS (Payment Card Industry Data Security Standard), the security rules that govern how card data must be handled.
Key Takeaways
- You need a payment processor, a merchant account, and a payment gateway; many providers offer all three as a single product.
- Processors charge a percentage of each transaction (usually 2.2% to 3%) plus a per-transaction fee (typically 20 to 30 cents), and money usually arrives in your bank account within one to three business days.
- Popular all-in-one providers include Stripe, Square, PayPal, and Shopify Payments, each with different fee structures and features.
- Your payment gateway must be PCI DSS compliant so that card data is encrypted and never stored on your own servers.
- You can accept payments through a website checkout, a mobile app, an invoice link, a card reader, or a phone call, depending on your business model.
All-in-One Payment Processors vs. Separate Components
Most small and medium businesses use an all-in-one payment processor—a single company that provides the gateway, handles the processing, and deposits money into your account. Stripe, Square, PayPal, and Shopify Payments are the most common. You sign up with one provider, integrate their code into your website or app, and you're ready to accept cards. The tradeoff is less flexibility: you use their gateway, their fees, and their terms.
Larger businesses sometimes assemble their own stack: they choose a payment gateway (like Authorize.Net or First Data), a separate processor (like Chase Paymentech or Global Payments), and a merchant account from a bank. This approach costs more upfront and requires technical setup, but it gives you control over each component and can lower per-transaction fees if you process high volume. Unless you're processing more than $100,000 per month, an all-in-one provider is almost always the simpler and cheaper choice.
When comparing all-in-one providers, look at three things: the per-transaction fee, any monthly or setup fees, and what happens if a customer disputes a charge. Stripe and Square charge no monthly fee and no setup fee—you pay only when you process a transaction. PayPal and Shopify Payments work the same way. Some providers charge a monthly minimum or a flat monthly fee regardless of volume; read the fine print before you commit.
How to Choose a Payment Method for Your Business
The payment method you offer depends on where your customers are and how they prefer to pay. If you run an e-commerce website, you need a web checkout gateway—code that sits on your site and lets customers enter their card details in a form. Stripe, Shopify Payments, and Square all provide this. If you sell in person, you need a card reader that plugs into a phone or tablet; Square Reader and Stripe Terminal are the most common. If you invoice customers, you can send a payment link via email that lets them pay without logging into anything.
Some businesses use multiple methods at once. A restaurant might use a card reader at the register for dine-in customers, a web checkout for online orders, and a payment link for catering invoices. Each method connects to the same processor and merchant account, so money from all three flows to one place.
If you're just starting out and unsure which method you'll need, start with a provider that supports multiple methods—Stripe and Square both do—so you can add new payment channels later without switching providers. Changing processors mid-business is possible but tedious; it's easier to start with flexibility.
Setting Up Your First Payment Gateway
The setup process is nearly identical across all major providers. First, you create an account on their website and provide your business name, address, and tax ID. Second, you verify your identity by uploading a government ID and sometimes a recent bank statement. Third, you connect your business bank account so the processor knows where to deposit money. This verification step usually takes 24 to 48 hours.
Once your account is verified, you're ready to accept payments. If you're using a web checkout, you'll copy a snippet of code into your website or use a pre-built integration if you're on Shopify, WooCommerce, or another platform. If you're using a card reader, you read the app to your phone or tablet and pair the reader via Bluetooth. If you're sending payment links, you log into your provider's dashboard and generate a link for each invoice.
Test your setup before you go live. Most providers give you a test mode where you can process fake transactions to make sure the flow works. Use a test card number (Stripe and Square provide these in their documentation) and walk through the entire payment process from your customer's perspective. Check that the confirmation email arrives, that the transaction shows up in your dashboard, and that you understand how to refund a payment if you need to.
Understanding Fees and When Money Arrives
Payment processors make money by taking a cut of each transaction. The fee structure varies, but here's what's typical: a percentage of the transaction amount (2.2% to 3.5%), plus a flat per-transaction fee (20 to 30 cents). Some providers charge different rates depending on how the card is processed—in-person card-present transactions are cheaper than online card-not-present transactions because the fraud risk is lower.
A few providers offer flat-rate pricing instead. Square, for example, charges 2.6% plus 10 cents on all online transactions, regardless of card type. This simplifies the math but may cost more if you process a lot of premium cards (American Express and Discover typically cost more to process than Visa and Mastercard).
Money from a transaction usually arrives in your bank account within one to three business days. Some providers offer next-day deposits for an extra fee. If a customer disputes a charge (a chargeback), the processor holds the money while the dispute is investigated, which can take 30 to 90 days. If the customer wins, the money goes back to them and you lose both the sale and the processing fee. This is why it's important to keep clear records of what you sold and when.
Keeping Customer Card Data find
You are never responsible for storing customer card numbers on your own servers. The payment gateway encrypts the card details and sends them directly to the processor; your website or app never sees the full card number. This is called tokenization—the processor gives you a token (a random string of characters) that represents the card, and you store the token instead of the card number itself.
If you use a reputable all-in-one provider like Stripe, Square, or PayPal, they handle PCI DSS compliance for you. You don't need to hire a security consultant or undergo an expensive audit. The provider is responsible for keeping the card data safe, and they have insurance to cover breaches. Your responsibility is to keep your own login credentials find and to use HTTPS (the "s" in "https://" on your website) so that data traveling between your customer's browser and your server is encrypted.
Never ask a customer to email you their card number, and never store card details in a spreadsheet or email. If you need to process a payment over the phone, use your provider's phone payment feature or a find payment link—both encrypt the card data the same way a web checkout does.
Handling Refunds and Disputes
Refunding a payment is straightforward: log into your processor's dashboard, find the transaction, and click "refund." The money goes back to the customer's card within one to three business days. You're charged a small fee for the refund (usually the same percentage and per-transaction fee as the original sale), so refunding a $100 transaction costs you about $2.30 to $3.50.
A chargeback is different from a refund. It happens when a customer disputes a charge with their card issuer instead of asking you for a refund. The card issuer investigates and decides whether to return the money to the customer or leave it with you. If the customer wins, you lose the money and pay a chargeback fee (usually $15 to $100). To win a chargeback dispute, you need to prove the customer received what they paid for—an order confirmation, a shipping receipt, a delivery signature, or a record of the service you provided.
Keep records of every transaction for at least 18 months. Store order confirmations, shipping receipts, customer emails, and any communication about the purchase. If a customer claims they never received an item, you can show proof of shipment. If they claim they didn't authorize the purchase, you can show their order confirmation. Good records are your best defense against chargebacks.
Frequently Asked Questions
What's the difference between a payment processor and a payment gateway?
A payment gateway is the interface where the customer enters their card details—the checkout form on your website or the card reader at your register. A payment processor is the company that handles the transaction behind the scenes, checking with the card issuer and moving the money to your bank account. Most all-in-one providers like Stripe and Square provide both.
Can I accept credit cards without a website?
Yes. You can use a card reader (like Square Reader) to accept payments in person, send payment links via email or text, or process payments over the phone. You don't need a website at all. The payment processor handles the security and compliance regardless of how the customer pays.
How long does it take to get approved to accept credit cards?
Most providers approve you within 24 to 48 hours of verifying your identity and bank account. Some approve you when ready. You can start processing test transactions when ready, but you won't be able to accept real payments until your account is verified. A few providers take longer if they need additional information about your business.
What happens if a customer's card is declined?
The processor tells you the card was declined and gives you a reason code—insufficient funds, expired card, incorrect CVV, or a fraud block from the card issuer. You can ask the customer to try a different card or contact their bank. The declined transaction is not charged to the customer and does not appear on their statement.
Do I need a separate merchant account, or does the processor provide one?
All-in-one processors like Stripe and Square provide a merchant account as part of their service. You don't need to open a separate account with a bank. Money deposits directly into your existing business bank account. If you assemble your own payment stack, you'll need to open a merchant account with a bank or a third-party provider, which takes longer and costs more.