Acquirer
An acquirer, or acquiring bank, is the financial institution that accepts card payments on a merchant’s behalf, sends them through the card networks for authorisation and settles the funds. Many merchants never deal with it directly: a payment service provider sits in front and passes on the acquirer’s results and decline codes.
How it works
An acquirer receives an authorisation request and forwards it through the card network to the card issuer. The issuer approves or declines. The answer travels back through the acquirer and usually through a payment service provider. Illustrative, synthetic example:
PAY-7C1D Provider T -> acquirer -> issuer
issuer: declined, code "51"
acquirer: response "DECLINED/51"
callback: Provider T status: failed reason: "insufficient funds"
By the time the merchant sees the result, the original code may have been renamed twice.
Why it matters
The acquirer is often where decline codes and settled amounts originate, but the merchant sees them through a PSP’s wording. That wording differs by provider. On one anonymised merchant day, 113 provider-and-code pairs collapsed into 22 reasons in one dictionary. 42.5% of declines carried a code whose meaning was not proven, so they stay “unknown”.
How to spot it
- Ask each PSP which acquirers it routes your card traffic through.
- Compare decline codes for the same reason across providers.
- Check whether statements name the acquirer or only the PSP.
Related terms
Payment service provider · Decline reason · Settlement · End provider · Provider intelligence
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