Payment Processor

Billing Payments

5 min read

Also known as: Payment Gateway, Merchant Processor, Card Processor

A payment processor is the service that moves card and ACH transactions between your customer, their bank, and your merchant account.

Definition

A payment processor is the technical middleman that handles the actual movement of money when a customer pays you. It authorizes the card or bank transaction, routes it through the card networks and issuing banks, and settles the funds into your account — usually within one to three business days.

In practice, your billing system hands off card details (or a tokenized version) to the processor, which returns an approval or decline in seconds. The processor also handles refunds, chargebacks, recurring charge attempts, and the compliance scaffolding around PCI data handling.

Payment processors are often confused with payment gateways and merchant accounts. The gateway is the front-door interface that captures card data, the merchant account is the bank account that holds funds before payout, and the processor is the engine routing the transaction between all parties — though many modern vendors bundle all three under one contract.

Why It Matters

Your processor choice directly affects revenue. Authorization rates, supported payment methods, retry logic for failed recurring charges, and dispute-handling tools all live at the processor layer — a one or two percent swing in approval rates can be the difference between hitting plan and missing it. Fee structures also vary widely, and a processor optimized for high-ticket B2B invoicing looks nothing like one tuned for low-ticket e-commerce.

Teams that pick a processor on price alone usually pay later in operational pain. Common failures include weak international card support that silently declines foreign buyers, no native ACH for invoice payments, slow dispute interfaces that cause you to miss chargeback deadlines, and rigid APIs that make subscription changes (proration, pauses, plan swaps) a manual exercise for your billing team.

Examples in Practice

A 40-person SaaS company processing monthly subscriptions notices involuntary churn climbing because expired cards are silently failing. Switching to a processor with account updater services and smart retry logic recovers roughly 30 percent of failed renewals without any human intervention.

A managed-services firm sending five-figure invoices to enterprise clients adds ACH and wire support through their processor. Card fees on a $25,000 invoice were eating thousands per transaction, while ACH costs a flat fee — the switch pays for itself within the first month.

A direct-to-consumer brand expanding into Europe finds their U.S.-centric processor declines a high share of EU cards. Moving to a processor with local acquiring in target markets lifts approval rates by double digits and unlocks region-specific methods like SEPA and iDEAL.

Frequently Asked Questions

What is a payment processor and why does it matter?

A payment processor is the service that authorizes and settles transactions between your customer's bank and yours. It matters because it controls your authorization rate, payout timing, supported payment methods, and fee structure — all of which directly hit revenue. A poorly matched processor can quietly leak five to ten percent of your top line through declines and avoidable fees.

How is a payment processor different from a payment gateway?

The gateway is the front-end layer that captures and tokenizes card data, often embedded in your checkout or invoice. The processor is the back-end that routes the authorized transaction through the card networks to the issuing bank and settles funds. Most modern vendors bundle both, so operators rarely have to choose them separately — but the distinction matters when troubleshooting failed transactions.

When should I switch payment processors?

Consider switching when authorization rates drop below industry benchmarks, when you expand into new geographies your current processor handles poorly, when fees scale faster than revenue, or when your billing model outgrows what the processor supports. Subscription businesses especially should evaluate annually as recurring-payment features evolve quickly.

What metrics measure payment processor performance?

Track authorization rate (approved transactions divided by attempts), involuntary churn from failed renewals, average time to settlement, chargeback rate, dispute win rate, and effective fee percentage (total fees divided by gross volume). For subscription businesses, also monitor recovery rate from retry logic and account updater services.

What's the typical cost of a payment processor?

Card processing typically runs 2.5 to 3.5 percent plus a fixed per-transaction fee for card-not-present transactions, with interchange-plus pricing available for higher-volume merchants at roughly interchange plus 0.3 to 0.8 percent. ACH transactions usually cost a flat fee under a dollar or a small percentage capped at a few dollars. International cards, premium rewards cards, and disputes carry additional fees.

What tools handle payment processing?

The category includes full-stack processors that bundle gateway, merchant account, and processing in one contract, traditional acquiring banks paired with separate gateways, and specialized subscription billing platforms that sit on top of one or more processors. Subscription billing engines layered over a processor give you proration, dunning, and revenue recognition that raw processors don't provide.

How do I implement a payment processor for a small team?

Start by mapping your payment methods (cards, ACH, wires, local methods), your billing model (one-time, recurring, usage-based), and your geographic footprint. Choose a processor that natively supports all three rather than bolting them on. Have your billing platform vendor handle the integration end-to-end so your team isn't writing webhook handlers or managing PCI scope directly.

What's the biggest mistake teams make with payment processors?

Picking on headline fee percentage alone. The cheapest sticker price often comes with weak recurring-payment tooling, poor international approval rates, and clunky dispute handling — costs that show up later as churn and chargebacks rather than line items on a statement. Evaluate total cost of ownership including involuntary churn and operational overhead, not just the processing percentage.

Can I use multiple payment processors at once?

Yes, and many growing companies do. Common patterns include using one processor for domestic cards, another for international acquiring, and a separate ACH provider for high-ticket invoices. A capable billing platform routes transactions to the right processor based on currency, region, or payment method, which can lift overall approval rates meaningfully.

What is PCI compliance and how does it relate to processors?

PCI DSS is the security standard for handling cardholder data. Your processor handles most of the compliance burden when you use their hosted fields or tokenized checkout, keeping raw card data off your servers. If your team ever touches unencrypted card numbers, your PCI scope expands dramatically and the audit costs follow — so a processor that minimizes your scope is worth real money.

The AMW Suite