Payment Service Provider
What Is a Payment Service Provider (PSP)? Definition and How It Works
Definition
A Payment Service Provider (PSP) is a company that enables merchants to accept electronic payments, including credit cards, debit cards, digital wallets, and bank transfers, by providing the technology, acquiring connectivity, and processing infrastructure required to initiate, route, authorise, and settle transactions. PSPs sit between merchants and the broader payment ecosystem, abstracting the complexity of connecting to card networks, acquirers, and alternative payment methods.
How it works
A PSP bundles several payment functions into a single merchant-facing product. At minimum, a PSP provides a payment gateway, the technology that captures, encrypts, and transmits payment data, and acquiring connectivity, either through a direct acquiring licence or through relationships with acquiring banks. Many PSPs also provide fraud screening, tokenisation, dispute management, and reporting within the same platform.
When a merchant processes a transaction through a PSP, the flow is: the merchant's checkout sends payment data to the PSP; the PSP applies initial fraud checks and routes the authorisation request to the appropriate acquirer; the acquirer forwards the request to the card network; the network routes it to the issuing bank, which approves or declines; the response travels back through the chain to the merchant in milliseconds.
PSPs vary significantly in architecture. Some operate as both gateway and acquirer; others are pure gateways connecting to external acquirers; others are full-stack payment orchestration platforms managing multiple acquirers, payment methods, and intelligent routing. The term PSP is used broadly across all configurations.
Commercially, PSPs charge merchants through per-transaction fees, monthly platform fees, and interchange-plus or blended pricing models. Enterprise PSP contracts are negotiated on individual terms based on volume, mix, and geography.
Why it matters
The PSP relationship is the primary commercial and operational interface for most merchants accessing payment infrastructure. The PSP's authorisation rate performance, fraud detection accuracy, settlement timing, and fee structure directly affect merchant revenue, margin, and operational overhead. A 1% improvement in authorisation rates on a $100M annual card volume translates to $1M in recovered revenue.
Multi-PSP strategies are common among enterprise merchants, who route transactions across multiple PSPs and acquirers to optimise authorisation rates by card type, geography, and issuer, and to maintain redundancy. Payment orchestration platforms that manage multi-PSP routing have grown as a result.
Regulatory requirements shape PSP relationships. In the EU, PSPs are regulated entities under PSD2, payment institutions or electronic money institutions, subject to conduct of business rules, AML obligations, and consumer protection requirements. Merchants must ensure their PSP holds appropriate authorisations for operating markets.
With PXP
PXP is a full-stack payment service provider, combining gateway, direct acquiring, orchestration, and smart routing in one platform. Talk to our team about how PXP can support your payment acceptance and orchestration.
Frequently asked questions
What is the difference between a PSP and a payment gateway?
A payment gateway is the technology component that securely captures and transmits payment data between the merchant and the processing network. A PSP is a broader company providing payment acceptance services, typically including a gateway plus acquiring connectivity, fraud tooling, settlement services, and reporting. All PSPs include a gateway function, but not all gateways are full PSPs.
What is the difference between a PSP and an acquirer?
An acquirer is a licenced financial institution that holds merchant accounts and assumes financial liability for card transactions. A PSP provides the technology and operational layer on top of acquiring. Many PSPs have direct acquiring licences; others operate as pure technology platforms connecting to external acquirers. The key distinction is regulatory: acquirers are licenced financial institutions; PSPs may or may not hold a financial licence.
How should merchants evaluate PSPs?
Key criteria: authorisation rate performance by market and card type; total cost of acceptance; fraud detection accuracy; settlement timing and currency support; technical reliability; payment method coverage; and reporting quality. Enterprise merchants should also assess the PSP's acquirer network breadth and smart routing capabilities.
Revolutionize your business with PXP
Take complete control of your commerce and payments with one platform.
Get Started