Payment integration services handle the technical work of accepting payments so you don't have to build it yourself

A payment integration service (also called a payment processor or payment gateway) sits between your business, your customers, and the banks. When a customer enters their card number or chooses a payment method on your website or app, the integration service encrypts that data, sends it to the card network and the customer's bank, and tells you whether the payment went through. You don't store the card number yourself, and you don't have to write the code that talks to Visa, Mastercard, or ACH networks.

The question isn't whether you need one — if you take payments online or through an app, you do. The real question is which one fits your business size, transaction volume, and technical skill. A freelancer taking invoices through PayPal has different needs than a retail chain processing thousands of transactions daily.

Key Takeaways

  • Payment integration services are required by law if you accept card payments; you cannot legally store raw card data yourself.
  • Costs vary by service: some charge a flat monthly fee, others take a percentage of each transaction, and most charge both.
  • Hosted solutions (like Stripe or Square) require less technical work than self-hosted gateways, but give you less control over the checkout experience.
  • Your choice depends on transaction volume, whether you need invoicing or recurring billing, and whether you have a developer on staff.
  • Switching services later is possible but involves updating your code and testing, so choosing one that scales with your business saves work.

What payment integration services actually do

When you use a payment integration service, you're outsourcing three things: data security, compliance, and the technical connection to payment networks. The service encrypts the customer's payment information before it leaves their browser, handles the PCI compliance paperwork (the security standard that card networks require), and maintains the live connection to Visa, Mastercard, ACH, and other networks.

Without a service, you would have to become PCI-compliant yourself, which means hiring security auditors, maintaining encrypted servers, and proving to card networks that you're storing and handling card data safely. That costs thousands of dollars a year and requires ongoing technical expertise. A payment integration service absorbs that cost and spreads it across thousands of businesses, so you pay a smaller per-transaction fee instead.

The service also handles disputes and chargebacks — when a customer claims they didn't authorize a charge or didn't receive what they paid for. The service documents the transaction, communicates with the customer's bank, and either refunds the customer or defends the charge on your behalf.

Hosted checkout versus self-hosted integration

Payment integration services come in two main shapes. A hosted checkout redirects the customer to a payment page that the service controls — you never see their card number, and your code doesn't touch the payment form. Stripe Checkout, Square Online, and PayPal are examples. A self-hosted integration lets you build the payment form into your own website or app, but the service's code handles the encryption before the data leaves the customer's browser.

Hosted checkouts are simpler to set up and require almost no coding. You add a button to your website, the customer clicks it, and they land on a page that looks like it belongs to the service. The downside is that you can't customize the look and feel much, and the customer leaves your website to pay. Self-hosted integrations (like Stripe Elements or Square Web Payments SDK) let you keep the customer on your site and design the payment form to match your brand, but they require a developer to write the code and test it.

For most small businesses, a hosted checkout is faster to launch. For larger businesses or those with specific design needs, self-hosted integration is worth the extra work.

How costs break down across different services

Payment integration services charge in three ways: a percentage of each transaction, a flat fee per transaction, and sometimes a monthly subscription. The percentage typically ranges from 2% to 3.5% of the transaction amount, and the flat fee is usually $0.20 to $0.50 per transaction. Some services waive the monthly fee if your volume is low; others charge $20 to $300 per month regardless.

A service that charges 2.9% + $0.30 per transaction costs you $3.59 on a $100 sale. A service that charges a flat $0.25 per transaction costs $0.25 on the same sale. Which is cheaper depends on your average transaction size. High-volume, low-dollar businesses (like a coffee shop) benefit from flat-fee services. Businesses with large, infrequent transactions (like a consulting firm) benefit from percentage-based pricing.

International payments, recurring billing, and invoice sending often cost extra. If you need those features, compare the total cost across services, not just the per-transaction rate. Some services bundle invoicing and recurring billing into their base price; others charge separately.

When you need more than a basic payment processor

A basic payment integration service processes one-time payments. If your business needs invoicing, recurring billing, or the ability to refund customers without manual work, you need a service that offers those features built in or through integrations.

Invoicing services like FreshBooks or Wave let you send an invoice to a customer, and they can pay it directly from the email without logging into your website. Recurring billing services like Recurly or Zuora handle subscription payments automatically — they charge the customer on a schedule and retry failed payments. Some services (Stripe, Square) offer both as add-ons to their base payment processing.

If you sell through multiple channels — your website, a mobile app, and a physical store — you need a service that works across all three. Stripe and Square both do this. If you only sell on your website, a simpler service may be cheaper.

Switching services later and avoiding lock-in

You can switch payment integration services, but it requires work. You'll need to update the code on your website or app to point to the new service's API, test the new integration to make sure payments go through, and migrate any stored customer payment information (if the old service stored it). For businesses with a developer on staff, this takes a few days. For businesses without technical help, it can take weeks or cost thousands in consulting fees.

To avoid being stuck with a service that no longer fits your needs, choose one that's widely used and well-documented. Stripe and Square have the most tutorials and developer support, so switching away from them (or to them) is easier than switching to or from a niche service. Also check whether the service lets you export transaction history and customer data — some do, some don't.

If you're just starting out, don't worry too much about lock-in. Pick a service that's cheap and easy to set up now, and plan to switch in a year or two if your needs change. The switching cost is usually less than the savings from moving to a service that fits your volume better.

Red flags and what to avoid

Avoid services that promise to store your customers' card numbers for you without PCI compliance. If a service says "we'll keep your card data safe," ask them to show you their PCI compliance certificate. Legitimate services either don't store raw card data at all (they use tokenization, which stores a reference instead) or they're audited by a third party every year.

Avoid services with no clear pricing. If the website doesn't list the per-transaction fee or monthly cost, contact them and ask. Services that hide pricing often have surprise fees or charge more than competitors.

Avoid services with no dispute or chargeback protection. Every payment service will eventually face a chargeback — a customer claiming they didn't authorize a charge. The service should document the transaction, help you respond to the chargeback, and not automatically refund the customer without investigating. Read the terms of service or ask their support team how they handle disputes.

Frequently Asked Questions

Do I need a payment integration service if I only take payments in person?

No. If you only accept cash or checks, you don't need one. If you accept cards in person, you need a point-of-sale system (like Square or Toast), which includes payment processing. If you accept payments both in person and online, you need a service that handles both — most modern services do.

What happens if a customer disputes a charge?

The payment service notifies you of the dispute and gives you a window (usually 7 to 10 days) to respond with proof that the customer authorized the charge and received what they paid for. Proof can be an email confirmation, a shipping receipt, or a signed contract. If you respond with proof, the service defends the charge. If you don't respond or your proof is weak, the service refunds the customer and may charge you a dispute fee ($15 to $100).

Can I use multiple payment services at once?

Yes. Some businesses use one service for online payments and another for in-person payments, or one for subscriptions and another for one-time purchases. This adds complexity — you'll have multiple dashboards to check and multiple sets of fees to track — but it can be cheaper if different services excel at different things. Most businesses start with one service and add another only if the first one doesn't meet a specific need.

What's the difference between a payment gateway and a payment processor?

A payment gateway is the software that encrypts the customer's payment information and sends it to the payment networks. A payment processor is the company that receives that information and talks to the banks. Most services you'll encounter (Stripe, Square, PayPal) are both — they provide the gateway and process the payment. The distinction matters mainly if you're building a very large system and need to separate these functions.

Do I need a merchant account to use a payment integration service?

Not always. A merchant account is a bank account that receives card payments. Some payment services (Stripe, Square) set up a merchant account for you automatically. Others (like Authorize.net) require you to open one separately with a bank. Check the service's requirements before signing up — if they require a separate merchant account and your bank charges for it, factor that into your cost comparison.