What happens when you accept a one-time credit card payment

A one-time credit card payment means the customer gives you their card details once, you process that single transaction, and the relationship ends there. No recurring charges, no stored card on file, no future access to their account. The money moves from their bank to yours (or to a payment processor you use), and you keep a record of the transaction.

The actual mechanics depend on what tools you have. If you're a small business or freelancer, you might use a payment processor like Stripe, Square, or PayPal. If you run a larger operation, you might have a merchant account through your bank. Either way, the customer's card data gets encrypted, the processor checks with the card issuer that funds are available, and you get a confirmation within seconds to a few minutes.

One-time payments are simpler than recurring billing because there's no ongoing relationship to manage, no subscription to cancel, and no reason for the customer to dispute a charge months later. But you do need to handle the card details securely, which is where most small businesses run into trouble.

Key Takeaways

  • You need either a payment processor (Stripe, Square, PayPal) or a merchant account through your bank to legally accept credit cards.
  • The customer's card data must be encrypted in transit and at rest, which is why you should never store card numbers in email, spreadsheets, or unencrypted files.
  • Payment processors charge a fee per transaction, usually 2.2% to 3.5% of the amount plus a flat fee of 20 to 30 cents.
  • The customer's bank can dispute the charge for up to 120 days, so keep records of what was sold, when, and to whom.

Setting up a payment processor or merchant account

If you don't already accept cards, you have two main routes. A payment processor like Stripe, Square, or PayPal lets you start within hours. You sign up online, link a bank account, and you can begin accepting payments the same day. These services handle the encryption, fraud checks, and deposit to your bank. They charge a percentage of each transaction plus a small flat fee.

A merchant account through your bank is more formal and takes longer to set up—usually a few days to a week. Your bank runs a background check, reviews your business history, and may ask for financial statements. Once approved, you get a dedicated account for card payments and lower per-transaction fees if you process high volume. Most small businesses don't need this route unless they're processing thousands of dollars per month.

For a one-time payment, a payment processor is almost always the right choice. You don't need to commit to anything, you can process a single $50 transaction or a $5,000 one, and you only pay when money actually comes in.

How to collect the card details safely

Never ask the customer to email you their card number, expiration date, or security code. Never type it into a spreadsheet or text file. Never photograph it. These are the fastest ways to expose yourself to fraud liability and to violate payment card industry rules.

Instead, use one of these methods. If you use a payment processor, they provide a payment link or payment form that you send to the customer. The customer clicks the link, enters their card details on an encrypted page hosted by the processor, and the transaction completes. You never see the full card number. This is the safest route and the one most processors recommend.

If you need to collect the payment in person or over the phone, use a card reader (a small device that plugs into your phone or computer) or a phone-based payment system. Square, PayPal, and most processors offer these. The customer swipes, inserts, or taps their card, and the device encrypts the data before it leaves the reader. Again, you never handle the raw card number.

Some processors also offer invoicing tools where you create an invoice, send it to the customer, and they pay by clicking a button in the email. The payment form is hosted by the processor, so the card data stays encrypted throughout.

What fees you'll pay and when

Payment processors charge in two ways. First, a percentage of the transaction, usually between 2.2% and 3.5%. Second, a flat fee per transaction, typically 20 to 30 cents. So if a customer pays you $100, you might pay $2.90 to $3.50 in fees, and you receive $96.50 to $97.10 in your bank account.

Some processors charge differently. PayPal charges 2.2% plus 30 cents for online transfers. Stripe charges 2.7% plus 30 cents for card payments. Square charges 2.6% plus 30 cents. These rates vary slightly by processor and by whether the card is present (in person) or not present (online). Rates also change, so check your processor's current pricing page before you commit.

You pay the fee only when the transaction succeeds. If the customer's card is declined, you pay nothing. The fee comes out of the deposit to your bank account, so you see the net amount (after fees) hit your account, not the full transaction amount.

Some processors charge monthly minimums or monthly fees, but most don't for one-time payments. Read the fine print before you sign up.

Processing the payment and confirming it went through

Once the customer submits their card details through your payment link or form, the processor sends the request to the customer's bank. The bank checks whether the account has sufficient funds, whether the card is active, and whether the transaction matches the customer's usual spending patterns. This takes a few seconds to a minute.

You'll see a confirmation on your screen or in your processor's dashboard. The customer will also receive a confirmation email from the processor. At this point, the money is authorized but not yet in your bank account.

The actual deposit to your bank account happens on a schedule set by your processor. Most deposit within one to two business days. Some deposit the same day if the transaction happens early enough. A few hold funds for longer if they detect unusual activity or if you're a new account. Check your processor's deposit schedule when you sign up.

Keep the confirmation number or transaction ID for your records. If the customer later disputes the charge, you'll need to show proof that the transaction was authorized and that you delivered what was promised.

Protecting yourself from fraud and disputes

A chargeback is when a customer tells their bank the transaction was unauthorized or fraudulent, and the bank reverses the charge and pulls the money back from your account. You have the right to dispute the chargeback, but you have to prove the transaction was legitimate. This is why records matter.

For a one-time payment, keep these documents: the invoice or receipt showing what was sold, the date, the amount, and the customer's name. If the payment was for a service, keep records of when the service was delivered. If it was for goods, keep a shipping confirmation or delivery proof. If the customer signed a contract or agreement, keep that too.

You can also reduce fraud risk by asking for the customer's billing address and matching it to the address on file with their bank. Most payment processors do this automatically. If the address doesn't match, the processor will flag it, and you can decide whether to proceed.

For high-value transactions, consider asking for additional verification—a photo ID, a phone call to confirm the order, or a signature. This sounds paranoid for a $50 payment, but it's reasonable for a $5,000 one.

What to do if the payment fails

If the customer's card is declined, the processor will tell you why. Common reasons include insufficient funds, the card being expired, the card being reported lost or stolen, or the bank blocking the transaction because it looks suspicious. The processor usually gives you a specific decline code.

Ask the customer to try a different card, to contact their bank to ask why the transaction was blocked, or to use a different payment method altogether. You can also ask them to try again in a few minutes—sometimes banks temporarily block transactions and allow them on a retry.

If the customer's bank is blocking the transaction because it looks suspicious, the customer can call their bank and tell them to expect the charge. This is common for out-of-state or international transactions.

If the payment fails repeatedly, you have the option to ask the customer to pay by check, bank transfer, or another method. There's no rule that says you must accept credit cards.

Frequently Asked Questions

Can I ask the customer to pay me directly through their bank instead of using a card?

Yes. Bank transfers (ACH transfers in the US) are often cheaper for you because the fees are lower, usually 1% or a flat fee of a dollar or two. The downside is that the transfer takes a few business days, and the customer has to know your bank account number. For a one-time payment, a credit card is usually faster and easier for both of you.

What if I'm selling something digital, like a read or a course?

The process is the same. Use a payment link or form, collect the payment, and then send the customer a read link or account access. Keep a record of the transaction. Digital goods have higher chargeback rates, so be extra careful to document what you sold and when the customer received access.

Do I need to collect sales tax on the credit card payment?

That depends on your state and what you're selling. Sales tax rules are separate from payment processing. If you're required to collect sales tax, add it to the amount before you send the payment link to the customer. The processor will charge fees on the total amount including tax.

How long do I have to refund the customer if they ask?

That's up to you and your refund policy. There's no legal requirement to refund a credit card payment just because the customer asks. But if you do issue a refund, most processors can reverse the transaction within 90 days. After that, you have to issue a manual refund to the customer's card, which takes a few business days.

What if the customer's card is from another country?

Most payment processors accept international cards. You may pay a slightly higher fee for international transactions—sometimes an extra 1% to 2%. The customer's bank may also charge them a foreign transaction fee, but that's their responsibility, not yours. The process is the same: the customer enters their card details, the processor encrypts it, and the bank approves or declines the charge.