Yes, you can take payment from a credit card — but you need a processor and a way to collect the card details safely

If you're a business, freelancer, or anyone collecting money from others, you can accept credit cards. You'll need three things: a payment processor (the company that handles the transaction), a merchant account (the bank account where money lands), and a way to collect card details without storing them yourself. The processor handles the security, the bank handles the deposit, and you handle the customer relationship.

The card details never touch your computer or phone directly — they go encrypted to the processor, which charges you a fee (usually 2 to 3 percent of the transaction plus a flat fee per sale). The money arrives in your bank account within one to three business days, minus the processor's cut.

Key Takeaways

  • You need a payment processor (like Square, Stripe, or PayPal) to accept credit cards legally and securely — you cannot store card numbers yourself.
  • Fees typically run 2 to 3 percent of the transaction amount plus 25 to 50 cents per sale, and vary by processor and card type.
  • Money from credit card sales deposits to your bank account in one to three business days, not instantly.
  • You are responsible for refunds if a customer disputes the charge or returns goods, and the processor will reverse the deposit if the dispute is lost.

Payment processors and how they work

A payment processor is a company that sits between you and the credit card networks (Visa, Mastercard, American Express, Discover). When a customer swipes, taps, or enters their card, the processor encrypts the data, sends it to the card issuer for approval, and tells you whether the charge went through. Popular processors include Square, Stripe, PayPal, Toast, and Clover — each has different fee structures and features.

The processor does not hold your money. It collects the card details, confirms the charge is real, and then sends the funds to your bank account. You choose which bank account receives the deposit when you sign up. The processor keeps its fee and passes the rest to you.

Some processors require you to rent or buy a physical card reader (a small device that plugs into your phone or tablet). Others let you type in card details manually or send a payment link to the customer. The method you choose depends on whether you're taking payments in person, online, or over the phone.

In-person, online, and phone payment methods

In-person payments use a card reader — a small device that connects to your phone or tablet via Bluetooth or headphone jack. The customer inserts, taps, or swipes their card into the reader. Square Reader and Stripe Terminal are common options. You see the charge go through on your screen, and the customer gets a receipt. The money deposits to your bank account the next business day or within two to three days, depending on the processor.

Online payments use a payment link or embedded form on your website. The customer enters their card details into a secure form hosted by the processor — not your website. You never see the full card number. Stripe, PayPal, and Shopify all offer this. The charge goes through instantly, and the customer sees a confirmation page.

Phone payments require you to enter the card details into the processor's system while the customer reads them to you. This is the least secure method because you handle the card number, but some processors allow it for established customers. You'll need to follow PCI compliance rules, which means using a certified system and never writing down or storing the number.

Fees and what they cover

Credit card processing fees vary by processor, card type, and how you collect the payment. A typical breakdown: 2.2 to 2.9 percent of the transaction amount, plus 30 cents per sale. American Express and Discover often cost more than Visa and Mastercard. Keyed-in (phone or manual) transactions cost more than swiped or tapped ones because they're riskier for fraud.

Some processors charge a monthly fee ($0 to $50) whether you process any sales or not. Others charge only per transaction. A few charge a percentage of deposits. Read the processor's pricing page carefully — the advertised rate often does not include all fees.

The fee comes out of the deposit before it hits your bank account. If a customer pays $100 and the fee is $2.95, you receive $97.05. You do not pay the fee separately.

Chargebacks and disputes when a customer contests the charge

A chargeback happens when a customer tells their credit card company the charge was wrong, fraudulent, or the product never arrived. The card issuer investigates and either sides with you or reverses the charge. If reversed, the processor takes the money back out of your account — even if you already spent it.

You can dispute a chargeback by providing evidence: a signed receipt, a shipping confirmation, an email from the customer confirming the purchase, or a refund you already issued. The processor gives you a window (usually 7 to 10 days) to submit proof. If the card issuer agrees with you, the money stays in your account. If not, it's gone.

Chargebacks are expensive. Most processors charge $15 to $100 per chargeback, on top of losing the sale amount. If you get too many chargebacks (usually more than 1 percent of your sales), the processor can close your account.

Refunds and how to handle them

If a customer returns goods or you need to refund a charge, you issue a refund through the processor's dashboard. The refund goes back to the customer's card, not to you. The processor reverses the original charge and the fee you paid on it — so if you charged $100 and paid $2.95 in fees, the refund is $100 and you get the $2.95 fee back.

Refunds take one to three business days to appear on the customer's statement, depending on their bank. Some banks hold refunds for up to five business days. You cannot refund more than the original charge amount, and you cannot refund to a different card or bank account — it always goes back to the card that was charged.

If a customer disputes a charge instead of asking for a refund, it becomes a chargeback and costs you more. Always offer a refund first if something went wrong.

Security and PCI compliance

You are not allowed to store credit card numbers, expiration dates, or security codes on your computer, phone, or paper. The payment processor stores them in an encrypted vault, and you never see the full number after the transaction is complete. This is required by PCI DSS (Payment Card Industry Data Security Standard), a set of rules all card processors follow.

If you use a certified processor with a card reader or payment form, you are already compliant — the processor handles the security. If you manually enter card details (phone payments), you must use a PCI-certified system and never write down or store the number. Violating PCI rules can result in fines from the card networks, even if no fraud happens.

Fraud protection varies by processor. Most cover you if a customer's card was stolen and used without permission — the processor eats the loss, not you. But if a customer claims they never received goods or the product was not as described, that's a chargeback, and you have to prove otherwise.

Choosing a processor for your situation

If you take payments in person (retail, food, services), Square or Clover work well — they're designed for small businesses and have low per-transaction fees. If you sell online, Stripe or Shopify Payments integrate with websites and shopping carts. If you're a freelancer or service provider taking occasional payments, PayPal or Square Cash work for phone or email invoices.

Compare processors on three things: the per-transaction fee, whether there's a monthly fee, and whether the features match your business (invoicing, recurring billing, reporting, integration with your other tools). Most offer a free trial or low-cost first month, so test one before committing.

Frequently Asked Questions

How long does it take for credit card money to show up in my bank account?

Most processors deposit funds within one to three business days. Some offer next-day deposits for an extra fee. Weekends and holidays extend the timeline. Check your processor's deposit schedule in the settings — it usually shows the exact day and time deposits hit your account.

What happens if a customer's card is declined?

The processor tells you the charge failed, and the customer is not charged. Common reasons: insufficient funds, expired card, fraud block from the bank, or a typo in the card number. Ask the customer to try a different card or contact their bank. You can retry the charge, but most processors limit retries to avoid annoying the customer.

Can I accept credit cards without a physical card reader?

Yes. You can send a payment link via email or text, embed a payment form on your website, or manually enter card details into the processor's system. Each method has different fees — links and forms are usually cheaper than manual entry. You do not need a physical reader unless you take payments in person.

What if I process a lot of transactions — do fees go down?

Some processors offer lower rates if you process more than a certain amount per month (often $10,000 or $50,000). Contact the processor's sales team to negotiate. Larger businesses sometimes get custom rates, but most small businesses pay the standard rate regardless of volume.

Am I responsible if a customer's card was stolen and used fraudulently?

No. The card issuer and processor handle fraud liability. You are not charged back for a stolen card used without permission. However, if a customer claims they never received goods or the product was defective, that's a chargeback, and you have to prove the sale was legitimate.