Wallets & Alternative Rails / Learning brief
PSP, gateway, acquirer: who does what
Your notes
In simple terms / 01
What this means in plain language
Merchants meet a crowd of intermediaries with overlapping names: gateway, payment service provider, acquirer, payment facilitator. Each does a distinct job. The gateway carries the transaction, the acquirer holds the scheme licence and the money, and a payment facilitator lets small merchants trade under its own umbrella. Untangling the roles tells you who is accountable when something breaks.
Taking cards is a job with several distinct trades, and one company often wears more than one hat, which is why the names blur. A payment gateway is the technical doorway: it captures the payment at checkout, forwards the authorisation request, and returns the answer — it holds no money. A payment service provider (PSP) is the broader contracting party that gives a merchant the ability to accept payments, often bundling the gateway with acquiring access, risk, and settlement reporting. The acquirer is the licensed bank that actually collects the card money and holds the scheme licence. A payment facilitator sits on top of an acquirer, onboarding many small sub-merchants under its own umbrella. The roles stay stable even when one provider combines them, and naming them is how you tell who is accountable when a payment or a refund goes wrong.
Key takeaways / 03
Three things to remember
- 01
A gateway carries the transaction and holds no funds; the acquirer holds the scheme licence and the money.
- 02
A PSP is the contracting party that may bundle gateway, acquiring access, and reporting into one relationship.
- 03
A payment facilitator lets small sub-merchants accept cards under its master acquiring relationship, concentrating onboarding and monitoring duties on itself.
Practical use cases / 04
Where you would use this
A merchant reading a chargeback notice works out which party — gateway, PSP, or acquirer — actually owns the dispute.
A small seller decides between contracting its own acquirer and joining a payment facilitator's umbrella for faster onboarding.
An operations lead maps the accountability chain before a launch, so an outage or a refund failure has a clear owner.
Worked example / 05
Put the idea into a real situation
(SYNTHETIC / TRAINING ONLY) Demo Coffee Ltd signs one contract with Larkpay, a fictional payment institution, to take cards. In that single relationship Larkpay is the gateway (its checkout captures the card), the PSP (it arranges acceptance and reporting), and it routes to Meridian Bank as the acquirer that holds the licence and collects the money. When a customer later disputes a EUR 4.50 charge, Demo Coffee needs to know that the chargeback is owned by the acquirer through Larkpay, not by the gateway software — the same firm, but a different hat. Had Demo Coffee instead been a sub-merchant under a payment facilitator, that facilitator would have answered for onboarding and monitoring.
Evidence & review / 07
Evidence & review
Card acceptance for online and in-person merchants; role names vary by provider and market, but the accountability chain holds.
What this brief simplifies: One provider often bundles several roles, so the clean separation shown here is a teaching model. Payment-facilitator obligations are summarised, not enumerated. Merchant and provider are synthetic.
Sources for this brief2
- Market practiceMarch 2003 edition
A glossary of terms used in payments and settlement systems ↗ — CPSS (now CPMI), Bank for International Settlements · Definitions: acquirer, payment service provider
Terminology has evolved since this edition; newer CPMI publications refine some definitions.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal · Role separation and synthetic merchant example
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.