PSP (Payment Service Provider)
A company that enables merchants to accept payments, often providing gateway, processing, routing and settlement services.

A payment service provider, or PSP, is a firm that lets a business take payments. It connects the shop to the acquirers, card networks and other methods behind the scenes. It usually handles the technical work too: taking card details, sending requests and reporting results. The term is broad, which is both its strength and its problem. It covers firms that do a narrow slice of this, and firms that do nearly all of it.
That breadth is the main source of muddle. Two firms can both call themselves a PSP and offer very different things. One may be a gateway with a single acquiring partner. Another holds its own licence, acquires directly and settles funds itself. UK rules name the regulated jobs rather than the marketing term, and Schedule 1 of those rules lists what counts as a payment service. Reading that list beats reading a brochure.
The Jobs A PSP Covers
It collects payment details, usually through hosted fields or a hosted payment page. It sends the request for approval and returns the answer, stores cards as tokens for repeat use, handles refunds, passes on disputes, reports what happened, and in many cases pays the money over. Where the PSP also holds the link to the acquirer, it may issue a merchant account under its own deal.
The Different Shapes
A PSP that is only a gateway moves messages and leaves the money to someone else. A full stack PSP does both, which is simpler to buy and harder to leave. An aggregator puts many sellers under one master account, which suits platforms and marketplaces, and makes each seller a registered sub-merchant. Some hold an electronic money institution licence and can hold funds themselves. Asking which shape you are buying is the first useful question.
Licensing And Who Holds The Money
This is where the gaps bite. If the PSP holds funds before passing them on, it needs a licence to do so, and the safeguards around that money depend on which licence it holds. If it does not hold funds, the money moves from the acquirer to the business directly. Neither is better in the abstract. What matters is knowing which applies, because that decides what happens to money in flight if the PSP runs into trouble.
What Good Looks Like
Staying up comes first, and uptime figures during peak trading matter more than a yearly average, because the bad hours are the expensive ones. Clear decline data matters too, since vague reasons turn a retry policy into guesswork. Reports should match what finance already uses, and settlement timing should be stated plainly, including what would change it. A PSP that dodges any of these is telling you something.
Access, Standards And Bank Connections
Where a PSP touches bank accounts rather than cards, a different rulebook applies. Banks must offer licensed firms a working access route, publish the technical detail free of charge, and give notice before changing it, and Article 30 of those standards sets all of that out, along with a way to test ahead of launch. That duty is what lets a PSP offer bank based payments as a real product.
One Provider Or Several
One PSP is simpler to run and leaves the business exposed on a bad day, while several bring reach and cover and multiply the reporting work. The middle path is a main PSP with a second route kept live, which serves both failover and a way to compare. Adding an external payment provider later is far easier when the first build allowed for it.
What A PSP Charges For
Pricing usually mixes a percentage of the amount with a fixed sum per payment, and on top of that sit the extras. Refunds, disputes, currency swaps, card storage and a monthly minimum all show up on real invoices and seldom on first quotes. Where the PSP also acquires, the acquiring cost and the service cost get quoted as one figure. Asking for the split is fair, and a PSP that will not give it is worth a second look.
Switching Costs Are Real
Leaving a PSP is harder than joining one. Stored cards sit in its vault and have to be moved, which needs the PSP to help and needs a formal process. Report formats differ, and matching history stays behind. None of this is a reason to stay with a poor PSP. It is a reason to ask about exit terms while you still have leverage, which means before you sign.
Matching A Provider To The Need
Work out which parts of the chain you actually need. Then match a PSP to that instead of buying all of it. Confirm who holds the money and under what licence. Ask about moving the card vault before signing. Keep one reference per payment, so a second PSP can be added with no rework of the data model. And keep measuring results all year. That is the theme of this piece on how to track provider performance. This look at orchestrator, gateway and PSP models is a useful frame.
Frequently Asked Questions
One is simpler to run and leaves the business exposed if it has a bad day. Several bring reach and resilience and multiply the reporting work. A common middle path is a primary provider with a second route kept live, both for failover and to give a genuine comparison on performance.
Not necessarily. Some PSPs hold their own acquiring licence and settle funds themselves. Others are effectively a gateway with an acquiring partner behind them. The difference matters most when something goes wrong, because responsibility follows the licence rather than the brand on the contract.
That depends on the model. Where a PSP holds funds before passing them on, it needs authorisation to do so and the safeguards depend on the licence. Where it does not, money moves from the acquirer to the business directly. Knowing which applies is worth establishing before signing.
Uptime during peak trading rather than an annual average, the clarity of decline data, settlement timing and what would change it, and how faults are communicated. Vault migration terms are worth agreeing at the start, since they are much harder to negotiate once you have decided to leave.
Harder than most supplier changes. Stored cards sit in the provider's vault and need a formal migration, reporting formats differ, and reconciliation history stays behind. Building the first integration with a second provider in mind makes the eventual change considerably less painful.

Still Have Questions?
Let’s Find the Right Solution for You
Stay Connected with Us!
Follow us on social media to stay up to date with the latest news, updates, and exclusive insights!


