A payment service provider handles the money part so your website doesn't have to

A payment service provider (PSP) is a company that sits between your website and the banks, moving money from a customer's card or account into yours. When someone buys something on your site, the PSP collects their payment information, checks with their bank that the money is there, takes a small fee, and deposits the rest into your account. Without a PSP, you would have to build all of that yourself — talking to banks, storing card numbers (which creates serious legal problems), and handling the security.

The PSP handles the technical and legal work that most websites are not equipped to do. They keep your site from ever touching the actual card number. They follow the rules that banks and governments set for handling money. They deal with fraud, chargebacks, and the constant updates to security standards. You focus on your product; they focus on the money moving safely.

Key Takeaways

  • A payment service provider collects payment information from customers, verifies the money exists, and deposits it into your business account, taking a percentage fee in the process.
  • Using a PSP means your website never stores or sees the customer's full card number, which keeps you out of complicated legal and security requirements.
  • Different PSPs charge different fees, support different payment methods (cards, digital wallets, bank transfers), and work better for different types of businesses.
  • A PSP integrates into your website through code, so your developer needs to connect it during the build or redesign phase.
  • The PSP also handles disputes, refunds, and fraud detection, which would otherwise fall on you to manage manually.

How a payment service provider actually processes a transaction

The process happens in seconds but involves several steps. A customer enters their card number on your checkout page. That information goes to the PSP's find server, never touching your own servers. The PSP sends the card details to the customer's bank (the issuer) and asks: does this person have the money? The bank says yes or no. If yes, the PSP holds the money, takes its fee (usually 2 to 3 percent plus a small flat fee per transaction), and tells your website the payment went through. Within one to three business days, the remaining money lands in your business bank account.

If the customer disputes the charge later, the PSP handles the back-and-forth with the bank. If the payment fails, the PSP tells your website why — card expired, insufficient funds, fraud block — so you can show the customer a specific error message instead of a generic one. The PSP also watches for patterns that look like fraud: the same card used in five countries in one hour, or a card number that appears on a known stolen list. These checks happen automatically and invisibly to the customer.

Why your website needs a PSP instead of handling payments yourself

Storing card numbers on your own servers is legal only if you follow PCI DSS (Payment Card Industry Data Security Standard), a set of rules so strict that most small and medium businesses cannot meet them without spending tens of thousands of dollars on security infrastructure. You would need encrypted servers, regular security audits, restricted access, and constant monitoring. A single breach exposes you to lawsuits, fines from card companies, and criminal liability.

A PSP takes that liability off your hands. They are built to handle card data safely and are required by law to maintain PCI compliance. They also carry insurance for breaches. If your website gets hacked but the PSP never saw the card number, you are not the one liable. The PSP is. This is why even large companies with their own engineers use PSPs — the legal and financial risk of handling card data yourself is not worth it.

Beyond security, a PSP handles the relationships with banks and card networks (Visa, Mastercard, American Express). Those companies set rules about how payments work, what fees you can charge, and how disputes are resolved. A PSP knows those rules and updates their system when they change. You do not have to.

Different PSPs charge different fees and support different payment methods

PSPs make money by taking a percentage of each transaction. A typical fee is 2.9 percent plus $0.30 per transaction for credit and debit cards. Some PSPs charge a flat monthly fee instead of per-transaction fees, which makes sense if you process a high volume. Others charge different rates depending on the type of card (a debit card might be cheaper than an international credit card) or the type of business (nonprofits often get lower rates).

PSPs also differ in what payment methods they support. Most handle Visa, Mastercard, and American Express. Some also support digital wallets like Apple Pay and Google Pay, which are faster for customers and have lower fraud rates. Others support bank transfers, PayPal, or regional payment methods like iDEAL in the Netherlands or Alipay in China. If your customers are international, you need a PSP that supports the payment methods they use in their countries.

Common PSPs include Stripe, Square, PayPal, Adyen, and Authorize.net. Each has different pricing, different supported payment methods, and different features. Stripe is popular with software companies and startups because it has good documentation for developers. Square is common in retail because it started with physical card readers. PayPal is familiar to many customers. Choosing one depends on your business type, your customers' locations, and your budget.

How a PSP connects to your website

Your developer integrates the PSP into your website using code. The PSP provides an API (a set of instructions that lets your website talk to the PSP's servers) and usually a pre-built checkout form that you can drop into your site. The developer writes code that sends the customer's payment information to the PSP, waits for a response, and then either shows a success page or an error message.

This integration happens during the initial build of your website or during a redesign. It is not something you can add later without rebuilding the checkout process. If you are building a new site, choose your PSP before your developer starts coding. If you want to switch PSPs later, your developer will need to rewrite the payment code, which takes time and costs money.

Some PSPs also provide a dashboard where you can see all your transactions, refund customers, read reports, and manage your account settings. You log in to this dashboard to see how much money came in, which payments failed, and what disputes are pending. This is separate from your website itself — it is the PSP's own system for managing your account.

What happens when a payment fails or a customer disputes a charge

When a payment fails, the PSP tells your website why. The customer might see a message like "Your card was declined" or "This card has expired." Your website can then ask the customer to try a different card or payment method. The PSP logs the failed attempt so you can see later which customers had trouble and why.

When a customer disputes a charge — claiming they did not make the purchase or that the product never arrived — the PSP handles the dispute process with the bank. You upload evidence (an order confirmation, a shipping receipt, a message from the customer) to the PSP's dashboard. The PSP sends that evidence to the bank. The bank decides whether the customer or you is right. If you lose, the money goes back to the customer. If you win, you keep it. The PSP manages the timeline and the paperwork.

Refunds work the same way. If you decide to refund a customer, you log into the PSP's dashboard and click "refund." The PSP sends the money back to the customer's card or account. The refund usually takes one to five business days to appear on the customer's statement, depending on their bank.

Choosing a PSP for your specific business type

If you run an online store, you need a PSP that supports recurring charges (subscriptions) and integrates with shopping cart software like Shopify or WooCommerce. Stripe and Square both do this well. If you run a SaaS (software as a service) business where customers pay monthly, you need the same thing. If you run a nonprofit and accept donations, some PSPs offer lower fees for nonprofits — look at Stripe Nonprofit or PayPal Giving Fund.

If your customers are mostly in one country, any major PSP works. If they are spread across multiple countries, you need a PSP that supports multiple currencies and payment methods in those regions. Adyen and Stripe are strong internationally. If you process very high volumes (millions per month), you might negotiate custom pricing with your PSP or use a payment processor (a different type of company that works more directly with banks) instead.

Talk to your developer about which PSPs they have experience with. They may have a preference based on the code they know best. Ask your PSP about their fees, what payment methods they support in your customers' countries, and what their customer support looks like. Some PSPs have live chat support; others only have email. If something breaks on a Friday night, you want to know you can reach someone.

Frequently Asked Questions

Does using a PSP mean my customers' card numbers are safe?

Yes, safer than if you handled the payments yourself. The PSP never sends the full card number to your website, so even if your site gets hacked, the thief does not get card numbers. The PSP stores card data in encrypted form on servers that meet strict security standards. Your customers' information is safer with a PSP than with most businesses.

Can I use multiple PSPs on the same website?

Technically yes, but it is usually a bad idea. Each PSP integration adds code complexity and makes your checkout slower. Most businesses stick with one PSP. If you want to offer multiple payment methods, choose a PSP that supports them all rather than adding a second PSP.

What happens if my PSP goes out of business?

Your money in their account is protected by law — it does not disappear. You will need to switch to a new PSP, which means your developer will need to rewrite the payment code on your website. This takes time but is not a financial disaster. Choose a PSP that has been around for a few years and has a stable business model.

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

Most PSPs deposit money one to three business days after the customer's payment clears. Some offer faster payouts (next day) for a higher fee. Weekend and holiday deposits usually wait until the next business day. Check your PSP's payout schedule when you sign up.

Can customers save their card information for future purchases?

Yes, if your PSP supports it and you ask the customer's permission. The PSP stores a token (a code that represents the card) instead of the card number itself. Next time the customer buys, they do not have to re-enter their card — your website uses the token to charge them. This is common for subscription services and repeat purchases.