You made a thing. Somebody wants it. Now money has to move from their card to your bank account, and the thing has to land in their hands. That part scares a lot of beginners more than building the product did.
It shouldn't. Getting paid online is a solved problem. You don't have to understand banking. You just have to understand a handful of moving parts and set them up carefully.
By the end of this, you'll know what a payment processor does, what to look for on a checkout page, how to deliver a product after someone pays, how to write a refund policy you can live with, and what a chargeback is before one shows up and ruins your afternoon.
The short version
- A payment processor is the middleman that takes the customer's card and sends the money to you, minus a fee.
- Test the whole path yourself, from clicking "buy" to getting the product, before anyone else does.
- Write a fair refund policy, post it where buyers can see it, and then actually follow it.
What a payment processor actually does
A payment processor is a company that handles card payments for you. The customer types in their card number, the processor checks that the card is real and has the money, and then it moves that money into an account for you. Later it sends that money to your bank. That last step is called a payout.
You've seen these companies even if you didn't know the name for them. Stripe, PayPal and Square are well-known examples. Many website and store platforms have one built in, or let you connect one with a few clicks.
Why not take cards yourself? Handling card numbers directly comes with serious security rules, and you do not want that job. The processor carries that weight.
What you'll need to sign up
Expect a processor to ask for real information about you. That usually means your legal name, address, a bank account for payouts, and a tax ID such as a Social Security number or a business tax number. They ask because they're required to know who they're sending money to.
Use your real details. A processor that can't verify you can freeze your account, and frozen money is not a fun puzzle to solve.
Fees exist, they vary, and you should read them
Every processor charges something. Often it's a small percentage of each sale plus a small flat amount per transaction, but the exact setup changes from company to company and over time. Some charge extra for things like international cards, currency conversion, or faster payouts.
I'm not going to give you numbers, because they change and any number I give you will be wrong eventually. What I will tell you is where to look: the processor's pricing page, and the terms you agree to when you sign up.
Read the fee page before you set your price, not after your first sale.
Then do a little math: figure out roughly what lands in your bank after fees. That's your real income from the sale. Less exciting. Also true.
Checkout pages: the last door before the sale
A checkout page is the screen where the buyer enters payment details and clicks the final button. Most processors and store platforms give you one. You usually don't build it from scratch, which is a mercy.
A good checkout page is boring in the best way. It should clearly show:
- What they're buying, in plain words
- The total price, with nothing sneaky added at the last second
- A link to your refund policy
- How and when they'll get the product
- How to contact you if something goes wrong
Keep it short
Every extra box you ask someone to fill in is another chance for them to wander off and make a sandwich instead. Ask for what you need to deliver the product and send a receipt. Usually that's a name, an email address and payment details. You don't need their birthday.
Don't play games
No fake countdown timers. No "only 2 left" on a digital file that can't run out. No pre-checked boxes that quietly add things to the cart. Those tricks might squeeze out a sale today, but they burn trust, and trust is the whole business.
Delivering the thing after they pay
Taking the money is half the job. The other half is getting the product to the person who paid for it, quickly and without them having to chase you.
For digital products, most beginners use one of these:
- Automatic delivery from the platform. Many store tools email a download link or show it on a thank-you page right after payment. This is the easiest option.
- A thank-you page with the link. After checkout, the buyer is sent to a page with their download or access instructions.
- Manual delivery. You see the sale and email the file yourself. This works when sales are rare, but it means buyers wait on you. If you go this way, tell them how long it might take.
Whatever you pick, send a confirmation email that includes the receipt and the delivery details. People lose browser tabs. They don't usually lose email.
Writing a fair refund policy, and keeping it
A refund is when you send a buyer's money back. A refund policy is your written promise about when you'll do that.
You get to decide what's fair for your product, within whatever your processor, platform and local consumer rules require. Common approaches include:
- Refunds within a set window after purchase, no questions asked
- Refunds if the product doesn't work or isn't what was described
- No refunds on some items, stated clearly before purchase
Whatever you choose, write it in plain words. "If the file doesn't work or isn't what the page described, email me within [your window] and I'll refund you" is better than a paragraph of legal fog.
Then keep it
The policy only matters if you follow it. When someone asks for a refund that fits your policy, give it promptly and politely. Don't argue, don't guilt them, and don't make them jump through hoops you didn't mention up front.
A few people may take advantage. Treat that as a cost of doing business, not a reason to treat everyone like a suspect.
Chargebacks, explained without the panic
A chargeback is different from a refund. A refund is you sending money back. A chargeback is the buyer going to their bank or card company and saying "reverse this charge," and the bank pulling the money back, often before you've said a word.
Card companies allow this to protect people from fraud and from sellers who don't deliver. Sometimes it's a stolen card. Sometimes it's a buyer who doesn't recognize the charge. Occasionally it's someone trying to get something free.
Chargebacks often come with an extra fee from your processor, and too many of them can get your account reviewed or shut down. So you want to prevent them where you can.
How to keep them rare
- Make your business name on card statements recognizable, so buyers know who charged them. Most processors let you set this.
- Deliver quickly and send clear receipts.
- Make refunds easy. A buyer who can get a refund from you in one email has little reason to go to their bank.
- Answer messages fast. Silence makes people nervous.
If one happens anyway
Your processor will usually notify you and give you a chance to respond with evidence. That's where your records come in: the receipt, proof of delivery, the email thread, your posted refund policy. Respond calmly and stick to facts. You won't win every one. That's normal.
Keep receipts for everything
Every sale should leave a paper trail, even if the paper is digital. Your processor keeps a record of transactions, but don't rely on that alone. Download or export your sales records regularly and keep them somewhere you control.
Keep records of refunds and chargebacks too. Keep receipts for what you spend running the business. When tax time comes, or a buyer disputes something, or you just want to know whether this whole thing is working, records turn a guess into an answer.
For how long to keep them and what counts for taxes, check irs.gov or ask a tax professional. This article is general information, not tax or legal advice.
Do this next
Money moving is not magic. It's plumbing. Check for leaks before you turn on the water.
Veteran. Gen Xer. Thirty-plus years building things on the web. I write these so you can skip some of the expensive mistakes.