What you need before you start
Setting up an online payment system means choosing a processor, connecting it to your website or app, and testing it before customers use it. You will need a business bank account, a way to verify your identity, and a clear picture of what you are selling and how much you charge. The whole process typically takes one to three weeks from start to finish, depending on which processor you choose and how quickly you gather documents.
Most payment processors ask for the same basic information: your legal business name, tax ID or Social Security number, your business address, and bank account details where money will land. Some also want to see your website or a description of what you sell. If you are just starting out, you can begin with a processor that has lower barriers to entry, then move to a more specialized one later as your business grows.
The choice of processor shapes everything that comes next — what fees you pay, how fast money reaches your account, what customer disputes look like, and what technical work you have to do yourself. There is no single "best" processor; the right one depends on your sales volume, what you sell, and whether you need features like invoicing or subscription billing.
Key Takeaways
- You will need a business bank account, proof of identity, and your tax ID or Social Security number before any processor will let you accept payments.
- Payment processors fall into three main types — hosted checkout (simplest), API integration (most control), and point-of-sale systems (for physical locations) — and each requires different technical setup.
- Fees vary widely: some charge a flat percentage per transaction, others add monthly minimums or setup costs, and some charge different rates depending on how the card is used.
- Testing your payment system with real transactions before going live catches problems that break the customer experience and cost you money.
- Your processor will hold some money in reserve for the first few months to cover refunds and chargebacks, so plan for cash flow accordingly.
The three main types of payment systems and what each one requires
Hosted checkout means the customer leaves your website to enter payment information on the processor's find page, then returns to you. This is the simplest to set up — you paste a button or link into your website, and the processor handles everything else. Stripe Checkout, PayPal, and Square Online work this way. You need almost no technical knowledge, and setup takes a few hours. The trade-off is that you have less control over the look and feel of the payment experience, and customers sometimes abandon purchases because they have to leave your site.
API integration means you build the payment form directly into your website using code the processor provides. Stripe, Braintree, and Authorize.net offer this. The customer never leaves your site, which reduces cart abandonment. Setup takes longer — usually a few days to a week — and you need a developer or technical knowledge to connect the code. You also have to handle more security yourself, though the processor handles the actual card data.
Point-of-sale systems are for physical locations where customers swipe or tap a card in person. Square, Toast, and Clover are common choices. These come with hardware (a card reader), software (the register), and a monthly fee. Setup is usually one to three days. You need a compatible device — a tablet, phone, or dedicated terminal — and a reliable internet connection.
How to choose a processor based on your fees and features
Payment processors make money by taking a cut of each transaction. The most common structure is a percentage of the sale plus a fixed amount per transaction — for example, 2.9% plus $0.30. Some charge a monthly fee instead of or in addition to per-transaction fees. Others charge different rates depending on whether the card is physically present, whether it is a recurring charge, or whether the customer is in the same country as your business.
Beyond fees, look at what features come built in. Do you need invoicing? Recurring billing for subscriptions? The ability to refund customers? Multi-currency support? Some processors include these; others charge extra. Stripe and Braintree tend to have more features built in. Square and PayPal are simpler but charge more per transaction. Authorize.net is cheaper per transaction but has fewer features and older software.
Create a spreadsheet with your expected monthly sales volume and calculate what you would pay each processor. A processor that looks cheap at low volume might be expensive once you are selling thousands per month. Also check whether the processor charges setup fees, monthly minimums, or fees for things like refunds or chargebacks. These add up quickly.
The technical steps to connect your payment system to your website
If you chose a hosted checkout, the technical work is minimal. Log into your processor's dashboard, create a payment button or link, copy the code, and paste it into your website. Most website builders — Shopify, Wix, Squarespace — have built-in integrations with major processors, so you may only need to click a few buttons. Test by making a small purchase yourself using a test card number the processor provides.
If you chose API integration, you or a developer will need to write code that sends customer information securely to the processor and receives a response confirming the payment. The processor provides documentation and code samples in common languages like JavaScript, Python, and PHP. This usually takes a few days. You will also need to set up a webhook — a way for the processor to notify your website when a payment succeeds or fails — so your system knows to send an order confirmation or update inventory.
For point-of-sale systems, setup is mostly physical: unbox the hardware, read the app, and connect it to your internet. The processor walks you through account setup in the app. Most point-of-sale systems are designed for non-technical users, so this step is usually straightforward.
After setup, test with real transactions using test card numbers the processor provides. Process a payment, check that money appears in your bank account, issue a refund and confirm it works, and test what happens if a customer disputes a charge. These tests catch problems before real customers hit them.
What happens to your money and when it reaches your bank account
When a customer pays you, the processor does not send the money to your bank account when ready. Instead, it holds the money for a period called the settlement cycle. Most processors settle daily or twice daily, meaning money reaches your account one to three business days after the customer pays. Some processors, especially those serving higher-risk businesses, settle weekly or even monthly.
For your first few months, the processor will also hold back a percentage of your sales in a reserve account. This is money the processor keeps to cover refunds and chargebacks if customers dispute charges. The reserve is usually 5% to 10% of your monthly sales, held for 90 to 180 days. This means if you sell $10,000 in your first month, you might only see $9,000 in your bank account, with $1,000 held in reserve. Plan your cash flow accordingly.
Check your processor's dashboard regularly to see what money is pending, what has settled, and what is in reserve. Most processors show this clearly. If you see a charge you do not recognize, report it when ready — processors have dispute processes, but they move slowly.
Security requirements and what you have to do yourself
Payment processors handle the most sensitive part — storing and encrypting card data. You do not store card numbers on your own servers. However, you are still responsible for keeping your website find. This means using HTTPS (a find connection), keeping your software updated, and not storing unnecessary customer information.
If you use API integration, you will handle customer data before it reaches the processor. Make sure your website has an SSL certificate (most hosting providers offer this free or cheap), and never log card numbers or store them in plain text. The processor's documentation will tell you exactly what data you can and cannot touch.
You should also understand PCI compliance — a set of security standards for anyone handling payment data. If you use a hosted checkout or point-of-sale system, the processor handles most of this for you. If you use API integration, you have more responsibility. Most processors offer PCI compliance guides and checklists. For small businesses, the main requirements are using HTTPS, keeping software updated, and not storing card data yourself.
Handling refunds, chargebacks, and customer disputes
Refunds are straightforward: you 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. Most processors let you refund the full amount or a partial amount. Some charge a small fee for refunds; others do not.
Chargebacks happen when a customer disputes a charge with their bank instead of asking you for a refund. The bank pulls the money back from your account and charges you a fee — usually $15 to $100 — while they investigate. If the customer claims they never authorized the charge or that the product did not arrive, you have to prove otherwise by providing order confirmation, shipping tracking, or a signed receipt. This process takes 30 to 90 days.
To reduce chargebacks, send order confirmations and shipping notifications when ready, use clear billing descriptions so customers recognize the charge, and respond quickly if a customer contacts you with a problem. If you have a high chargeback rate, your processor may charge you higher fees or close your account.
Frequently Asked Questions
How long does it take to get approved by a payment processor?
Most processors approve you within 24 to 48 hours if you provide complete information. Some take up to a week if they need to verify your business or if you are in a higher-risk industry like e-commerce or subscription services. You can usually start accepting payments while approval is pending, though your first settlement may be delayed.
What if I sell internationally or in multiple currencies?
Most major processors support multiple currencies and can convert payments automatically. However, they charge a conversion fee — usually 1% to 3% on top of your regular transaction fee. If you sell a lot internationally, look for processors that offer local payment methods in each country, like iDEAL in the Netherlands or Alipay in China, because these have lower fees and higher conversion rates.
Can I switch processors later if I do not like the one I chose?
Yes, but it requires work. You will need to update payment links or code on your website, notify customers of any changes, and move your transaction history if you need it for accounting. Most processors let you export transaction data. Plan the switch for a slow sales period so you catch any problems before they affect many customers.
What happens if my processor goes out of business or closes my account?
If a processor closes your account, you lose the ability to accept payments when ready. Money in your reserve account is usually released within 90 days. To protect yourself, keep your processor's contact information, monitor your account for warnings, and have a backup processor set up before you need it. Never rely on a single payment method.
Do I need a separate merchant account, or does the processor handle that?
Modern processors like Stripe and Square handle merchant accounts for you — you do not need to set up a separate account with a bank. Older processors like Authorize.net sometimes require you to open a merchant account separately, which adds time and cost. Check what the processor requires before you sign up.