The Basic Steps to Accept Card Payments

To accept credit card payments, you need three things: a way to process the card (a payment processor or merchant account), a way to collect the card details (a terminal, online form, or payment link), and a bank account where the money lands. The processor reads the card information, checks it with the card issuer, and deposits the funds into your account — usually within one to three business days.

The simplest route for a small business or freelancer is a payment processor like Square, Stripe, or PayPal. These companies handle the technical work and the relationship with the card networks. You do not need to apply for a separate merchant account; the processor provides one as part of their service. You pay a fee per transaction — typically 2.2% to 3% of the amount plus a small flat fee — and the processor handles the rest.

If you process a high volume of payments or want lower fees, you can apply for a merchant account directly from a bank or payment processor. This route requires more paperwork and a longer approval process, but the per-transaction fees are lower. Most small businesses find a payment processor more practical because the setup is faster and the fees are transparent.

Key Takeaways

  • Payment processors like Square and Stripe let you accept cards immediately with minimal setup; you pay per transaction and the funds arrive in your bank account in one to three business days.
  • You can accept cards in person using a card reader plugged into your phone or tablet, online through a payment form or checkout page, or by phone if the customer reads you their card details.
  • The card issuer (the customer's bank) approves or declines the transaction in seconds; if declined, the processor tells you why and you can ask the customer for a different card.
  • Fees vary by processor and payment method — in-person card-present transactions usually cost less than online or phone payments because fraud risk is lower.
  • You are responsible for keeping card details secure; most processors handle this for you, but you must never store full card numbers yourself or transmit them unencrypted.

In-Person Payment Methods

If you take payments face-to-face, you have two main options: a card reader that plugs into your phone or tablet, or a physical terminal that sits on your counter. Card readers are cheaper and more portable — Square Reader, PayPal Here, and Stripe Terminal are common examples. The customer inserts, taps, or swipes their card; the reader encrypts the data and sends it to the processor; and the transaction completes in seconds. You pay a small fee per transaction, usually 2.5% plus $0.15 or similar.

A physical terminal is a dedicated machine that looks like what you see at a retail checkout. It costs more upfront (typically $200 to $500) but can process more transactions per day and does not depend on your phone's internet connection. Terminals are common in restaurants, salons, and retail shops. You still work with a payment processor; the terminal just handles the card reading and encryption for you.

Both methods are card-present transactions, which means the card is physically in front of you. Card-present transactions have lower fraud risk, so processors charge lower fees than they do for online or phone payments. If a transaction is declined, the terminal or reader tells you immediately, and you can ask the customer for a different card or payment method.

Online and Phone Payment Methods

For online payments, you embed a payment form on your website or send customers a payment link they can click. The form or link is hosted by your processor, so the customer's card details never touch your server. Popular options include Stripe Checkout, Square Online, and PayPal's payment buttons. The customer enters their card information, the processor verifies it, and the money goes into your account. Fees are typically 2.9% plus $0.30 per transaction for online card payments.

For phone payments, you read the card details to the customer over the phone, or they read them to you. You then enter the details into your processor's system manually. This is called a card-not-present transaction and carries higher fraud risk, so processors charge higher fees — often 3.5% or more. You should never write down or store card details; always enter them directly into the processor's secure form, which encrypts them immediately.

Some processors offer invoicing as an alternative: you send the customer an invoice with a payment link, and they click it to pay. This is useful for service businesses and freelancers because the customer can pay on their own time, and you do not have to handle their card details at all. The processor still charges a transaction fee, but the process is simpler and safer for both of you.

How the Transaction Actually Works

When a customer swipes, taps, or enters their card, the processor sends the card details to the card network (Visa, Mastercard, American Express, or Discover). The network routes the request to the customer's bank, called the card issuer. The issuer checks whether the account exists, whether the card is active, whether the amount is within the customer's available balance or credit limit, and whether the transaction matches the customer's typical spending pattern.

The issuer approves or declines the transaction and sends the response back through the network to your processor. This whole process takes a few seconds. If approved, the processor shows you a confirmation and the transaction is complete. If declined, the processor tells you the reason — insufficient funds, card expired, incorrect PIN, suspected fraud, or a code specific to the issuer. You can then ask the customer for a different card or payment method.

The money does not appear in your bank account immediately. The processor batches your transactions — usually once per day — and sends them to your bank. Your bank then transfers the funds to your account, which typically takes one to three business days. Some processors offer next-day deposits for an extra fee, and a few offer same-day deposits for high-volume merchants.

Fees and What They Cover

Every payment processor charges fees, and the amount depends on the payment method and your volume. Card-present transactions (in-person, with the physical card) usually cost 2.5% to 2.75% plus a flat fee like $0.15. Card-not-present transactions (online or phone) usually cost 2.9% to 3.5% plus $0.30. Some processors charge a monthly fee ($10 to $30) in addition to per-transaction fees, while others charge only per transaction.

The fee covers the processor's work, the card network's fee, and the card issuer's fee. You do not pay these separately; the processor bundles them into one fee and deducts it from each transaction. For example, if a customer pays $100 and your rate is 2.9% plus $0.30, the processor deducts $3.20 and deposits $96.80 into your account.

Some processors charge extra fees for specific situations: a fee if a transaction is declined, a fee if a customer disputes a charge (called a chargeback), a fee if you refund a transaction, or a fee if you do not process a minimum amount per month. Read the processor's fee schedule carefully before you sign up, because these extras can add up.

Security and PCI Compliance

You are responsible for keeping card information secure, but most of that responsibility falls on your processor. When you use a payment processor's form, terminal, or reader, the card details are encrypted immediately and you never see the full card number. The processor stores the encrypted data in a secure vault and handles all the security compliance for you.

You must never ask a customer to email you their card details, write down a full card number, or store card information in a spreadsheet or email. If you take phone payments, enter the details directly into your processor's secure form — never into a text document or your own system. If you store any card data yourself, you must comply with PCI DSS (Payment Card Industry Data Security Standard), which requires encryption, firewalls, regular security audits, and other expensive measures. Most small businesses avoid this by letting the processor handle all storage.

If a customer's card is compromised after you process a payment, the card issuer is responsible for protecting the customer, not you. Your processor's encryption and security practices protect both of you. If you ever suspect a security breach — for example, if you notice fraudulent transactions on your own account — contact your processor immediately.

Choosing a Payment Processor

The right processor depends on how you take payments. If you sell in person, look for one with a good card reader app — Square and PayPal are popular because their readers are cheap and reliable. If you sell online, look for one with an easy checkout experience and good integration with your website platform — Stripe is common for custom websites, while Shopify Payments works well if you use Shopify.

Compare the per-transaction fees, any monthly fees, deposit speed, and customer support. Most processors offer a free trial or a low-risk first month, so you can test them before committing. Read reviews from other small businesses in your industry, because experience varies depending on your business type and transaction volume.

You can use more than one processor if you need to. For example, you might use Square for in-person payments and Stripe for online payments. Each processor will deposit into your bank account separately, so you will see multiple deposits per day, but this gives you flexibility and lets you optimize fees for each payment method.

Frequently Asked Questions

What happens if a customer disputes a charge after I process it?

The customer contacts their bank and claims the charge was unauthorized or the product did not arrive. The bank investigates and either sides with the customer (a chargeback) or sides with you. If you lose, the processor reverses the transaction and charges you a chargeback fee, usually $15 to $25. Keep records of all orders, receipts, and shipping confirmations to defend yourself if a dispute happens.

Can I accept credit cards without a business bank account?

Most processors require a business bank account because they need somewhere to deposit the money. Some will accept a personal account if you are a sole proprietor, but this is less common. Open a business account before you set up a payment processor; it takes a few days and protects your personal finances from your business transactions.

What if a customer's card is declined?

The processor tells you the reason — insufficient funds, expired card, incorrect PIN, or a code from the issuer. You can ask the customer for a different card, a different payment method, or to contact their bank to find out why the card was declined. You cannot charge the card again without the customer's permission, even if you think the decline was a mistake.

Do I have to refund a customer if they change their mind?

That depends on your refund policy, not on the payment processor. The processor can process a refund if you ask them to, and the money goes back to the customer's card in one to three business days. You decide whether to offer refunds and under what conditions. The processor charges a small fee for the refund, usually the same per-transaction fee as the original charge.

Can I accept payments without a website?

Yes. You can use a payment link that your processor generates for you — you send the link to the customer by email or text, they click it, and they pay. You can also take in-person payments with a card reader on your phone. You do not need a website at all; a payment processor and a bank account are enough to start accepting cards.