Front-End vs Back-End Processor

Also called front end processor, back end processor, authorization platform, settlement platform

The front end authorizes your transaction in two seconds. The back end settles it, funds you, and produces your statement.

What it is

Payment processing splits into two jobs handled by two different systems, often owned by different companies. The front-end processor handles authorization: it takes the transaction from your terminal or gateway, routes it to the network and the issuer, and returns approve or decline, usually in about two seconds. Speed and uptime are its whole job. The back-end processor handles everything after: clearing, settlement, funding your bank account, interchange qualification, chargeback handling, fee calculation and the monthly statement. This is where your money actually moves and where your pricing is actually applied. It is also where problems live — a deposit that didn't arrive, a downgraded interchange category, an unexplained fee. Historically, front-end platform names like Nashville, Omaha, Buypass and North's EPX indicated which system your account ran on and determined which terminals and gateways could connect to you. That matters less than it used to but hasn't disappeared: platform compatibility is still why some hardware can't be reprogrammed to a new processor and why some POS integrations are available on one platform and not another.

Why it matters to your business

When something goes wrong, knowing which half is broken saves you an afternoon. Declines and slowness are front-end problems. Missing deposits, weird fees and bad interchange qualification are back-end problems. Say which one you have when you call and the conversation gets shorter. When you're evaluating a switch, the front-end platform determines whether your hardware moves with you. Ask before you buy equipment, not after — the answer determines whether your terminals are assets or anchors.

Where it gets contested

The split is invisible to merchants and that invisibility is convenient for whoever is at fault. When authorization is slow or failing, the front end is the problem. When funding is late or interchange qualified badly, the back end is. Merchants calling support are routinely bounced between them, and the sales office that sold the account frequently has visibility into neither. The more consequential issue is platform lock. Terminals are programmed to a specific front-end platform, and moving to a different processor often means new hardware or a reprogramming process that some providers will not perform on equipment they didn't sell. That converts a $400 terminal into a switching cost. It's rarely explained at sale. The defense is that the split exists for good engineering reasons — authorization needs sub-second reliability, settlement needs accuracy and auditability, and those are genuinely different systems with different requirements. It also enables competition: a gateway can route to many front ends, which is precisely what makes an independent gateway portable.

How to check it yourself

Ask your provider which front-end platform your account runs on and whether your current terminals can be reprogrammed to another processor or would need replacement. Get it in writing before you buy any hardware outright.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.

North owns EPX, its own back-end processing platform, alongside PayTrace and Payanywhere
partners.north.com ↗
An independent gateway connecting to 150+ processors lets a merchant change processors without re-integrating the checkout
nmi.com ↗