Payment service provider

A payment service provider (PSP) is a company that accepts payments on a merchant’s behalf through cards, wallets, bank transfers or local methods. It reports each payment back through callbacks and status responses, and later through a statement. Each PSP uses its own message formats, status words and statement layouts.

How it works

A payment service provider stands between the merchant and the payment networks. The merchant sends a payment request. The PSP processes it, sometimes through an acquirer. It then reports the result. Illustrative, synthetic example:

request    PAY-2F6C  -> Provider P  CUR-2  amount: 750
callback   Provider P  {"state": "OK", "sum": 75000}
statement  Provider P  ref: P-5531  amount: 750.00  status: Completed

One payment, three records, three vocabularies. The amount even changes unit between them.

Why it matters

Each payment service provider speaks its own language, and a merchant with many PSPs must translate all of them. On one anonymised merchant day, 96 providers produced 1,198 distinct message forms and 318 raw status values. Those mapped to only 9 canonical statuses. Without that translation, the same outcome looks different for every provider.

How to spot it

  • List every PSP with traffic, including ones reached through an orchestrator.
  • For each, note how it reports status and amount units.
  • Check whether each one sends a statement, and in which format.

Related terms

Acquirer · Payment orchestrator · End provider · Message shape · Providers

Try it on one day of your data

One day of your data, reconciled, and the report stays with you whether or not you continue.

Updated