Payment Service Provider (PSP)

Overview

How it works and why it matters

A PSP supplies payment-related services to merchants or customers, but its exact scope varies by market and contract. It may provide checkout, processing, risk checks, accounts, settlement or reporting through its own systems and partners. The responsible legal and operational entity matters more than the marketing label.

Important technical and operational details

Depending on the market, a PSP may combine gateway, acquiring, processing, accounts, payment methods, fraud controls, settlement, reporting, or payouts.

Practical decision points

To compare PSPs, draw a responsibility map covering merchant onboarding, checkout interface, payment authorization, processing, fraud screening, custody, conversion, settlement, refunds and customer support. One provider may perform all these roles; another may resell a combination of upstream services. If a transfer fails, the merchant needs to know whether the merchant, PSP, acquiring partner, wallet owner or network is responsible for investigation. The same term can refer to different regulated entities under different local laws, so product capability should never be mistaken for a license status. Record the specific contracting entity and where funds are held at each stage.

Related concepts

Payment Provider; Provider Settlement

Further reading

• bis.org documentation