What you actually need to do to accept payments online

Setting up a payment gateway means connecting your website to a system that processes credit cards, bank transfers, or digital wallets. You do not build this yourself—you choose a provider, integrate their code into your site, and they handle the transaction security and fraud checks. The process takes anywhere from a few hours to a few days depending on which provider you pick and how fast they verify your business.

The core steps are: choose a payment processor, create an account with them, get your API keys or integration code, add that code to your website, test with fake transactions, then go live. The time between "I want to accept payments" and "customers can actually pay me" depends mostly on how long the processor takes to review your business—some take 24 hours, others take a week.

Key Takeaways

  • You choose a payment processor (Stripe, Square, PayPal, etc.), not build a gateway from scratch—they provide the technology and handle security.
  • The processor will ask for your business details, bank account information, and sometimes tax documents before you can go live.
  • You add their code to your website using either a plugin, a pre-built form, or custom integration depending on your platform.
  • Testing with fake card numbers in a sandbox environment is required before real transactions can process.
  • Fees vary by processor and transaction type—typically 2.2% to 3.5% per card transaction, plus a per-transaction fee of $0.30 to $0.50.

Choosing between hosted pages, embedded forms, and custom code

A hosted payment page means the customer leaves your site to pay on the processor's page, then returns. This is the simplest to set up—you just link to a URL—but some customers distrust the redirect. Stripe Checkout and PayPal Standard work this way.

An embedded form keeps the customer on your site while they enter card details. The form lives on your page but the processor handles the actual card data, so you never see the raw numbers. Stripe Elements, Square Payment Form, and most modern processors offer this. It requires a bit more code but looks more professional.

Custom API integration means your developer writes code that talks directly to the processor's system. This gives you the most control over the experience but requires the most technical work and the most security responsibility. Only use this if you have a developer on staff or budget for one.

For most small websites, an embedded form is the middle ground: looks good, takes a few hours to set up, and you do not have to manage raw card data yourself.

The account setup and verification process

When you sign up with a payment processor, they will ask for your business name, address, phone number, and the bank account where deposits should go. They will also ask what you sell and roughly how much you expect to process per month. Some processors ask for a tax ID or EIN; others ask for a copy of your business license or articles of incorporation.

The processor runs a background check and verifies your bank account by depositing two small amounts (usually under $1 each) that you have to confirm. This can take 1 to 5 business days. Until you confirm those deposits, you cannot process real transactions.

Some processors, especially those handling high-risk categories like gambling or adult content, may ask for additional documents or deny you outright. If you are rejected by one processor, another may accept you—Stripe and Square have different risk appetites, for example.

Once verified, you get access to a dashboard where you can see transactions, refunds, and payouts. You also get API keys or access tokens—long strings of characters that let your website talk to the processor. Keep these secret; if someone gets them, they can process charges on your account.

Adding the payment code to your website

If you use WordPress with WooCommerce, Shopify, or another e-commerce platform, most major processors have a plugin you can install with a few clicks. You paste your API key into the plugin settings, and payments start flowing through.

If you have a custom website built in HTML, PHP, JavaScript, or another language, your developer will need to use the processor's SDK (software development kit) or API documentation. The processor provides code examples in multiple languages. Your developer reads the documentation, adds the code to your checkout page, tests it, and deploys it.

The processor will give you a test API key separate from your live key. You use the test key to process fake transactions with test card numbers (like 4242 4242 4242 4242 for Stripe). This lets you confirm the integration works before real money moves. Never skip this step.

Once testing is done, you swap the test key for the live key, and real transactions start processing. The processor deposits the money into your bank account on a schedule—usually daily, sometimes weekly, depending on the processor and your agreement.

Security, compliance, and what you are responsible for

The processor handles the heavy security work: encryption, fraud detection, and PCI compliance (the standard that protects card data). You do not store raw credit card numbers on your server, and you do not have to become a security informed.

What you are responsible for: keeping your API keys secret, using HTTPS on your website (not HTTP), and not doing anything that looks like fraud yourself. If you process a transaction and the customer disputes it, the processor investigates. If the dispute is legitimate, the money comes back out of your account.

You should also have a clear refund policy on your website and honor refund requests promptly. Processors track refund rates and chargeback rates; if yours gets too high, they may suspend your account or raise your fees.

If you handle sensitive data beyond just payment (like health information or social security numbers), you have additional compliance obligations that go beyond payment processing. Consult a lawyer or compliance specialist if you are unsure.

Understanding fees and how money reaches your bank account

Most processors charge a percentage of each transaction plus a flat fee. A typical structure is 2.9% + $0.30 per card transaction. So a $100 sale costs you $3.20, and $96.80 lands in your account. Some processors charge differently for different card types (American Express costs more than Visa, for example) or for different transaction types (recurring charges may cost less than one-time charges).

ACH transfers (bank-to-bank payments) usually cost less—sometimes 1% + $0.25, sometimes a flat $1 per transaction. Digital wallets like Apple Pay and Google Pay usually cost the same as credit cards.

Processors also charge for refunds, chargebacks, and failed transactions. A refund might cost you $0.15 to $1.00 depending on the processor. A chargeback (when a customer disputes a charge with their bank) can cost $15 to $100 plus the refund itself.

Money does not hit your bank account when ready. Most processors hold funds for 1 to 2 business days before depositing them. Some hold longer if you are new or if transaction volume spikes. You can see pending deposits in your processor dashboard, but you cannot access the money until it actually arrives in your bank.

Common problems and how to fix them

Transactions are declining for no obvious reason: Check that your test mode is off and your live API key is in place. Confirm your bank account is verified. If the processor is declining specific card types (like international cards), check your processor settings—you may have accidentally blocked them.

Money is not showing up in your bank account: Confirm the bank account you registered is correct. Check your processor dashboard for pending payouts—they may be held for review if this is your first large transaction. Contact the processor's support if a payout is stuck for more than a few business days.

Customers are seeing error messages: Check that your SSL certificate is valid (your site should show a padlock in the browser). Confirm your API key is correct and not expired. Test with a fake card number in sandbox mode to see if the error is on your end or the processor's.

You are getting chargebacks or fraud: Review the disputed transactions in your processor dashboard. If the customer has a legitimate complaint, issue a refund. If it looks like fraud, provide evidence (like shipping confirmation or IP address logs) to the processor. Processors have fraud tools you can enable, like 3D find or AVS (address verification), that reduce fraud but may also decline legitimate transactions.

Frequently Asked Questions

Do I need a business license or LLC to set up a payment gateway?

Most processors do not require it, but some do depending on your industry and location. Sole proprietors can usually set up an account with just a social security number and bank account. If you operate as an LLC or corporation, the processor will ask for your EIN. Check with your specific processor before assuming you need legal paperwork.

What happens if a customer disputes a charge?

The processor investigates and either sides with you or the customer. If the customer wins, the money is refunded to them and deducted from your account. You can provide evidence like shipping confirmation or delivery proof. If chargebacks happen too often, the processor may raise your fees or close your account.

Can I use the same payment processor on multiple websites?

Yes. Most processors let you create multiple accounts or manage multiple websites from one account. Some charge per website; others do not. Check your processor's pricing and account structure before setting up multiple sites.

What if I want to accept payments in multiple currencies?

Most major processors support multiple currencies, but they charge a conversion fee (usually 1% to 3% on top of the transaction fee). Some processors handle the conversion automatically; others require you to set it up in your dashboard. Confirm your processor supports the currencies you need before signing up.

How long does it take to get paid after a customer makes a purchase?

The processor deposits money into your bank account on a schedule—usually daily or weekly. The deposit takes 1 to 2 business days to appear in your account after the processor sends it. So a purchase on Monday might not be in your bank until Wednesday or Thursday. New accounts sometimes have longer hold periods.