A payment processor is the entity that moves money between a customer's bank and a merchant's account during a transaction. It routes the transaction through the card network to the customer's issuing bank, receives an approval or denial, and transfers the funds once the payment is authorized.
A payment processor is easy to confuse with a payment gateway, since the two terms often get used interchangeably even though they do different jobs. A payment gateway tokenizes and encrypts a customer's payment details at checkout and returns a success or failure message. The payment processor does the underlying work with the banking system: it routes requests through the card network to the issuing bank, checks for available funds, and moves money from the customer's account to the merchant's account.
Both roles are required to accept an online payment. Some providers bundle gateway and processor functions into a single service, which simplifies setup. Others keep them separate, which can offer more flexibility but takes more technical integration work. Reliable communication between the two pieces matters, because a mismatch between gateway and processor is a common source of payment failures.
Why it matters
The payment processor a business uses affects how often legitimate transactions get approved, how quickly funds settle, and which countries, currencies, and payment methods it can support. For a subscription business running recurring charges, processor reliability feeds directly into involuntary churn: a processor with poor authorization rates on renewals can look like customers leaving when the real problem is payment infrastructure. Connecting to more than one processor, rather than being locked into a single one, gives a business room to route around those weak spots instead of absorbing the lost revenue.
How to work with a payment processor
A subscription business generally works with a payment processor through a few steps:
Choose a processor, or a gateway that bundles processor access, based on the currencies, countries, and payment methods you need to support.
Integrate it with your billing or checkout system so authorization, decline, and settlement events flow back into your records automatically.
Monitor authorization and decline rates over time, since processors and card networks periodically change requirements that can affect success rates.
Add a second processor or gateway relationship where it makes sense, so a single point of failure doesn't take down your ability to collect payments.
Benefits and examples
A subscription business billing customers in multiple countries might find that its primary processor authorizes card transactions well in one region but has lower success rates for a regional card brand used elsewhere. Recognizing that this is a processor-level issue, rather than assuming those customers simply have bad cards, lets the business route those transactions through a different processor or adjust its integration instead of losing the revenue.
Connecting to more than one gateway and processor is what makes that possible. Recurly connects to many gateways and processors rather than tying a merchant to a single one, including Stripe, Adyen, GoCardless, Cybersource, and FreedomPay. That gives merchants room to choose the combination that fits their geography, payment method mix, and existing banking relationships, and to add a second processor without rebuilding their billing integration from scratch.
Frequently asked questions
Is a payment processor the same as a payment gateway? No, though the terms are often used loosely. A gateway tokenizes and encrypts payment details at checkout. A processor handles the underlying transfer of funds between banks. Most businesses need both, sometimes bundled from one provider and sometimes as separate services.
Do I need more than one payment processor? Not necessarily, but many subscription businesses that operate across multiple countries or currencies use more than one, since authorization rates for specific card brands or regions can vary between processors.
Why did a legitimate customer's payment get declined? This can happen for reasons that have nothing to do with the customer, including how a specific processor evaluates a transaction, temporary issues at the issuing bank, or mismatched data between the gateway and processor. Reviewing decline patterns by processor can help separate a customer-side issue from an infrastructure one.
What should I look for when choosing a payment processor? Coverage for the countries, currencies, and payment methods your customers use, reliable authorization rates, and how well it integrates with your existing billing platform are the main considerations for most subscription businesses.
